Amazon Disputes Report an AWS Service Was Taken Down By Its AI Coding Bot (aboutamazon.com)
(Sunday February 22, 2026 @05:34PM (EditorDavid)
from the humor-errors dept.)
- Reference: 0180841588
- News link: https://slashdot.org/story/26/02/22/0650216/amazon-disputes-report-an-aws-service-was-taken-down-by-its-ai-coding-bot
- Source link: https://www.aboutamazon.com/news/aws/aws-service-outage-ai-bot-kiro
Friday Amazon published a blog post " [1]to address the inaccuracies " in a Financial Times [2]report that the company's own AI tool Kiro caused two outages in an AWS service in December.
Amazon writes that the "brief" and "extremely limited" service interruption "was the result of user error — specifically misconfigured access controls — not AI as the story claims."
And "The Financial Times' claim that a second event impacted AWS is entirely false."
> 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. 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.
>
> 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 to improve our security and resilience. Additional safeguards include mandatory peer review for production access. While operational incidents involving misconfigured access controls can occur with any developer tool — AI-powered or not — we think it is important to learn from these experiences.
[1] https://www.aboutamazon.com/news/aws/aws-service-outage-ai-bot-kiro
[2] https://it.slashdot.org/story/26/02/20/1252243/amazon-service-was-taken-down-by-ai-coding-bot
Amazon writes that the "brief" and "extremely limited" service interruption "was the result of user error — specifically misconfigured access controls — not AI as the story claims."
And "The Financial Times' claim that a second event impacted AWS is entirely false."
> 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. 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.
>
> 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 to improve our security and resilience. Additional safeguards include mandatory peer review for production access. While operational incidents involving misconfigured access controls can occur with any developer tool — AI-powered or not — we think it is important to learn from these experiences.
[1] https://www.aboutamazon.com/news/aws/aws-service-outage-ai-bot-kiro
[2] https://it.slashdot.org/story/26/02/20/1252243/amazon-service-was-taken-down-by-ai-coding-bot
Of course it is ... (Score:2)
by Compholio ( 770966 )
It's always the engineer's fault when you are making [1]reverse centaurs [medium.com].
[1] https://doctorow.medium.com/https-pluralistic-net-2025-12-05-pop-that-bubble-u-washington-8b6b75abc28e
They got a credibility problem there... (Score:2)
by gweihir ( 88907 )
Anyways, this "explanation" reeks of misdirection to me.
Re: (Score:2)
by 93 Escort Wagon ( 326346 )
"AI-generated blog post explains that AI wasn't involved in AI-caused outage"
Obvioulsy (Score:3)
by s0nicfreak ( 615390 )
When AI does something good it was AI's fault
When AI does something bad it was the fault of the prompter and/or the person that gave it access
According to Amazon (Score:2)
by sjames ( 1099 )
Your honor, my client is innocent. Sure, he set fire to that house and burned it to the ground, but where were the police? They should have stopped him! I say it's their fault the house burned down, prosecute them!
Of course they dispute it (Score:5, Informative)
What else were they supposed to say? Yes, you're right. Now let our stock price tumble?