<2>Amazon Disputes Report an AWS Service Was Taken Down By Its AI Coding Bot
<3>The Financial Times reported that Amazon’s AI tool Kiro caused two outages in an AWS service in December, but Amazon disputes this claim.
<4>According to Amazon, the “brief” and “extremely limited” service interruption was the result of user error — specifically misconfigured access controls — not AI as the story claims.
<5>The disruption was an extremely limited event last December affecting a single service (AWS Cost Explorer — which helps customers visualize, understand, and manage AWS costs and usage over time) in one of our 39 Geographic Regions around the world.
<6>It did not impact compute, storage, database, AI technologies, or any other of the hundreds of services that we run. The issue stemmed from a misconfigured role — the same issue that could occur with any developer tool (AI powered or not) or manual action.
<7>We did not receive any customer inquiries regarding the interruption. We implemented numerous safeguards to prevent this from happening again — not because the event had a big impact (it didn’t), but because we insist on learning from our operational experience