AWS Refutes AI Tool Blamed for Service Outage

The spokesperson emphasized that the outage stemmed from “misconfigured access controls, not AI,” dispelling any misconceptions about the role of artificial intelligence in the incident.

This response came after a Financial Times article suggested that a 13-hour outage was linked to adjustments made by the Kiro AI tool. AWS refuted this claim, asserting that the report was inaccurate and reaffirming that user error was the definitive cause of the outage.

According to the AWS representative, “Kiro puts developers in control—users need to configure which actions Kiro can take, and by default, Kiro requests authorization before taking any action,” highlighting the importance of user oversight in utilizing such tools.

We’d love to be your preferred source for news.

Please add us to your preferred sources list so our news, data and interviews show up in your feed. Thanks!

Additionally, the AWS representative noted that the service disruption specifically affected the AWS Cost Explorer and did not impact other services, including computing, storage, databases, or AI technologies.

Previously, PYMNTS reported that AI coding assistants empower companies to significantly reduce technology development costs while maintaining competitive digital capabilities. These advanced tools leverage large language models to generate code, fix bugs, and streamline processes, allowing smaller teams to tackle tasks that would typically require extensive resources.

In August, concerns arose among investors regarding AI tools facilitating faster and cheaper software development, prompting a market selloff that affected major software companies.

One prominent provider of an agentic coding solution, Anthropic, announced on February 12 that its Claude Code product has garnered significant interest, generating a run-rate revenue of $2.5 billion since its public release in May.

AWS faced a separate, more widespread outage in October that disrupted services for millions globally. This incident was linked to issues within the Amazon DynamoDB system, responsible for providing database storage and computing power.

To keep up-to-date with all AI-related news from PYMNTS, subscribe to our daily AI Newsletter.