Pitfalls of Infrastructure as Code (And how to avoid them!)
summary
Choose a framework with migration paths not marketing spin and treat security and policy as code rather than an afterthought. Concrete fixes include using terraform and Pulumi instead of cloud‑specific lock in, enforcing rules with Open Policy Agent, scanning with terrascan / checkov, and breaking resources into modules to avoid state file bloat causing 1–2 hour runs. The claim is that these tools and patterns reduce surprises by making deployments reproducible, verifiable, and fast.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:17What is IaC
- 3:45Types of pitfalls in Infrastructure as Code
- 5:50Choosing IaC framework
- 9:18IaC security
- 12:06Default config pitfalls
- 14:53Avoiding IaC repetition
- 16:58Managing IaC state size
- 20:10Resources & closing
related talks
54mInfrastructure as code (anti) Patterns
42mInfrastructure as Code - Lessons learned from Dev to Ops
36mInfrastructure as Code Done Right: Discovering and Fixing Common Missteps
33mScaling Infrastructure as Code
46mImplementing Infrastructure as Code
46mThe Rise and (Potential) Fall of Infrastructure as Code
01h 02mTools and Techniques for Infrastructure as Code
32mCode Quality and Infrastructure as Code