Amazon Web Services – Four Years and Out

Amazon Web Services is portrayed as having shifted from its earlier reputation for customer focus and infrastructure innovation to a “Day 2” behemoth chasing GenAI hype, treating staff as fungible, and tolerating lower quality in both internal work and customer support. Commenters cite examples such as immature AI‑generated content in presentations, AI support bots giving wrong or low‑value answers, and an internal culture that prizes rapid product launches over real user needs. Many see these trends as part of a broader pattern of large tech firms enshitifying their services, eroding labor conditions, and risking long‑term decline in the pursuit of short‑term efficiency and shareholder value.

AWS culture, “Day 2,” and loss of customer focus

  • Many see AWS as past its peak; some date this to mid‑2010s, others to leadership changes and high‑profile departures.
  • Original core services (S3, EC2, SQS, VPC) are praised as true innovations; newer data and AI services are seen as MBA‑driven, scattershot bets.
  • Commenters argue AWS now floods the market with half‑baked products to see what sticks, echoing broader “enshittification” and late‑stage capitalism critiques.
  • Some still note AWS infra remains generally reliable and crucial, suggesting “IBM phase”: boring but important, with innovation energy gone.

GenAI pivot and quality degradation

  • Mandated GenAI use and AI‑generated slides/images with obvious errors are seen as anti–“customer obsession” and emblematic of organizational rot.
  • Several say GenAI amplifies laziness and produces “bullshit to answer bullshit,” degrading communication and software quality.
  • Others defend AI tooling as a productivity necessity; argue companies are rational to push rapid adoption, analogizing to CNC machines.

“Fungible” employees and labor anxieties

  • AWS (and big firms generally) are described as treating workers as interchangeable “cattle, not pets.”
  • Some argue large enterprises must assume replaceability, but that Amazon is unusually gleeful about it.
  • There’s extensive discussion comparing AI‑driven displacement to the Industrial Revolution, including fears of reduced labor leverage, social unrest, and violence; others push back that current white‑collar conditions are nowhere near historical atrocities.

Support, AI bots, and customer experience

  • Multiple anecdotes describe deteriorating AWS (and other vendors’) support: long delays, wrong answers, and obvious AI‑generated replies.
  • AI chatbots that merely regurgitate docs are widely disliked, especially when they replace escalation paths to humans.
  • Some concede that many tickets are basic and cost pressures are real, but argue AI systems should also know when to escalate.

Hiring, talent, and FAANG signaling

  • Mixed views on Amazon’s hiring: some say it’s a “golden age” for employers with many capable devs; others at AWS report open roles going unfilled and declining candidate quality.
  • FAANG experience is no longer universally seen as a strong signal; big‑company culture can be misaligned with smaller org needs.

Cloud history and alternatives

  • Debate over how revolutionary AWS was: some insist pre‑AWS VM hosting was already common and cheaper; others stress AWS’s API‑driven elasticity and integrated services as the real shift.
  • Several note many enterprises still provision on‑prem due to internal bureaucracy, not technical limits.

Avoiding faceless‑corp decay

  • Suggestions include limiting scale, focusing on craft, avoiding hype and VC pressure, and looking to niche exemplars (e.g., Costco, small artisan businesses) as models.