An Environment Per Branch with Infrastructure as Code
summary
Claims that per-branch environments built with Infrastructure as Code speed development and testing and notes two years of practice across AWS CDK, Terraform and CloudFormation. Describes a pipeline that auto-deploys a full stack per branch, runs a destroy pipeline on merge or branch deletion, and tags resources for cost reporting. Warns about naming limits, quotas, retained resources (databases and S3), surprising costs for many servers and cases of a thousand lambdas per account to track. Examples and CDK code linked.
AI-written summary · about
related talks
42mTransient Test Environments
27mFrom Infrastructure as Code to Environment as Code: ...
46mImplementing Infrastructure as Code
23mCI/CD at Scale: Best Practices with AWS DevOps Services
23mCI/CD at Scale: Best practices with AWS DevOps Services
28mFrom Infrastructure as Code to Environment as Code: Challenges scaling IaC
33mEnvironments as Cattle
25mImprove Developer Productivity with Ephemeral Environments