Comment

Comment on What if rogue Ai agents or other bad actors take over these 2?

How exactly would an AI agent “take over” AWS or Cloudflare? That doesn’t even make sense.

The whole purpose of cloudflare is literally to take a shitload of traffic, your quote from wherever it’s from is just describing Cloudflare working as intended? The only thing happening here is customers getting bigger bills

For anything external to “take over” AWS in any remotely meaningful way, AWS would have to have a long cascade of internal fuck-ups so all-encompassing, that it’s kinda unfathomable.

source

Sort:hotnew top

fartzo@lemmy.dbzer0.com ⁨21⁩ ⁨hours⁩ ago
I assumed it was saying that 60% of traffic seen by cloud flare was AI scrapers. Which is believable TBH.

source
- 9point6@lemmy.world ⁨20⁩ ⁨hours⁩ ago
  Yeah that’s kinda what I’m saying, cloudflare is a CDN, handling a lot of traffic is the point of it. It’s a pretty big stretch to link that to AI “taking over” it. Heavily using it perhaps, as I insinuated with customers getting bigger bills
  
  source
The__Leaker@lemmy.world ⁨1⁩ ⁨day⁩ ago
Ai coding bots caused at least two minor internal outages at AWS in late 2025. Not the same as agents but you get it.

source
- 9point6@lemmy.world ⁨1⁩ ⁨day⁩ ago
  AI being associated with those issues is kinda secondary (and cynically, scapegoating to dodge scrutiny). It was ultimately engineers shirking the responsibility of their jobs and not checking their work that caused the issues. If someone wants to tell an agent to fuck around with production and not check what is about to be deployed first, that’s the engineer being a negligent dumbass, not any kind of malicious AI
  
  And unless Amazon wants to lose significant amounts of business due to that becoming a repeat occurrence, they will have already put safeguards in place to make sure engineers do their jobs in future.
  
  source
  - The__Leaker@lemmy.world ⁨1⁩ ⁨day⁩ ago
    True. Usually it is the humans fucking up.
    
    source