Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add pre-built AMIs to Terraform and update documentation
- Loading branch information
Showing
15 changed files
with
302 additions
and
70 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,3 +6,5 @@ Boxes/* | |
.DS_Store | ||
Terraform/*/*.tfstate | ||
Terraform/*/.terraform | ||
Terraform/*/*.tfvars | ||
Terraform/*/*.lock.info |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
# Method 1 - Build Locally and Import to AWS | ||
|
||
This method uses Terraform to bring DetectionLab infrastructure online by using pre-built shared AMIs. | ||
|
||
The supplied Terraform configuration can then be used to create EC2 instances and all requisite networking components. | ||
|
||
## Prerequisites | ||
* A machine to build DetectionLab with | ||
* An AWS account | ||
* An AWS user and access keys to use with the AWS CLI | ||
* Optional but recommended: a separate user for Terraform | ||
|
||
## Step by step guide | ||
|
||
1. [Configure the AWS command line utility](https://docs.aws.amazon.com/polly/latest/dg/setup-aws-cli.html) | ||
2. Copy the file at [/DetectionLab/Terraform/terraform.tfvars.example](./terraform.tfvars.example) to `/DetectionLab/Terraform/terraform.tfvars` | ||
3. In `terraform.tfvars`, provide overrides for the variables specified in [variables.tf](./variables.tf) | ||
4. From the `/DetectionLab/Terraform/` directory, run `terraform init` to setup the initial Terraform configuration | ||
5. Run `terraform apply` to begin the provisioning process |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,21 +1,16 @@ | ||
# DetectionLab Terraform | ||
|
||
When I considered the possible ways of building DetectionLab using Terraform, two possibilities came to mind: | ||
|
||
### Method 1 - Building locally and exporting VMs | ||
The general concept behind this method is to use Virtualbox or VMware to build DetectionLab. You can then use AWS's VM import capabilities to create AMIs based off of the virtual machines. Once that process is complete, the infrastructure can easily be spun up using a Terraform configuration file. | ||
### Method 1 - Building the VMs locally and exporting them to AWS as AMIs | ||
One method for spinning up DetectionLab in AWS is to begin by using Virtualbox or VMware to build DetectionLab locally. You can then use AWS's VM import capabilities to create AMIs based off of the virtual machines. Once that process is complete, the infrastructure can easily be spun up using a Terraform configuration file. | ||
|
||
This method has the benefit of allowing users to customize the VMs before importing them to AWS. | ||
|
||
The obvious downside is that it still requires local infrastructure to build the lab, and uploading large OVA files to S3 can be extremely time consuming on slower connections. | ||
|
||
### Method 2 - Building and deploying in AWS | ||
The alternative to building locally would be to build the lab entirely in AWS. This would mean the Packer builds would need to be modified to generate EBS volumes and the Vagrant provisioning would need to be modified to support cloud infrastructure. Virtualbox and VMware-based builds benefit from things like virtual machine guest tools for file sharing, which are obviously unavailable on AWS instances. | ||
The instructions for deploying DetectionLab in AWS via this method are available here: [Build Your Own AMIs README](./VM_to_AMIs.md) | ||
|
||
This method has the benefit of not requiring any local infrastructure for builds but requires a lot of work, cost, and time to convert the build process to be cloud-based. | ||
|
||
### Progress Updates | ||
### Method 2 - Pre-built AMIs | ||
As of March 2019, I am now sharing pre-built AMIs on the Amazon Marketplace. The code inside of main.tf uses Terraform data sources to determine the correct AMI ID and will use the pre-built AMIs by default. | ||
|
||
The instructions for deploying DetectionLab to AWS via Method 1 are available here: [Method 1 README](./Method1/Method1.md) | ||
Using this method, it should be possible to bring DetectionLab online in under 15 minutes. | ||
|
||
Progress on Method 2 will be tracked using a GitHub project that is viewable here: https://github.com/clong/DetectionLab/projects/1 | ||
The instructions for deploying DetectionLab in AWS using the pre-built AMIs are available here: [Pre-Built AMIs README](./Pre-Built_AMIs.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
# Method 1 - Build Locally and Import to AWS | ||
|
||
This method involves using Terraform to bring DetectionLab infrastructure online by first building it locally using Virtualbox/VMware and then [importing the resulting virtual machines](https://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html#import-vm-image) as AMIs on AWS. | ||
|
||
The supplied Terraform configuration can then be used to create EC2 instances and all requisite networking components. | ||
|
||
## Prerequisites | ||
* A machine to build DetectionLab with | ||
* An AWS account | ||
* An AWS user and access keys to use with the AWS CLI | ||
* Optional but recommended: a separate user for Terraform | ||
|
||
## Step by step guide | ||
|
||
1. Build the lab by following the [README](https://github.com/clong/DetectionLab/blob/master/README.md) | ||
2. [Configure the AWS command line utility](https://docs.aws.amazon.com/polly/latest/dg/setup-aws-cli.html) | ||
3. [Create an S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-bucket.html). You will upload the DetectionLab VMs to this bucket later. | ||
|
||
4. For the VM importation to work, you must create a role named `vmimport` with a trust relationship policy document that allows VM Import to assume the role, and you must attach an IAM policy to the role: | ||
|
||
```aws iam create-role --role-name vmimport --assume-role-policy-document file:///path/to/DetectionLab/Terraform/vm_import/trust-policy.json``` | ||
|
||
5. Edit `/path/to/DetectionLab/Terraform/vm_import/role-policy.json` and insert the name of the bucket you created in step 3 on lines 12-13, replacing `YOUR_BUCKET_GOES_HERE` with the name of your bucket. | ||
|
||
6. Use the create-role command to create a role named vmimport and give VM Import/Export access to it: | ||
|
||
```aws iam put-role-policy --role-name vmimport --policy-name vmimport --policy-document file:///path/to/DetectionLab/Terraform/vm_import/role-policy.json``` | ||
|
||
7. Export the DetectionLab VMs as single file OVA files if they are not already in that format | ||
8. [Upload the OVAs to the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/upload-objects.html) you created in step three | ||
9. Edit the `logger.json`, `dc.json`, `wef.json` and `win10.json` files and modify the S3Bucket and S3Key headers to match the location of the OVA files in your S3 bucket. | ||
10. Import the VMs from S3 as AMIs by running the following commands: | ||
``` | ||
aws ec2 import-image --description "dc" --license-type byol --disk-containers file:///path/to/DetectionLab/Terraform/vm_import/dc.json | ||
aws ec2 import-image --description "wef" --license-type byol --disk-containers file:///path/to/DetectionLab/Terraform/vm_import/wef.json | ||
aws ec2 import-image --description "win10" --license-type byol --disk-containers file:///path/to/DetectionLab/Terraform/vm_import/win10.json | ||
aws ec2 import-image --description "logger" --license-type byol --disk-containers file:///path/to/DetectionLab/Terraform/vm_import/logger.json | ||
``` | ||
11. Check on the status of the importation with the following command: | ||
|
||
```aws ec2 describe-import-image-tasks --import-task-ids <import-ami-xxxxxxxxxxxxxxxxx>``` | ||
|
||
12. Fill out the variables in `/path/to/DetectionLab/Terraform/terraform.tfvars` | ||
13. Run `terraform init` to setup the initial Terraform configuration | ||
14. `cd /path/to/DetectionLab/Terraform/Method1 && terraform apply` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
output "logger_public_ip" { | ||
value = "${aws_instance.logger.public_ip}" | ||
} | ||
|
||
output "dc_public_ip" { | ||
value = "${aws_instance.dc.public_ip}" | ||
} | ||
|
||
output "wef_public_ip" { | ||
value = "${aws_instance.wef.public_ip}" | ||
} | ||
|
||
output "win10_public_ip" { | ||
value = "${aws_instance.win10.public_ip}" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
region = "us-west-1" | ||
shared_credentials_file = "/home/user/.aws/credentials" | ||
public_key_name = "id_logger" | ||
public_key_path = "/home/user/.ssh/id_logger.pub" | ||
private_key_path = "/home/user/.ssh/id_logger" | ||
ip_whitelist = ["1.2.3.4/32"] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
[ | ||
{ | ||
"Description": "dc", | ||
"Format": "ova", | ||
"UserBucket": { | ||
"S3Bucket": "YOUR_BUCKET_GOES_HERE", | ||
"S3Key": "dc.ova" | ||
} | ||
}] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
[ | ||
{ | ||
"Description": "logger", | ||
"Format": "ova", | ||
"UserBucket": { | ||
"S3Bucket": "YOUR_BUCKET_GOES_HERE", | ||
"S3Key": "logger.ova" | ||
} | ||
}] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
{ | ||
"Version":"2012-10-17", | ||
"Statement":[ | ||
{ | ||
"Effect":"Allow", | ||
"Action":[ | ||
"s3:GetBucketLocation", | ||
"s3:GetObject", | ||
"s3:ListBucket" | ||
], | ||
"Resource":[ | ||
"arn:aws:s3:::YOUR_BUCKET_GOES_HERE", | ||
"arn:aws:s3:::YOUR_BUCKET_GOES_HERE/*" | ||
] | ||
}, | ||
{ | ||
"Effect":"Allow", | ||
"Action":[ | ||
"ec2:ModifySnapshotAttribute", | ||
"ec2:CopySnapshot", | ||
"ec2:RegisterImage", | ||
"ec2:Describe*" | ||
], | ||
"Resource":"*" | ||
} | ||
] | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
{ | ||
"Version": "2012-10-17", | ||
"Statement": [ | ||
{ | ||
"Effect": "Allow", | ||
"Principal": { "Service": "vmie.amazonaws.com" }, | ||
"Action": "sts:AssumeRole", | ||
"Condition": { | ||
"StringEquals":{ | ||
"sts:Externalid": "vmimport" | ||
} | ||
} | ||
} | ||
] | ||
} |
Oops, something went wrong.