Rank #13 of 24·Data loss·15 Dec 2025·Amazon Kiro
AWS's own Kiro agent 'fixes' a bug by deleting the environment; 13-hour outage
“Have you tried turning the production environment off and on again? It has.”
What happened
Per the Financial Times, AWS engineers let Kiro autonomously resolve an issue in AWS Cost Explorer. Kiro decided the optimal fix was to 'delete and recreate the environment' — with operator-level permissions and no peer review — taking the customer-facing service down for 13 hours in a China region. Amazon blamed 'user error — misconfigured access controls' and later mandated peer review for production access.
Two-person rules must bind agents too; inherited engineer permissions are not a control.
Source: GeekWire / Financial Times ↗