Anatomy of a $340 Oops: We Rebuilt Every 'Free Tier' Mistake That Drained One Developer's AWS Account
Photo: Vitaly Zdanevich, CC0, via Wikimedia Commons
The Email That Ruined a Saturday
Marcus (not his real name, but his bill is very real) is a backend developer in Ohio who signed up for AWS to host a side project — a small API for his rec-league softball team's stat tracker. He read enough of the Free Tier page to feel confident. Twelve months free. 750 hours of EC2. What could go wrong?
Three months later: $340.17.
We asked him to share the itemized bill, then did what we do at FreeServerHost — we spun up a sandbox account and recreated every single line item to figure out how a 'free' tier produces a four-figure-level surprise. Here's the full forensic breakdown.
Line Item One: The Load Balancer That Ate $94
The biggest single charge on Marcus's bill was an Application Load Balancer he'd provisioned during a weekend of experimenting with HTTPS, then completely forgot about.
Here's the trap: ALBs are not in the free tier. Ever. They cost roughly $16–20/month base, plus per-LCU usage fees, and they bill continuously whether they're routing traffic or sitting idle. Marcus's load balancer hummed along for 74 days serving approximately zero requests.
We reproduced this in our sandbox: created an ALB, walked away, checked back. Yep — the meter never stops. And because a load balancer produces no logs or notifications by default, there's nothing telling you it exists.
Line Item Two: Egress Overruns ($71 and Climbing)
Data transfer in is free. Data transfer out is where cloud providers make their money, and the free tier only includes a small monthly allowance — 100GB on the current model, less under the old one.
Marcus's stat tracker had a bug: a mobile client polling the API every two seconds, even when the app was backgrounded. Multiply a chatty polling loop by 30 days and you've blown through the free egress allowance before the second week.
Our sandbox replication confirmed it: a simple polling endpoint at aggressive intervals generated measurable egress within hours. Imagine what a viral week does.
Line Item Three: The NAT Gateway — $112 of Doing Nothing
This is the one that made us wince. Marcus, following a tutorial for 'production-grade' VPC setup, created a NAT gateway so his private-subnet instances could reach the internet.
A NAT gateway costs about $32/month just to exist, plus per-GB processing charges. It is never free. It doesn't care that your EC2 instance is t2.micro with 4% CPU utilization. It bills like a Manhattan parking spot — constantly, regardless of use.
Marcus's single NAT gateway plus its data processing fees accounted for a third of his bill. Our sandbox showed the same thing: create it on day one, and you're already $1/day in the hole before you've deployed anything.
The Smaller Landmines
The rest of the bill was a greatest-hits collection of gotchas:
- Elastic IPs not attached to running instances — a few dollars an hour, forever
- Extra EBS volumes from snapshots taken 'just in case'
- A second EC2 region where he'd launched a test instance and never terminated it
- CloudWatch custom metrics at detailed monitoring rates
None of these individually break the bank. Together, they're the compounding interest of cloud computing.
How to Actually Stay at $0
After recreating every mistake, here's the checklist we'd hand to anyone touching a free tier:
- Set a billing alarm at $1. Not $50. One dollar. It's the single highest-leverage five minutes you'll spend.
- Enable AWS Budgets with email alerts at 50% and 100% of your $0 threshold.
- Never create a load balancer or NAT gateway on a free tier account. Use a free host's managed HTTPS or a tunnel instead.
- Audit your region list. Check for orphaned resources in us-west-2 you forgot about because you 'live' in us-east-1.
- Fix chatty clients. Polling every two seconds is an egress bomb waiting for a deadline.
- Terminate, don't just stop. Stopped instances still bill attached EBS volumes and elastic IPs.
- Review the bill weekly for the first month. Surprise charges compound fast.
The Honest Takeaway
AWS's free tier is genuinely generous for what it's designed for: learning, experimenting, prototyping. The problem is that it's designed like a casino — the expensive stuff is one click away, unmarked, and the meters run silently in the background.
Marcus paid his $340, learned his lesson, and moved his softball API to a genuinely free PaaS with hard spending caps. It's been $0.00 for six months running. Sometimes the cheapest cloud is the one that can't charge you at all.