Closed kartone closed 3 years ago
Thanks for the heads up! Will push out new AMIs tonight. I'm guessing this was from a Terraform deployment?
Yeah, I confirm that. Sorry for not being specific... :( thanks for the great project
I am experiencing the same issue, also a Terraform deployment using the AMIs. The AMIs haven't been updated yet, right?
Should be fixed now - can anyone confirm?
Just did: From DetectionLab/Vagrant: $ vagrant destroy wef $ [y] $ vagrant up wef
and looks good?
Thanks @MHaggis ! I'm gonna close this one out as fixed.
Hi, would like to reopen this issue since I am suffering the same problem. Latest version of DetectionLab used, following the usual AWS+Terraform tutorial:
Clone the DetectionLab repo to your filesystem: git clone https://github.com/clong/DetectionLab.git
In your AWS console, create and apply this policy to the IAM user whose keypair you will be using for terraform. This policy has been tailored to only use the required permissions needed for DetectionLab.
Configure the AWS command line utility and set up a profile for Terraform via aws configure --profile terraform.
Create a private/public keypair to use to SSH into logger: ssh-keygen -b 2048 -f ~/.ssh/id_logger
Copy the file at DetectionLab/AWS/Terraform/terraform.tfvars.example to /DetectionLab/AWS/Terraform/terraform.tfvars
In terraform.tfvars (the file you just copied), provide overrides for the variables specified in variables.tf.
The lab was successfully created however ATA is already expired.
Best regards.
Thanks for the heads up! Will take a peek
Yep, definitely expired. Will get some new AMIs pushed out shortly.
Sorry, had some issues with the exchange AMI last week. Got it working today. Should be fixed now.