Reports claim an AWS outage last year was caused by an AI coding tool deciding to 'delete and recreate the environment' from scratch, while Amazon says 'misconfigured access controls' were to blame
The vibes may have been off.
Keep up to date with the most important stories and the best deals, as picked by the PC Gamer team.
You are now subscribed
Your newsletter sign-up was successful
Want to add more newsletters?
Every Friday
GamesRadar+
Your weekly update on everything you could ever want to know about the games you already love, games we know you're going to love in the near future, and tales from the communities that surround them.
Every Thursday
GTA 6 O'clock
Our special GTA 6 newsletter, with breaking news, insider info, and rumor analysis from the award-winning GTA 6 O'clock experts.
Every Friday
Knowledge
From the creators of Edge: A weekly videogame industry newsletter with analysis from expert writers, guidance from professionals, and insight into what's on the horizon.
Every Thursday
The Setup
Hardware nerds unite, sign up to our free tech newsletter for a weekly digest of the hottest new tech, the latest gadgets on the test bench, and much more.
Every Wednesday
Switch 2 Spotlight
Sign up to our new Switch 2 newsletter, where we bring you the latest talking points on Nintendo's new console each week, bring you up to date on the news, and recommend what games to play.
Every Saturday
The Watchlist
Subscribe for a weekly digest of the movie and TV news that matters, direct to your inbox. From first-look trailers, interviews, reviews and explainers, we've got you covered.
Once a month
SFX
Get sneak previews, exclusive competitions and details of special events each month!
A report from The Financial Times claims that, according to four of its sources, two recent AWS outages were caused by engineers allowing its Kiro AI coding tool to make changes without oversight.
According to a senior AWS employee, at least two production outages in the past few months were caused by the AI agent operating on its own terms. "The engineers let the AI [agent] resolve an issue without intervention," one source claims. "The outages were small but entirely foreseeable."
The FT's sources claim that one particular 13-hour interruption in December of last year was caused by the agentic tool deciding that the best course of action was to "delete and recreate the environment", which has echoes of another rogue AI agent last year deleting an entire codebase on a whim.
However, Amazon has since claimed that access control permissions were to blame, not the AI itself. In a statement to The Register referencing the aforementioned event, Amazon said:
"This brief event was the result of user (AWS employee) 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."
And in similar statements to the FT, Amazon said that its Kiro AI tool "requests authorisation before taking any action", and repeated the claim that the engineer involved in the December incident had "broader permissions than expected." The company also said that it was a "coincidence that AI tools were involved."
Keep up to date with the most important stories and the best deals, as picked by the PC Gamer team.
So, user error not AI error, at least according to Amazon. Still, as AI coding tools continue to be deployed by engineers across the globe, I doubt this is the last time we'll hear claims of rogue AI deployments running amok and causing significant disruption, as well as companies rushing to claim that it's still in full control, not the AI.
While agentic AI coding certainly seems to have its uses, it seems that figuring out the guardrails around its deployment is still something of a work in progress, even for a web giant like AWS.

1. Best gaming laptop: Razer Blade 16
2. Best gaming PC: HP Omen 35L
3. Best handheld gaming PC: Lenovo Legion Go S SteamOS ed.
4. Best mini PC: Minisforum AtomMan G7 PT
5. Best VR headset: Meta Quest 3

Andy built his first gaming PC at the tender age of 12, when IDE cables were a thing and high resolution wasn't—and he hasn't stopped since. Now working as a hardware writer for PC Gamer, Andy spends his time jumping around the world attending product launches and trade shows, all the while reviewing every bit of PC gaming hardware he can get his hands on. You name it, if it's interesting hardware he'll write words about it, with opinions and everything.
You must confirm your public display name before commenting
Please logout and then login again, you will then be prompted to enter your display name.

