Amazon claims it was 'coincidence' that AI tools were involved when company's service went and that the …

Amazon's cloud unit reportedly suffered at least two outages in the past few months. According to a report in Financial Times, these outages are reportedly linked to the use of company's own AI coding tools. This led the company to a closer examination of how these assistants are being deployed across its operations. A report claims that the biggest cloud service provider has shared an internal postmortem about the “outage” of an AWS system that will allow customers to review and analyse the costs of its services. After the investigation, Amazon has concluded that it was a "coincidence that AI tools were involved" and noted that "the same issue could occur with any developer tool or manual action."

In a statement to the Financial Times (FT), the company characterised both incidents as user-related mistakes, claiming that “in both instances, this was user error, not AI error," and added that internal analysis found no evidence suggesting errors were more frequent when AI tools were used compared with other development methods.

According to the FT report, in one instance, a 13-hour disruption in December 2025 occurred after engineers allowed Kiro, Amazon’s agentic AI coding tool, to make changes to a system, following which the tool determined that the best course of action was to "delete and recreate the environment."

The company also noted that the December 2025 incident was an “extremely limited event” that affected only a single service in certain parts of mainland China. Amazon also stated that the second incident did not impact a “customer-facing AWS service.”

Amazon also claimed that it was seeing continued customer adoption of Kiro and that it aims to benefit both customers and employees from efficiency improvements.

“Following the December incident, AWS implemented numerous safeguards,” the company said, adding that these measures include mandatory peer review processes and additional staff training.

In a statement to TOI, Amazon spokesperson denied any AWS outage, “This brief event was the result of user error—specifically misconfigured access controls—not AI. The service interruption was an extremely limited event last year when a single service (AWS Cost Explorer—which helps customers visualize, understand, and manage AWS costs and usage over time) in one of our two Regions in Mainland China was affected. This event didn’t impact compute, storage, database, AI technologies, or any other of the hundreds of services that we run. Following these events, we implemented numerous additional safeguards, including mandatory peer review for production access. Kiro puts developers in control—users need to configure which actions Kiro can take, and by default, Kiro requests authorization before taking any action,” said an AWS spokesperson.