FAQ
How can I customize the CloudFormation stacks that mu creates for my environment/service/database/pipeline?
You can provide custom CloudFormation YAML in your mu.yml that gets merged into the templates that mu creates. To learn more, check out Custom CloudFormation to learn more.
Yes! You can target an existing VPC in your mu.yml. Check out the vpc-target example to learn more.
Yes! You can provide CloudFormation in your mu.yml to define the VPN. Check out the vpn example to learn more.
Yes! You can configure your environments to use EC2 and CodeDeploy rather thatn ECS inside your mu.yml. Check out the vpn example to learn more.
- Traditional Infrastructure - Demonstration of using EC2 + CodeDeploy rather than ECS for running services
Why is there still a CloudFormation stack named mu-bucket-codepipeline after I terminated my pipeline?
The mu-bucket-codepipeline stack contains an S3 bucket for CodePipeline artifacts. It is shared by all pipelines that are deployed in a given region for an account. Therefore, since it is shared, it isn't safe to assume it can be deleted whenever a pipeline is terminated. Additionally, the bucket is likely not empty which would cause an error when CloudFormation tried to delete it. Alternatively, the bucket could have a DeletionPolicy of Retain, but that would cause a conflict the next time pipeline was created and the mu-bucket-codepipeline stack was recreated.
Therefore, the best approach was to retain the CloudFormation stack that managed the bucket. If you would like to delete the stack, then you should first empty the bucket with aws s3 rm s3://mu-codepipeline-<region>-<account_id> --recursive and then deleting the CloudFormation stack.
Awesome! Check out the contributing guidelines to get involved.
Ask on Gitter!