Why you should take care of infrastructure drift
summary
Shows an open source tool called drift control that scans AWS and compares live resources to Terraform state, reporting coverage percentage and listing unmanaged resources with IDs. Demonstrates three concrete failures: an extra IAM access key, a security group opened to the world, and S3 versioning accidentally enabled (big cost). Tool is Go, Apache 2, outputs JSON for CI, supports AWS and GitHub, runs hourly or as a pre/post-terraform check, and the demos show real found drift and actionable reports.
AI-written summary · about
chapters (13)
- 0:00Infrastructure drift intro
- 1:45Why drift matters now
- 3:52Security risks of cloud drift
- 4:37Real drift stories
- 7:30Detecting hidden drift
- 12:30S3 versioning cost disaster
- 16:25Exporting drift data
- 17:51Filtering drift with jq
- 18:55Ignoring drift with .driftignore
- 20:42Drift control in CI
- 21:44Drift control safety check
- 22:46Open-source drift control
- 23:49Help and contribute
related talks
30mWhy you should take care of infrastructure drift
31mWhy You Should Take Care of Infrastructure Drift
27mThe State of Infrastructure Drift: What We Learned From 100+ DevOps Teams
21mFrom Ghost Assets to Infrastructure Drift - Don't Get Spooked
30mDon't Panic: Getting Your Infrastructure Drift Under Control
32mManaging Terraform resource drift using the GitOps method
29mTerraform Drift Detection and Reporting
26mManaging Terraform resource drift with the GitOps approach