What struck me reading the postmortem wasn't the destruction itself. It was the decision chain: no remote state backend, deletion protection disabled, a Terraform archive from the old machine sitting there with full production state. Claude actually flagged the risk at multiple points. The human approved the destroy anyway.

I built a playable version of that session. You sit in a split-panel Claude Code interface - terminal on one side, AI agent on the other - and work through the recovery. The scenario uses the same kind of setup that caused the original disaster. It takes about 10-15 minutes.

This is part of YouBrokeProd, a browser-based incident response trainer I've been building. 10 scenarios total built from real postmortems - connection pool exhaustion, Kubernetes crashloops, DNS failures, SSL expiry, and others. Three are free including this one.

Stack: Next.js, Turso (SQLite at the edge), Supabase Auth. Each scenario is a state machine - you run commands, get realistic output back, form a hypothesis, and submit a diagnosis and fix. Scored on speed, accuracy, and efficiency.

The hardest part has been writing log output that's realistic enough to teach something but designed well enough to actually be solvable in 15 minutes. Curious what the SRE folks here think of the tradeoff.

You can stick an AWS architect badge on someone's forehead, or label them devops, but if there's a lack of systems experience and unpredictable tools at hand, disaster can and will happen.