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

    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.

    christianrickert@23.socialC nixcraft@mastodon.socialN aanee@mastodon.onlineA mellivora@im-in.spaceM cyberoutsider@infosec.exchangeC 17 Replies Last reply
    3
    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.

      christianrickert@23.socialC This user is from outside of this forum
      christianrickert@23.socialC This user is from outside of this forum
      christianrickert@23.social
      wrote last edited by
      #2

      @nixCraft

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

      C greenpete@sunny.gardenG 2 Replies 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.

        nixcraft@mastodon.socialN This user is from outside of this forum
        nixcraft@mastodon.socialN This user is from outside of this forum
        nixcraft@mastodon.social
        wrote last edited by
        #3

        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

        txalvita@neopaquita.esT adipoeserpursch@troet.cafeA mkoek@mastodon.nlM lexinova@cyberplace.socialL doomhammerng@mastodon.socialD 10 Replies 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.

          aanee@mastodon.onlineA This user is from outside of this forum
          aanee@mastodon.onlineA This user is from outside of this forum
          aanee@mastodon.online
          wrote last edited by
          #4

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

          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

            txalvita@neopaquita.esT This user is from outside of this forum
            txalvita@neopaquita.esT This user is from outside of this forum
            txalvita@neopaquita.es
            wrote last edited by
            #5

            @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

            eickot@mastodon.socialE comsey@mstdn.socialC steggy@sunny.gardenS 3 Replies 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

              adipoeserpursch@troet.cafeA This user is from outside of this forum
              adipoeserpursch@troet.cafeA This user is from outside of this forum
              adipoeserpursch@troet.cafe
              wrote last edited by
              #6

              @nixCraft Deploy directly on prod.

              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.

                mellivora@im-in.spaceM This user is from outside of this forum
                mellivora@im-in.spaceM This user is from outside of this forum
                mellivora@im-in.space
                wrote last edited by
                #7

                @nixCraft hahahahahahaha get fucked.

                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

                  eickot@mastodon.socialE This user is from outside of this forum
                  eickot@mastodon.socialE This user is from outside of this forum
                  eickot@mastodon.social
                  wrote last edited by
                  #8

                  @txalvita @nixCraft It's simple, they loose more money durint this 13h that they saved with the employers that fired. I expect not yet... also will be nice to know when they allowed the AI full access. it was 1 year ago. or only some weeks ago

                  phdgris@mastodon.socialP 1 Reply Last reply
                  0
                  • christianrickert@23.socialC christianrickert@23.social

                    @nixCraft

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

                    C This user is from outside of this forum
                    C This user is from outside of this forum
                    clickymcticker@hachyderm.io
                    wrote last edited by
                    #9

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

                    christianrickert@23.socialC 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

                      comsey@mstdn.socialC This user is from outside of this forum
                      comsey@mstdn.socialC This user is from outside of this forum
                      comsey@mstdn.social
                      wrote last edited by
                      #10

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

                        cyberoutsider@infosec.exchangeC This user is from outside of this forum
                        cyberoutsider@infosec.exchangeC This user is from outside of this forum
                        cyberoutsider@infosec.exchange
                        wrote last edited by
                        #11

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

                        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

                          mkoek@mastodon.nlM This user is from outside of this forum
                          mkoek@mastodon.nlM This user is from outside of this forum
                          mkoek@mastodon.nl
                          wrote last edited by
                          #12

                          @nixCraft *another* reason to get stuff away from there

                          1 Reply Last reply
                          0
                          • eickot@mastodon.socialE eickot@mastodon.social

                            @txalvita @nixCraft It's simple, they loose more money durint this 13h that they saved with the employers that fired. I expect not yet... also will be nice to know when they allowed the AI full access. it was 1 year ago. or only some weeks ago

                            phdgris@mastodon.socialP This user is from outside of this forum
                            phdgris@mastodon.socialP This user is from outside of this forum
                            phdgris@mastodon.social
                            wrote last edited by
                            #13

                            @eickot @txalvita @nixCraft do they?

                            1 Reply Last reply
                            0
                            • C clickymcticker@hachyderm.io

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

                              christianrickert@23.socialC This user is from outside of this forum
                              christianrickert@23.socialC This user is from outside of this forum
                              christianrickert@23.social
                              wrote last edited by
                              #14

                              @ClickyMcTicker @nixCraft

                              Yeah, but your average parrot is not going to shuffle the layout of the runways while squawking to the pilots. 🦜

                              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

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