Tools and Techniques for Infrastructure as Code
summary
Automates deploys so a git commit runs tests, provisions cloud resources and pushes a new release without human steps; replaces a seven‑year weekly spreadsheet routine with a 20‑minute AppleScript proof that saved hours; prefers immutable deployments—spin up new instances, health‑check, then kill old ones—to avoid outages at the cost of a brief 5–10 minute resource doubling; uses Chef/Puppet/Ansible/Terraform or cloud‑specific tools and keeps deployment code in version control.
AI-written summary · about
chapters (16)
- 0:00Introduction to automation
- 3:22Make it work make it better
- 6:54Dry principle explained
- 9:29Small automation steps matter
- 12:25Manual deployment is bad
- 15:12Why automate infrastructure
- 21:32Learning from failure
- 23:17Writing code to deploy
- 27:34Executable documentation
- 31:33Professional commitment
- 33:18Never take shortcuts
- 37:51Version control automation
- 41:23Imperative vs declarative
- 48:15Mutable vs immutable deployment
- 53:50Why immutable is better
- 1:00:20Popular IaC tools overview
related talks
46mImplementing Infrastructure as Code
42mInfrastructure as Code - Lessons learned from Dev to Ops
46mThink of your infrastructure as code
54mInfrastructure as code (anti) Patterns
15mInfrastructure as a Code: Best Practices and Myths
50mImmutable Infrastructure as Code. True story
42mAutomate all the things
33mScaling Infrastructure as Code