Amazon has published a blog post to address the inaccuracies in a Financial Times report that the company’s own AI tool Kiro caused two outages in an AWS service in December. 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. The disruption was an extremely limited event last December affecting a single service, AWS Cost Explorer, in one of Amazon’s 39 Geographic Regions around the world. The issue stemmed from a misconfigured role, the same issue that could occur with any developer tool or manual action.
