Mastodawn

juniyonul Feb 21

Amazon service (AWS) was taken down by AI coding bot named Kiro

https://futurism.com/artificial-intelligence/amazon-ai-aws-outages

In one incident in December, engineers at AWS allowed its in-house Kiro “agentic” coding tool to make changes that sparked a 13-hour disruption, according to four sources familiar with the matter. The AI, ill-fatedly, had decided to “delete and recreate the environment,” the sources said.

Amazon’s Blundering AI Caused Multiple AWS Outages

At least two outages at Amazon Web Services occurred after one of the company's AI models made changes to code.

Futurism

nixCraft 🐧Feb 21

So this wasn't some startup moving fast. This was Amazon, one of the biggest tech companies and their own AI coding tool still managed to take down a prod for 13 hours and it happened multiple times? If they can't get the this stupid AI stuff right the rest of the world should probably think twice on giving these AI tools write access to database, cloud, email and IT . Of course, Amazon is motivated to make more money by firing devs/IT staff and they think it is the next big thing. LOL

Tuchowski Feb 21

@nixCraft Deploy directly on prod.

Piotr Gaczkowski Feb 21

@nixCraft it's all about virtue signaling, I'm afraid.

@nixCraft Tell this to @signalapp

Taran Rampersad Feb 22

@nixCraft this just gets more and more funny. 🤣

@nixCraft I feel so bad about those PMs/C-suites deciding for these tools blindly. It cant be a simple engineer/architect that decided to go full on that. There is no way simple devs were preparing their replacement like that ;) I really wish this gets more traction to see the benefits of using AI..

> Of course, Amazon is motivated to make more money by firing devs/IT staff and they think it is the next big thing.

Right. That's the thing right there. Amazon is already extremely profitable. They have a good thing going, yet it is never enough. MORE MONEY this quarter as compared with last quarter is always the stupid goal. For some reason, the current profit level is insufficient, because… why?

Suryansh Feb 22

@nixCraft Human error they say

@nixCraft I was kidding when I said all the resent cloud outages was because of vibe coding/AI use. I guess reality really is a joke.

@nixCraft hahahahahahaha get fucked.

Morgana Magpie 🍉Feb 21

@nixCraft having used AWS for years, I know exactly why it decided to do that XD

@nixCraft Seems it was trained on the infamous IBM ad "have you tried turning it off and on again?".

SandroHc Feb 21

Amazlop? Colour me surprised.

Orca 🌻 | 🎀 | 🪁 | 🏴🏳️‍⚧️Feb 21

@nixCraft
Of course the AI decided to delete and recreate it.
It always does.😅

Kinene⭐🐻Feb 22

@nixCraft Suckers.

Guillotine Jones, Flâneur Feb 22

@nixCraft
Justice, and kind of poetic:
Amazon's AWS taken down by the work of an Ai coding bot.
Pleez feel the vibes.

@nixCraft This should surprise absolutely nobody who knows their shit. For example, #39C3 had multiple talks showing how "agentic coding" just keeps crashing and burning over and over again.

> AI tools were treated as an extension of an operator and given operator-level permissions

LOL.

Vinicius (PY2VMH)Feb 22

@nixCraft @Wuzzy AI agents are a cybersecurity nightmare. They are not easily controlled, so they can, and often do, end up doing stupid stuff (or malicious stuff) that breaks everything.

I am Jack's Found 404 Feb 22

Democracy dies in OooOooh shiny thing!

Al & Val's Modern Homesteading Feb 22

@nixCraft It sounds as though they're ALSO letting AI write their responses to disruptions and outtages.