Automating Chaos Engineering GameDays with Terraform
summary
Automates chaos gamedays by provisioning repeatable learning environments with Go and Terraform, spinning up AWS EC2 instances with a Gremlin agent on EC2 via user-data, wiring calendar, Slack and PagerDuty through Terraform providers, and packaging reusable logic into Terraform modules and providers. Demo shows infrastructure is created automatically and attacks run, cutting manual setup and repeat effort; notes friction around approvals, observability, and prepping teams despite generally successful runs.
AI-written summary · about
chapters (15)
- 0:00Introduction to talk
- 1:28Blame culture in tech
- 2:12What is chaos engineering
- 3:58Chaos maturity model
- 6:53What are Chaos GameDays
- 8:41Roles in Chaos GameDays
- 10:27Planning Chaos GameDays
- 12:37Manual Chaos GameDays challenges
- 15:14Terraform basics
- 16:40Provisioning chaos infrastructure
- 19:56Chaos attacks with Gremlin
- 21:03Terraform modules for chaos
- 24:15Automating Chaos GameDays
- 26:43Providers in Terraform
- 27:04Conclusion and Q&A
related talks
01h 23mAutomating your Infrastructure Deployments in the Google Cloud, Azure & AWS w/ Terraform
31mMaking AI work for you: Terraform engineer blueprint
32mBuilding Reliability into Kubernetes using Chaos Experiments with Terraform
27mAutomating for Failure: Disaster Recovery Testing with Terraform & Gremlin
46mEmbracing Collaborative Chaos
01h 03mTerraforming the world, one cloud at a time.
19mSynchronization of Infrastructure Provisioning & Application Deployments
57mLook Ma, no OPS! Automating microservices' infrastructure