Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. Amazon service (AWS) was taken down by AI coding bot named Kiro

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

Scheduled Pinned Locked Moved Uncategorized
38 Posts 35 Posters 2 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • nixcraft@mastodon.socialN nixcraft@mastodon.social

    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

    lexinova@cyberplace.socialL This user is from outside of this forum
    lexinova@cyberplace.socialL This user is from outside of this forum
    lexinova@cyberplace.social
    wrote last edited by
    #15

    @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.

    1 Reply Last reply
    0
    • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

      Link Preview Image
      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.

      favicon

      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.

      morganamagpie@tech.lgbtM This user is from outside of this forum
      morganamagpie@tech.lgbtM This user is from outside of this forum
      morganamagpie@tech.lgbt
      wrote last edited by
      #16

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

      1 Reply Last reply
      0
      • nixcraft@mastodon.socialN nixcraft@mastodon.social

        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

        doomhammerng@mastodon.socialD This user is from outside of this forum
        doomhammerng@mastodon.socialD This user is from outside of this forum
        doomhammerng@mastodon.social
        wrote last edited by
        #17

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

        1 Reply Last reply
        0
        • txalvita@neopaquita.esT txalvita@neopaquita.es

          @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

          steggy@sunny.gardenS This user is from outside of this forum
          steggy@sunny.gardenS This user is from outside of this forum
          steggy@sunny.garden
          wrote last edited by
          #18

          @txalvita @nixCraft it’s the second one. They don’t give a shit.

          1 Reply Last reply
          0
          • R relay@relay.an.exchange shared this topic
          • christianrickert@23.socialC christianrickert@23.social

            @nixCraft

            Handing write privileges to an AI is like handing a loaded gun to a drunk person.

            greenpete@sunny.gardenG This user is from outside of this forum
            greenpete@sunny.gardenG This user is from outside of this forum
            greenpete@sunny.garden
            wrote last edited by
            #19

            @christianrickert And what happened to staging? @nixCraft

            1 Reply Last reply
            0
            • R relay@relay.publicsquare.global shared this topic
            • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

              Link Preview Image
              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.

              favicon

              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.

              markus@toot.orchid-cottage.ukM This user is from outside of this forum
              markus@toot.orchid-cottage.ukM This user is from outside of this forum
              markus@toot.orchid-cottage.uk
              wrote last edited by
              #20
              @nixCraft Seems it was trained on the infamous IBM ad "have you tried turning it off and on again?".
              1 Reply Last reply
              0
              • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                Link Preview Image
                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.

                favicon

                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.

                iscarlosmolero@mastodon.socialI This user is from outside of this forum
                iscarlosmolero@mastodon.socialI This user is from outside of this forum
                iscarlosmolero@mastodon.social
                wrote last edited by
                #21

                @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.

                1 Reply Last reply
                0
                • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                  Link Preview Image
                  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.

                  favicon

                  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.

                  sandrohc@mastodon.socialS This user is from outside of this forum
                  sandrohc@mastodon.socialS This user is from outside of this forum
                  sandrohc@mastodon.social
                  wrote last edited by
                  #22

                  Amazlop? Colour me surprised.

                  1 Reply Last reply
                  0
                  • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                    Link Preview Image
                    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.

                    favicon

                    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.

                    orca@nya.oneO This user is from outside of this forum
                    orca@nya.oneO This user is from outside of this forum
                    orca@nya.one
                    wrote last edited by
                    #23
                    @nixCraft@mastodon.social
                    Of course the AI decided to delete and recreate it.
                    It always does.😅
                    1 Reply Last reply
                    0
                    • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                      Link Preview Image
                      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.

                      favicon

                      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.

                      ghostonthehalfshell@masto.aiG This user is from outside of this forum
                      ghostonthehalfshell@masto.aiG This user is from outside of this forum
                      ghostonthehalfshell@masto.ai
                      wrote last edited by
                      #24

                      @nixCraft

                      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

                      1 Reply Last reply
                      0
                      • nixcraft@mastodon.socialN nixcraft@mastodon.social

                        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

                        ck0@tech.lgbtC This user is from outside of this forum
                        ck0@tech.lgbtC This user is from outside of this forum
                        ck0@tech.lgbt
                        wrote last edited by
                        #25

                        @nixCraft Tell this to @signalapp

                        1 Reply Last reply
                        0
                        • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                          Link Preview Image
                          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.

                          favicon

                          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.

                          galacticstone@mastodon.socialG This user is from outside of this forum
                          galacticstone@mastodon.socialG This user is from outside of this forum
                          galacticstone@mastodon.social
                          wrote last edited by
                          #26

                          @nixCraft

                          Link Preview Image
                          1 Reply Last reply
                          0
                          • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                            Link Preview Image
                            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.

                            favicon

                            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.

                            c_merriweather@social.linux.pizzaC This user is from outside of this forum
                            c_merriweather@social.linux.pizzaC This user is from outside of this forum
                            c_merriweather@social.linux.pizza
                            wrote last edited by
                            #27

                            @nixCraft Suckers.

                            1 Reply Last reply
                            0
                            • comsey@mstdn.socialC comsey@mstdn.social

                              @txalvita @nixCraft I don't think people who would implement the AI agent with access to the production environment and people who decide that firing people is a feasible way of reducing the cost are anywhere near each other, it's a little bit more complicated than that

                              mcr314@todon.nlM This user is from outside of this forum
                              mcr314@todon.nlM This user is from outside of this forum
                              mcr314@todon.nl
                              wrote last edited by
                              #28

                              @comsey @txalvita @nixCraft true. But the overall impact on brand reliability is huge. Marketing alone should be walking both idiots to the curb.

                              1 Reply Last reply
                              0
                              • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                                Link Preview Image
                                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.

                                favicon

                                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.

                                guillotine_jones@beige.partyG This user is from outside of this forum
                                guillotine_jones@beige.partyG This user is from outside of this forum
                                guillotine_jones@beige.party
                                wrote last edited by
                                #29

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

                                1 Reply Last reply
                                0
                                • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                                  Link Preview Image
                                  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.

                                  favicon

                                  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.

                                  wuzzy@cyberplace.socialW This user is from outside of this forum
                                  wuzzy@cyberplace.socialW This user is from outside of this forum
                                  wuzzy@cyberplace.social
                                  wrote last edited by
                                  #30

                                  @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@mastodon.socialV 1 Reply Last reply
                                  0
                                  • nixcraft@mastodon.socialN nixcraft@mastodon.social

                                    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

                                    knowprose@mastodon.socialK This user is from outside of this forum
                                    knowprose@mastodon.socialK This user is from outside of this forum
                                    knowprose@mastodon.social
                                    wrote last edited by
                                    #31

                                    @nixCraft this just gets more and more funny. 🤣

                                    1 Reply Last reply
                                    0
                                    • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                                      Link Preview Image
                                      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.

                                      favicon

                                      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.

                                      float13@masto.hackers.townF This user is from outside of this forum
                                      float13@masto.hackers.townF This user is from outside of this forum
                                      float13@masto.hackers.town
                                      wrote last edited by
                                      #32

                                      @nixCraft

                                      Democracy dies in OooOooh shiny thing!

                                      1 Reply Last reply
                                      0
                                      • nixcraft@mastodon.socialN nixcraft@mastodon.social

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

                                        Link Preview Image
                                        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.

                                        favicon

                                        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.

                                        alandvalonline@mastodon.socialA This user is from outside of this forum
                                        alandvalonline@mastodon.socialA This user is from outside of this forum
                                        alandvalonline@mastodon.social
                                        wrote last edited by
                                        #33

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

                                        1 Reply Last reply
                                        0
                                        • wuzzy@cyberplace.socialW wuzzy@cyberplace.social

                                          @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@mastodon.socialV This user is from outside of this forum
                                          vinicius_py2vmh@mastodon.socialV This user is from outside of this forum
                                          vinicius_py2vmh@mastodon.social
                                          wrote last edited by
                                          #34

                                          @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.

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups