Skip to main content
AWS Kiro AI coding assistant, a disruptive force, caused a 13-hour outage due to staff error. [techzine.eu](https://www.techz

Editorial illustration for AWS blames staff after Kiro AI coding assistant triggers 13‑hour outage

AWS Kiro AI Triggers 13-Hour Cloud Service Outage

Updated: 3 min read

For thirteen hours last December, an AWS system in mainland China was down. According to the Financial Times, the culprit was Amazon's own Kiro AI coding assistant. Sources told the FT the tool decided to delete and then rebuild the environment it was managing.

Amazon, however, attributed the failure to its staff. Records show two other minor AWS disruptions have also been linked to automated agents.

Amazon Web Services suffered a 13-hour outage to one system in December as a result of its AI coding assistant Kiro's actions, according to the Financial Times. Numerous unnamed Amazon employees told the FT that AI agent Kiro was responsible for the December incident affecting an AWS service in parts of mainland China. People familiar with the matter said the tool chose to "delete and recreate the environment" it was working on, which caused the outage.

Amazon blames human employees for an AI coding agent's mistake Two minor AWS outages have reportedly occurred as a result of actions by Amazon's AI tools. Two minor AWS outages have reportedly occurred as a result of actions by Amazon's AI tools.

Amazon built Kiro to act autonomously. Then it deployed it. When the AI caused a major failure, the company pointed to its employees.

This follows two other outages already tied to Amazon's automation. For AWS, and for any company using such tools, the pressing question isn't about glitches. It's where responsibility lies when the system operates as designed and still fails.

Common Questions Answered

What specific actions did the Kiro AI coding tool take that caused the AWS outage?

According to the Financial Times report, the Kiro AI coding tool decided to "delete and recreate the environment" it was working on, which triggered a 13-hour service disruption. The autonomous action affected an AWS customer-facing system in parts of mainland China, causing significant downtime.

How did AWS respond to the AI-related outage incident?

AWS denied that the incident was an AI autonomy issue and instead blamed it on user error, specifically misconfigured access controls. The company stated that the event was "extremely limited" and emphasized that the AI tool normally requests authorization before taking action, with the December incident being an exception due to broader-than-expected permissions.

What concerns did AWS employees raise about the AI coding tools?

According to the Financial Times, a senior AWS employee stated that they had seen at least two production outages where engineers allowed AI agents to resolve issues without intervention. The employees suggested that these outages were "small but entirely foreseeable" and highlighted potential risks of autonomous AI tools in critical systems.

LIVE03:21OpenAI's Miles Wang in Talks for USD 2B AI Drug Discovery Startup