Files
DetectionLab/AWS/Terraform
Amit Serper ac17c974dd Update main.tf
Set the instance type of win10 to t2.large from t2.medium because t2.medium is barely responsive with this setup.
2021-07-21 10:43:04 -04:00
..
2021-07-15 15:05:00 -04:00
2021-05-15 08:41:30 -07:00
2020-08-14 00:33:59 -07:00
2021-07-21 10:43:04 -04:00
2021-06-27 09:45:12 -07:00
2020-06-25 17:09:39 -07:00
2020-11-20 22:58:07 -08:00
2021-07-11 20:11:39 -07:00
2020-06-25 17:11:04 -07:00

DetectionLab Terraform

Cost

terraform state pull |  curl -s -X POST -H "Content-Type: application/json" -d @- https://cost.modules.tf/
{"hourly": 0.17, "monthly": 123.26}

Method 1 - Pre-built AMIs

Estimated time to build: 30 minutes

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.

Using this method, it should be possible to bring DetectionLab online in under 30 minutes.

The instructions for deploying DetectionLab in AWS using the pre-built AMIs are available here: Pre-Built AMIs README

Method 2 - Building the VMs locally and exporting them to AWS as AMIs

Estimated time to build: 3-4 hours

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 instructions for deploying DetectionLab in AWS via this method are available here: Build Your Own AMIs README