I read the viral "leaving AWS" post twice.

AWS FOR THE REAL WORLD

⏱️

Reading time: 12 minutes

🎯

Main Learning: Most of the complaints in the viral "leaving AWS" post are skill issues — but egress pricing is a fair hit.

📝

Blog Post

Hey Reader 👋🏽
Recently, a post with the title "I returned to AWS and was reminded why I left" hit 810 upvotes on Hacker News last week and went pretty viral with it.
I read it twice before forming an opinion. My honest take: most of the complaints are skill issues! 🤷‍♂️
Nevertheless, the post is well written and I really couldn't stop myself from writing a detailed response about why most of it reads like someone used AWS the "wrong way" and blamed AWS for the outcome.
In this issue, I go through all the complaints one by one. Most things I disagree with while one is definitely legit.

At the end I explain the pattern I see across all of them 🫡

Find your Terraform maturity stage in 30 minutes.

Spacelift's free guide walks platform teams through the three maturity stages of running Terraform at scale. Spot which one you're stuck in.

Grab the free guide →

Spacelift is an infrastructure orchestration platform for Terraform, OpenTofu, Pulumi, CloudFormation, Ansible, and Kubernetes. Used in production at Duolingo, Figma, and 1Password.

This issue is sponsored by Spacelift.

A massive sledgehammer hitting a tiny thumbtack

📚 This Week's Deep Dive

A post about leaving AWS hit 810 upvotes on Hacker News last week. The frustration in it is real and the writing is sharp. But most of the ten complaints disappear the moment you look at how the platform is actually supposed to be used.

A few of the author's takes and the short version of why I disagree:

On IAM

"IAM — the hideously complex auth and access rules system. This was invented by Lucifer sitting on his burning throne in the ninth level of Hell as the worst possible torment for those who have been sent below for using AWS."

The core model is three questions: who, what action, on which resource. Lucifer's off the hook.

On DynamoDB

"DynamoDB what a hot pile of garbage. I tried it and ended up with a $75USD bill by the end of the day."

I ran DynamoDB for a million users on a few hundred a month. The difference between that and $75-in-a-day is whether you run full-table Scans.

On Lambda

"There's simply no genuine benefit to AWS Lambda compared to running your own web servers… Keep convincing yourself that using AWS Lambda is not a horrible mistake."

On event-driven workloads, "horrible mistake" is the wrong framing. Cold starts are well under 0.1% of invocations in production.

🚀 Read the full version of all ten points →

📰 This Week in AWS

🚀OpenSearch Serverless next-gen is GA

Scale-to-zero pricing replaces the old cluster-provisioning model, with up to 60% savings on spiky workloads and 20x faster scaling. The first time OpenSearch fits agentic-AI traffic patterns instead of fighting them.

🔧Bedrock exposes mantle quotas through Service Quotas

The bedrock-mantle endpoint (where OpenAI and Anthropic APIs run on Bedrock) now reports per-model token quotas via Service Quotas. Same surface as bedrock-runtime, so you can spot rate limits before prod traffic hits them.

That's it for this issue!
If you take one thing away: use the right tool for the right job. AWS is built for production at scale through IaC and you should know what you're doing. It's not the best "weekend hobby project platform" - we can be honest about that 😬

See you in the next one!

Sandro & Tobi

AWS for the Real World