This fix will restrict SSH access to only the creating user's CIDR, entered on the command line or in the console form fields. This occurs on all instances that are created, and also restricts inbound port 22 on the ACL to the creator's CIDR.
I also fixed an issue where the S3 bucket for build artifacts was not created. It was defaulting to "dromedary-" but no bucket was ever provisioned with that name. Unfortunately it can't be easily deleted on stack rollback or deletion as it contains files. I wish there was an "EmptyAndDelete" option for deletion policies. I set the deletion policy for this bucket to "Retain" so if you try to recreate the stack without manually deleting the bucket, you'll get a "Bucket already exists" error.
cplee
commented
7 years ago
This fix will restrict SSH access to only the creating user's CIDR, entered on the command line or in the console form fields. This occurs on all instances that are created, and also restricts inbound port 22 on the ACL to the creator's CIDR.
I also fixed an issue where the S3 bucket for build artifacts was not created. It was defaulting to "dromedary-" but no bucket was ever provisioned with that name. Unfortunately it can't be easily deleted on stack rollback or deletion as it contains files. I wish there was an "EmptyAndDelete" option for deletion policies. I set the deletion policy for this bucket to "Retain" so if you try to recreate the stack without manually deleting the bucket, you'll get a "Bucket already exists" error.