Find the money quietly leaking out of your AWS bill

#

Most of a startup’s AWS overspend has nothing to do with bad architecture. It is housekeeping nobody owns. A volume nobody deleted. A NAT gateway routing traffic that should have been free. Logs that never expire. None of it is dramatic, which is exactly why it survives.

This free field guide walks through the 17 leaks I run into most often. For each one you get where it hides, a read-only command to spot it in your own account in minutes, and the fix.

What is inside

#

• The 5 compute leaks that quietly inflate most bills: idle boxes, no Savings Plan, oversized instances, and two more.
• The storage and networking leaks nobody looks at, including the forgotten NAT gateway that costs more than most teams expect.
• A copy and paste read-only command for each one, safe to run against production today, because it only ever lists and describes and never changes anything.
• A rough euro tally so you can see what it all adds up to for a company your size.

Your email stays private. You get the guide, plus the occasional AWS note if you want it, and you can unsubscribe with one click anytime. See the privacy policy.

I am Hardik Mehta. I have spent 20 years building and running AWS platforms, including the streaming platform that put one of Germany’s leading film festivals fully online during COVID at roughly 6% of the festival budget, and a global manufacturer’s IoT platform where I led a cost reduction of around 30%. This guide is the short version of what I look for first.