I returned to AWS, and was reminded why I left

· cloud · Source ↗

TLDR

  • A 15-year AWS advocate returned briefly to test Bedrock and EC2 spot instances, got suspended for suspicious activity, and lost access to WorkMail for 4+ days with no support resolution.

Key Takeaways

  • Bedrock runs Claude but is slower and significantly more expensive than a direct Anthropic subscription; privacy benefit is real but cost is steep.
  • Account suspension triggered by a dormant account suddenly running a 192-core spot instance blocked all services including WorkMail, with support taking 3+ days and counting.
  • Egress pricing (9 cents/GB), DynamoDB billing surprises, and Lambda vendor lock-in are cited as structural cost and complexity traps.
  • AWS cloning Elasticsearch, Redis, and MongoDB into OpenSearch, Valkey, and DocumentDB forced defensive licenses (SSPL, Elastic License, RSAL) across the open-source ecosystem.
  • IAM complexity and hidden intra-service data-movement billing require dedicated expert staff to navigate safely.

Hacker News Comment Review

  • Commenters broadly agree AWS pricing UX is adversarial: instance launch flows historically omit prices, requiring cross-referencing separate spec and pricing tables simultaneously.
  • Elasticache drew specific criticism as pure margin capture: slower, less stable, and less configurable than a self-managed Redis install with zero added operational value.
  • A recurring counter-thread argued basic Linux sysadmin skills (systemd, reverse proxies) eliminate the need for most AWS abstractions, with several commenters reporting higher reliability after leaving.

Notable Comments

  • @djinn: Claims AWS has been systematically hollowed of technical staff since 2023 via layoffs and PIP cycles, warning to “use AWS at your own risk.”
  • @djyde: Traces a full Vercel -> Hetzner+Coolify migration arc, citing $20/month cost pressure even under 100 users as the trigger.

Original | Discuss on HN