Dear AWS, please let me be a cloud engineer again

Original Article ↗ Hacker News Discussion ↗

AWS’s heavy pivot toward generative AI — especially at events like re:Invent and re:Inforce — is frustrating engineers who feel core cloud infrastructure and “boring” but essential improvements are being neglected. Commenters argue that management chases AI hype to impress executives and investors, even though many GenAI tools are immature, hard to secure, or add complexity without clear benefit. Others note this pattern mirrors earlier tech fads: underlying cloud services and traditional engineering skills remain critical, but vendors market higher-margin AI offerings to climb the value stack and avoid being seen as laggards.

AWS’s GenAI Pivot and Branding

  • Many see AWS’s GenAI offerings (e.g., Bedrock, “FM” terminology) as muddled and overly buzzword-heavy; their differentiation vs. Azure/OpenAI and Google is unclear.
  • Conferences (re:Invent, re:Inforce, regional summits) are perceived as dominated by GenAI branding, even when the technical content is more mixed.
  • Several argue AWS is selling an AI story to CIOs/CEOs, not engineers, because “Generative AI” is the signal leadership and stock markets respond to.

Impact on Traditional Cloud Engineering

  • Concern that budgets and engineering attention are being diverted from “boring” but vital infra: IAM consistency, IPv6, ALB/API Gateway integration, VPC gaps, homogeneity, cost optimization.
  • Some fear slower improvement of core services and more brittle architectures, as engineers hack around missing features while AWS chases AI.
  • Others reply that many non‑AI sessions still exist and GenAI will eventually become just another tool in the stack.

Leadership, Incentives, and Hype Cycles

  • Commenters link the AI push to leadership incentives: career upside for “AI wins,” little downside for neglecting maintenance.
  • Debate whether this reflects incompetence (“leaders are dumb”) or rational self-interest under current incentives.
  • Parallels drawn with previous hype waves (big data, blockchain, serverless, Kubernetes) that eventually normalized.

Usefulness and Limits of GenAI

  • Experiences are mixed: some report real productivity gains (e.g., code generation, log/security report summarization), others see unreliable, unsafe, or superficial outputs.
  • A recurring theme: current tools often look impressive until scrutinized by subject-matter experts.

Job Impact and “Prompt Engineering”

  • Some predict cloud/solutions engineers are especially exposed to automation (LLMs generating IaC from natural language).
  • Others counter that existing tools in this space are not production-grade and still require experts.
  • “Prompt engineering” is debated: dismissed by some as rebranded “talk clearly to the tool,” defended by others as a genuine skills layer for reliably controlling non‑deterministic systems.

Cloud Business Economics and Strategy

  • Several argue AWS’s profits come more from higher-level managed services (databases, AI, analytics) than raw compute/storage; AI fits this margin strategy.
  • Others note big AI bills (GPUs, training workloads) but question whether GenAI is yet more than FOMO and high-markup GPU resale.