May 10, 2026
Cloudy with a chance of drama
I returned to AWS, and was reminded why I left
AWS ex-fan says the magic is gone, and the comments turned it into a breakup roast
TLDR: A former AWS evangelist says Amazon’s cloud platform went from exciting to exhausting, blaming hidden costs, complexity, and lock-in. Commenters turned it into a roast-fest, joking about toxic exes, giant-company overkill, and whether the cloud was ever as magical as people claimed.
This wasn’t just a tech rant — it was a full-on public breakup story, and the crowd absolutely ate it up. The writer, once an early superfan who helped promote Amazon Web Services in Australia, says the romance died slowly: confusing bills, pricey data fees, nightmare permissions, and tools that felt way harder than they were supposed to be. In plain English, he’s arguing that a service sold as “easy mode” for running internet businesses became a maze where one wrong click can cost real money. His hottest line? If you’re not constantly thinking about hidden charges, “the stooge” might be you.
And the comments? Pure popcorn. One person turned the whole thing into a mock love song — “I love you baby, I need you! I’d never cheat on you!” — like AWS was an ex texting at 2 a.m. Another commenter seized on the “find the stooge” line and declared their quest complete, while others piled on with their own horror stories. One said every visit to AWS feels less like setting up a small hobby project and more like launching a new bank with venture capital and 1,000 staff. Ouch.
But there was also a mini civil war over whether cloud computing was ever that revolutionary in the first place. One skeptic basically asked, “Am I the only one who remembers virtual private servers?” Others compared Amazon’s tools to rivals and called Amazon’s setup process “hot garbage.” The vibe was clear: less starry-eyed future, more messy ex, giant bill, and everybody in the comments has receipts.
Key Points
- •The author says they were an early AWS advocate, helped organize an early AWS event in Melbourne, and remained strongly supportive of the platform for about 15 years.
- •The article claims the author’s dissatisfaction developed gradually through issues including missing official client libraries in AWS’s early years and delayed migration support from Python 2 to Python 3.
- •DynamoDB is cited as a negative experience, with the author stating they incurred a $75 USD bill in one day of use.
- •The article criticizes AWS pricing and operations, specifically data-egress charges and what it describes as complex billing for internal data movement.
- •The author argues that IAM and AWS Lambda add substantial complexity, with Lambda also described as a source of vendor lock-in, and concludes by criticizing AWS’s handling of open-source alternatives such as OpenSearch, Valkey, and DocumentDB.