Whenever you are done with this scenario and environment, or if you want to take a break and come back a few days later, you can destroy this lab environment by using the command:



	./cloudgoat.py destroy ecs_takeover



Because this environment created EC2 instances, if you plan on stepping away from this lab for a few days, you should destroy it to a) avoid unnecessary charges and b) to avoid leaving a completely vulnerable EC2 instance in your AWS environment!



This lab environment will probably fail to destroy through this command alone. It might hang and you’ll sit there for a while and nothing will progress. In that case, just go in and manually remove the resources.



Go into ECS first and delete all clusters/services. Then, go into EC2 and terminate all running instances related to this lab (which should be 2)



Give that a couple of minutes, and then go into VPC. You won’t be able to delete the VPC if there are still running instances and network interfaces, so you’ll have to wait for those to fully terminate first. However, once you delete the cluster services and ec2 instance, Terraform may be able to handle the rest which is what happened for me:



     Destroy complete! Resources: 20 destroyed.



     [cloudgoat] terraform destroy completed with no error code.



     Successfully destroyed ecs_takeover_cgid12v3nnvkvd.



In that case just make sure you go through and verify that everything terminated successfully, and you’re good to go!



Also, and this is very important, if you created any resources of your own outside of what was created for us by CloudGoat, it will NOT be deleted! You need to go into the AWS account and manually delete! Leaving vulnerable resources behind will leave your account vulnerable.



I recommend performing a “visual inspection” of your AWS account to make sure everything truly did terminate.