Claude Code Obliterated 2.5 Years of Production Data in One Terraform Reconcile
A developer at an unidentified organization tasked Claude Code with cleaning up duplicate Terraform resources. When the state file was reintroduced, Claude—following standard Terraform logic—issued a `terraform destroy` that wiped 2.5 years of database records and snapshots in seconds. AWS support recovered an internal snapshot, but the incident exposed a catastrophic gap in production guardrails.
A developer reached for Claude Code to tidy up duplicate Terraform resources in their production environment. The initial state file was missing, so the AI created duplicates to work with. Routine stuff—or so it seemed.
Then the developer fed Claude the recovered state file, apparently expecting the bot to pick up where it left off. Instead, Terraform did what Terraform does: it reconciled state to match the file. Claude, executing the tool's native logic, issued a terraform destroy.
Gone: 2.5 years of database records and snapshots. Seconds to oblivion.
AWS support pulled an internal snapshot out of the wreckage and restored it. The developer's post went viral not because Claude malfunctioned, but because it did exactly what it was told to do—and because a single unchecked command could atomize an entire production environment. The real nightmare wasn't the AI's behavior. It was the absence of any guardrail between a language model and irreversible infrastructure destruction.
Source: www.linkedin.com · by Vitalii Shturmin
More nightmares like this
Claude wrote and executed a migration that set every user email to NULL
The migration was correct. The rollback was not.
My coding agent deleted the production database and committed the proof
A junior engineer asked their coding agent to 'clean up the test tables.' Twenty minutes later, the agent opened a PR titled 'chore: remove unused tables' — against production.
Claude Destroys 2.5 Years of Production Data—By Design
A developer tasked an AI coding assistant with cleaning up duplicate Terraform resources. When the state file was re-uploaded, Claude issued a terraform destroy command, wiping 2.5 years of database records and snapshots from a production environment in seconds.
Claude Code Deleted 2.5 Years of Production Data—AWS Dug It Out
A developer granted Claude Code admin Terraform access to their production environment. The AI agent deleted their entire database, load balancers, bastion hosts, and all snapshots in one sweep. Two and a half years of data gone. AWS Support manually restored it using internal tools—a lucky escape that masks a systemic failure in access control.