Description
Tired of Surprise `terraform plan` Changes — So I Built a Drift Detector
Hey r/devops
I’m a DevOps engineer with \~3 years of experience, and I kept running into the same issue: someone changes something directly in the AWS console, Terraform state drifts, and I only discover it when `terraform plan` suddenly shows 40 unexpected changes right before a deploy.
After dealing with that enough times, I decided to build something to make drift easier to understand and debug.
Full disclosure: I vibecoded most of this with Claude. I’m not a frontend/JS developer, but I knew exactly what workflow I wanted, and I think it solves a real pain point.
# What it does
* Reads your `.tfstate` file (local or S3) and gives you a visual dashboard of resources grouped by type/category
* Runs live drift detection against AWS APIs and shows the exact attributes that changed — not just “resource differs”
* Includes a Plan Analyzer: paste `terraform show -json tfplan` output and it compares:
* what your Terraform config wants
* what AWS actually has
* what the state file believes
GitHub: [[link]
Currently supports 34 AWS resource types across:
EC2, RDS, EKS, Lambda, S3, IAM, ECS, ElastiCache, OpenSearch, SQS, SNS, Route53, and more.
Runs with Docker Compose in a single command.
I know I didn’t manually write every line of code, but I did design the architecture, define the workflows/features, and validate it against real AWS infrastructure.
Would genuinely love feedback from people who deal with Terraform at scale:
* Is this a problem you actually run into?
* What would need to exist for you to use this in production?
* Any thoughts on querying AWS APIs directly vs relying on `terraform refresh`?
Happy to hear brutal feedback too.
[link]
[handle]
Employer contacts (email/phone/telegram) are hidden from the public preview —
send your CV, and we will connect you directly.