Infrastructure as a Code: Best Practices and Myths
summary
Three and a half years of IaC adoption yields concrete gains: a set of Git-tracked infrastructure modules, CI/CD pipelines that deploy Docker images, and artifacts stored in S3 so recovery spins a whole environment back up in minutes instead of days — work that used to take two days now runs from a single commit. Secrets live in a vault, not source, and access controls prevent runtime edits. Automation reduces onboarding and provisioning time but does not remove the need for ops. use Git as single source of truth never commit secrets
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:08Manual setup problems
- 2:37Automation benefits
- 4:33Resource consistency
- 6:23Change tracking importance
- 8:10Security and passwords
- 10:01Microsoft Azure features
- 11:14Server configuration
- 12:41Version control integration
- 13:27Deployment workflow
related talks
18mInfrastructure as Code Security Best Practices & Strats
36mInfrastructure as Code Done Right: Discovering and Fixing Common Missteps
46mImplementing Infrastructure as Code
28mInfrastructure as Code in the Real World
42mInfrastructure as Code - Lessons learned from Dev to Ops
01h 02mTools and Techniques for Infrastructure as Code
54mInfrastructure as code (anti) Patterns
51mInfrastructure-as-code: bridging the gap between Devs and Ops