Amazon service (AWS) was taken down by AI coding bot named Kiro
-
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
@nixCraft If AWS managed to destroy its dominance in the Cloud hosting market purely because it was trying to chase something around AI... well... let's just say I'm sure there's a German word for it.
-
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
@nixCraft *another* reason to get stuff away from there
-
-
@christianrickert @nixCraft More like handing your air traffic control over to a well trained parrot.
To me, the parrot sounds like an ATC operator. You could play it on a news broadcast or a press release and it’ll sound just fine to anybody who isn’t an ATC operator or pilot.
Now let’s imagine what happens when a plane is given permission to land on runway 13 and another is given permission to land on runway 31.
Yeah, but your average parrot is not going to shuffle the layout of the runways while squawking to the pilots. 🦜
-
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
@nixCraft don't use any US crap anymore so they can break it all they want not my problem anymore.
If they could delete every server of amazon... it would bring back job i guess.
-
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
@nixCraft having used AWS for years, I know exactly why it decided to do that XD
-
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
@nixCraft it's all about virtue signaling, I'm afraid.
-
@nixCraft
They are fucking idiots
OR
They don't give a shit about losing a lot of money if they can save it firing people. Trial and error.
They can afford it -
R relay@relay.an.exchange shared this topic
-
Handing write privileges to an AI is like handing a loaded gun to a drunk person.
@christianrickert And what happened to staging? @nixCraft
-
R relay@relay.publicsquare.global shared this topic
-
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
@nixCraft Seems it was trained on the infamous IBM ad "have you tried turning it off and on again?". -
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
@nixCraft This is fueling an unprecedented fear of flying in me. I’m constantly terrified of corporate ghouls deciding to let loose a text-based slot machine in aircraft’s codebases just to save money or whatever stakeholder pleasing shit.
-
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
Amazlop? Colour me surprised.
-
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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 service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
Yeah, I watched pivot to AI comments on this and I always love when he grimaces/grins about shit like this.
Obviously what they need to do is add more agents to help fix the bugs
-
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
@nixCraft Tell this to @signalapp
-
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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 service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
@nixCraft Suckers.
-
-
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
@nixCraft
Justice, and kind of poetic:
Amazon's AWS taken down by the work of an Ai coding bot.
Pleez feel the vibes. -
Amazon service (AWS) was taken down by AI coding bot named Kiro
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 (futurism.com)
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.
