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 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.
-
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 this just gets more and more funny.
-
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.
Democracy dies in OooOooh shiny thing!
-
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 It sounds as though they're ALSO letting AI write their responses to disruptions and outtages.
-
-
@Z_Zed_Zed @txalvita @nixCraft the main thing I’m still seeing and hearing from people I know in the company is not giving a shit
️ -
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 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.. -
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
> 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?
-
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 Millions are sitting in unclaimed cash while you struggle to pay bills. Over $35 BILLION is waiting to be claimed right now. Insurance refunds, lost checks, unpaid wages — it could be yours.
Check now before it’s gone.
https://www.chd93jds.com/CD2KW8S/PS824/
#unclaimed #money #insurence #refund -
R relay@relay.infosec.exchange shared this topic
