Infrastructure as code makes mistakes reproducible
Defining infrastructure in code makes everything consistent, including the mistakes.
A misconfiguration in a template is deployed identically everywhere it is used, which turns one error into a fleet-wide condition. That is the cost of the same property that makes it valuable, and it is why the templates deserve review the way application code does.
More on Cloud resilience
- Multi-region is not the same as multi-providerTwo towns, one mains
- Autoscaling can scale a failure tooIt copied the mistake
- Managed services move responsibility, not all riskThe van takes the machines
- Private networking does not automatically mean trustedNobody asks twice
- Egress is part of the cloud security boundaryWatch the loading bay
- Snapshots can copy sensitive data silentlyThe copy keeps nothing
