Menu

1 / 2

Terraform at Scale: How We Manage 500+ Resources Across 8 AWS Accounts Without Losing Our Minds

DEV Community: terraform·Garrett Yan·7 days ago
#Y46CsvID
#devtoterraform#devto#dev#terraform#plan
Reading 0:00
15s threshold

November 2026 | ~18 min read

The terraform destroy That Took Down Staging

It was 3:47 PM on a Thursday. An engineer ran terraform destroy to clean up a sandbox VPC. Except they were in the wrong Terraform workspace. Staging was gone — 47 resources deleted in 90 seconds. The RDS instance. The EKS cluster. The VPN connections. All of it.

Recovery took 6 hours. Not because the infrastructure was hard to rebuild — we had the Terraform code. But because nobody could figure out what the staging state file actually contained. The state was a single 50MB monolith covering every resource across every environment. Running terraform plan took 15 minutes. Finding which resources belonged to staging vs. production vs. shared-services required reading through 12,000 lines of state JSON.

The real problem wasn't the accidental destroy.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.