Infrastructure-as-code drifts aren't like Pokemon : you can't catch em all
summary
Shows how infrastructure drift can go unnoticed in Terraform-managed AWS environments as teams grow and interact with external services, listing common pitfalls of standard drift-detection commands. Describes measuring “IaC coverage” (like test coverage) to compare Terraform code against actual AWS state and introduces driftctl, an open-source Apache‑2.0 tool that detects and warns about drift.
AI-written summary · about
related talks
24mWhy you should take care of infrastructure drift
30mWhy you should take care of infrastructure drift
31mWhy You Should Take Care of Infrastructure Drift
30mDon't Panic: Getting Your Infrastructure Drift Under Control
27mThe State of Infrastructure Drift: What We Learned From 100+ DevOps Teams
19mInfrastructure as Code: A Must Know Skill for Today's Developers
10mInfrastructure as a Code Best Practices with Terraform
18mInfrastructure as Code Security Best Practices & Strats