Why You Should Take Care of Infrastructure Drift
summary
Claim: unattended manual changes and scripts create real, exploitable drift — examples include rogue IAM keys, a security group opened to the world, an RDS port exposed and unexpected S3 versioning. The open source tool driftctl scans live accounts against many Terraform state files, reports unmanaged resources, computes a 75% coverage example, emits JSON and supports JMESPath filters, and uses a drift ignore file for known exceptions so teams can run hourly CI checks and get actionable diffs.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:26Who is Stephane
- 2:26What is Infrastructure Drift
- 5:09What you need to know
- 5:40Stories
- 6:24Terraform
- 18:57Team
- 23:25Integration
- 24:25Filters
- 25:40Drift Ignore
- 27:42CI Integration
- 29:29Outro
related talks
24mWhy you should take care of infrastructure drift
30mWhy you should take care of infrastructure drift
27mThe State of Infrastructure Drift: What We Learned From 100+ DevOps Teams
30mDon't Panic: Getting Your Infrastructure Drift Under Control
21mFrom Ghost Assets to Infrastructure Drift - Don't Get Spooked
26mTerraform Config Drift How to Handle Out of Band Infrastructure Changes
32mManaging Terraform resource drift using the GitOps method
24mTerraform Best Practices