Implementing Infrastructure as Code
summary
Argues that defining infrastructure in versioned code and running it through CI pipelines turns risky, slow provisioning into routine, testable change. Shows concrete tooling and patterns: terraform/cloudformation stacks per environment, Packer-built AMIs for immutable servers, Ansible/Chef/Puppet for in-image configuration, Test Kitchen and Docker for fast server-level tests, and CI servers (GoCD/Concourse/Jenkins) to build, test and promote stacks. Demonstrates pipelines that create, test and tear down real environments to prevent drift and enable frequent, safe infrastructure changes.
AI-written summary · about
chapters (16)
- 0:00Start
- 5:34Lowers barriers to fixing broken
- 7:45Multiple teams working on a system with many moving parts
- 8:18Cloud and automation
- 9:14Configuration drift
- 9:54Automation fear cycle
- 11:10Synchronize continuously
- 14:26Automate each change as you work on it
- 15:35Define environments as code Environment configuration is
- 18:34Defining and provisioning environments Environment Definition Code
- 19:13Infrastructure stack
- 28:22Define server configuration as code Server configuration code
- 30:29Define custom server images as code
- 34:36Coordinating changes
- 35:37Draw boundaries to minimize changes that cross stacks
- 38:09Share components across stacks
related talks
46mThink of your infrastructure as code
42mInfrastructure as Code - Lessons learned from Dev to Ops
01h 02mTools and Techniques for Infrastructure as Code
54mInfrastructure as code (anti) Patterns
33mScaling Infrastructure as Code
01h 02mTools and Techniques for Infrastructure as Code
50mImmutable Infrastructure as Code. True story
32mCode Quality and Infrastructure as Code