It can be rather cumbersome to manage security groups. Especially if you have a build creating and testing AMI across multiple AWS accounts and regions. You have to add them in AWS and then ensure the correct one is being used in CI servers.
Instead of all that manual work, let's get AMI Spec to do it for us!
I propose that if a security group isn't provided via the command line, then a temporary security group is generated in AWS and used for the duration of the testing. This temporary security group allows SSH access. After the tests have completed and the EC2 instance is terminated, the security group is deleted.
It can be rather cumbersome to manage security groups. Especially if you have a build creating and testing AMI across multiple AWS accounts and regions. You have to add them in AWS and then ensure the correct one is being used in CI servers.
Instead of all that manual work, let's get AMI Spec to do it for us!
I propose that if a security group isn't provided via the command line, then a temporary security group is generated in AWS and used for the duration of the testing. This temporary security group allows SSH access. After the tests have completed and the EC2 instance is terminated, the security group is deleted.