AWS Billing in Plain English: Free Tier, Budgets, and Traps

Welcome back to our free AWS learning series. Last stop — AWS IAM, the permissions office — ended with a promise: we'd finally read the bill itself. Here it is. Your AWS bill is a utility meter, not a phone plan: every service records what you actually used — hours, gigabytes, requests — and at the start of the next month AWS adds it up and charges your card. After the spending. Never before it. And the reveal this post is built around, the one that surprises everyone from students to CFOs: there is no spending cap. Nowhere in AWS is there a setting that says "never charge me more than ten dollars." Not hidden in billing preferences, not behind a support ticket — it does not exist. The tools AWS gives you are alarms, not brakes. The one exception is brand new: since July 2025, the free account plan literally cannot bill you — because when its credits run out, AWS doesn't send an invoice. It closes the account.

So this post does three jobs in plain English: how the meter works and where charges hide, what the new Free Tier credits actually cover (and the 90-day clock nobody reads about until too late), and how to set the alarm — free, five minutes — that emails you before a surprise grows teeth. Jake and Ethan will do the explaining, as always, because Jake just received his first uncensored AWS bill, and there's a line on it he never ordered.

The Line Item Jake Never Ordered

Quick recap for anyone joining mid-series: Jake runs a phone repair shop, his booking page lives on a micro EC2 instance with an 8 GB drive whose 64-cent rent he once tried to dispute, Ethan translates cloud things into shop things, and the root login has been in a drawer since the text message that was never sent. On the first of the month, Jake's bill arrived, and he read it the way everyone reads their first real cloud bill — line by line, out loud, with rising indignation.

The server rent: fine, roughly what the calculator promised. The famous drive: 64 cents, an old enemy, respected now. The S3 backups: pennies. And then — "Public IPv4 address … $3.65." Jake put the phone down. "Ethan. They're charging me for the address. Not the shop. The address of the shop. It costs more than the drive. It costs almost six times the drive."

Ethan didn't even look up. "The internet ran out of IPv4 addresses years ago. They're scarce, they cost real money to buy, and since February 2024 AWS charges half a cent an hour for every public one — about $3.65 a month, whether it's attached to something or just sitting there reserved. You're not paying for the shop. You're paying for the street number, because the city stopped printing street numbers." That line item is real, it lands on every bill with a public address on it, and it's the perfect introduction to how AWS billing actually thinks — because nobody clicks a button labeled "buy an IP address." You click "launch a server," and a dozen small meters start spinning quietly behind it.

The Missing Off Switch

Here is the mental model that makes everything else in this post click. Your phone plan is a contract: you agree to a price, and the price is the ceiling. AWS is a utility: the meter spins while you use things, the reading becomes an invoice, and the invoice becomes a card charge early the next month. Nobody asks permission at any point, because you already gave it — the same way the electric company doesn't call before billing you for the AC you ran in July.

Which leads to the question every newcomer eventually asks, usually at speed, usually after a scare: "Okay, where's the setting that caps my spending at $10?" And the answer — the honest, unpadded answer — is: there isn't one. It is not hidden. It does not require a support ticket. It has simply never existed. You can be alerted at $10 (next section, and you should be), and you can wire up automatic actions that stop some things, but there is no master valve that shuts the whole account at a dollar figure. AWS's design philosophy is that stopping your resources mid-flight — deleting a database at 2 a.m. because a threshold tripped — could hurt you worse than the bill. Reasonable for a hospital's infrastructure. Cold comfort for a student with a hijacked access key, which is exactly why the IAM post spent so long on keys, and why the alarm in this one is non-negotiable.

• The meter is per-service and per-unit. Compute bills by the hour or second, storage by the gigabyte-month, requests by the thousand. Your bill is just all the meters, added up.
• The charge arrives in arrears. You always find out what a month cost after the month happened. That delay is the whole reason surprises are possible — and the whole reason alarms matter.
• One genuine exception exists now: the post-2025 free plan, next section — the first AWS account in history with an actual off switch built in.

The New Free Tier: Credits, a Clock, and a Kind Ending

For years, "AWS Free Tier" meant a fiddly bundle of allowances — 750 hours of this, 5 GB of that, for 12 months — with real charges waiting quietly behind every limit you crossed. Whole support forums existed to console people who learned this the hard way. In July 2025, AWS retired that model for new signups and replaced it with something dramatically easier to reason about: money.

• Every new account starts with $100 in credits and can earn up to $100 more by finishing a short onboarding checklist — launch and terminate a server, try a database, deploy a function, test an AI prompt, and (savor this one) create a budget. The landlord pays you to install your own smoke alarm.
• At signup you pick a lane: free plan or paid plan. Same credits either way. The paid plan is a normal account — credits absorb charges first, your card catches whatever exceeds them. The free plan is the remarkable one: it cannot charge you. AWS's own wording is that a free-plan account "won't see any charges" on its bills. No meter reaches your card, because your card is never in the line of fire.
• The catch is a clock, not a charge. The free plan lasts up to six months, or until the credits run out — whichever comes first. Then AWS doesn't bill you; it closes the account. Your data is kept for 90 days, during which you can upgrade to the paid plan and walk back in like nothing happened. After 90 days, the account and everything in it are permanently erased. For a learning account, honestly, that's a kind ending — the worst-case outcome of the old free tier was a bill; the worst case of the new one is a clean goodbye. Just don't keep anything in there you'd cry about, or set a calendar reminder for month five.
• The "always free" layer survives on both plans: 30-plus services with permanent monthly allowances that never expire. And if your account predates July 15, 2025, none of this applies to you — you're grandfathered on the old 12-month structure, allowances, traps and all.

One editorial note, because this series has marked a bill trap in every single post: the new free plan deserves real credit. "You cannot be charged, and the worst case is account closure" is the consumer protection people begged AWS for over a decade — it just arrived attached to a six-month clock instead of a settings toggle.

Where Charges Hide

Every surprise bill in cloud history comes from the same root cause: a meter kept spinning after the person stopped looking at it. The repeat offenders, ranked by how often they ambush people:

• The stopped-but-not-gone server. The series classic, from the EBS post: stopping an instance stops the compute meter, but the drive underneath is a rented shelf, and shelves bill whether the computer on them is awake or not. Terminate the instance and delete unneeded drives and old snapshots, or the shelf rent runs forever.
• The address you're not using. Public IPv4: $0.005/hour, ~$3.65/month, per address, on every service, attached or idle — since February 2024. A reserved Elastic IP sitting unattached is the purest form of this: paying rent on a street number for a demolished building.
• Data leaving the building. Data going into AWS is free; data going out to the internet is free for the first 100 GB a month, then roughly nine cents a gigabyte in US regions. Small for a booking page; the reason cloud-hosted video sites sweat.
• The other region. The console shows one region at a time. A server launched in Ohio during a tutorial keeps billing invisibly while you stare at Virginia. If a bill line mystifies you, check the region column first — it's the "look behind the couch" of cloud billing.
• The experiment that worked. Nobody forgets to delete the thing that crashed. The dangerous resource is the one that ran perfectly the night you got it working and never crossed your mind again. (Jake, reading this section: "So the bill is basically a museum of things I was once excited about." Ethan: "With admission charged monthly.")

Budgets: The Smoke Alarm

Now the defense. AWS Budgets lives in the Billing console, and the concept fits in a sentence: draw a line, and AWS emails you when spending crosses it. A budget of $10 with alerts at 50% and 100% means one email when the month passes $5 — your early warning, while a surprise is still pocket change — and another at $10. Better still, budgets can alarm on forecasted spending: AWS watches the pace of the month and warns you it's heading over the line before it gets there. That forecast email is the single highest-value notification in all of AWS.

• It's free where it matters. Alert-only budgets cost nothing, and each carries up to five alerts. Budgets that trigger actions are free for the first two, then about a dime a day — but a personal account needs exactly zero of those to start.
• There's a template for "any spend at all." The zero-spend budget emails you the moment the account's spending exceeds a few cents — perfect for a legacy free-tier account or any account that's supposed to cost nothing. It answers the question "is anything in here charging me?" permanently, by email.
• Actions exist, for when alarms aren't enough. A budget action can stop specific EC2 or RDS instances, or snap a deny-everything policy onto a user — the IAM veto, pulled by a tripwire. It's a partial brake, not a cap (more honesty below), but for "my test server must never run all weekend," it's exactly the tool.
• And the meta-endorsement: AWS pays new free-plan accounts credits for creating a budget. When the company that profits from the meter pays you to install the alarm, believe both halves of the message.

What Budgets Will Not Do for You

Fair warnings, in the spirit of the series:

• They won't stop the spending. Worth repeating once, plainly: a budget is a smoke alarm, not a sprinkler system. It tells you something is burning. It does not put the fire out. You do — by signing in and terminating what's spinning.
• They run on delayed film, not live TV. AWS refreshes billing data a few times a day, so an alarm can trail reality by eight-ish hours. A slow leak — the forgotten server, the orphaned drive — gets caught beautifully. A stolen access key mining crypto at full throttle can outrun the email, which is why key hygiene lives in the IAM post and not here.
• Actions cover some meters, not the bill. Stopping instances halts compute; storage, addresses, and data transfer keep ticking until a human cleans up. No action deletes your data for you — deliberately.
• They won't refund the surprise. Though here's the part people don't know: for a first genuine accident, AWS support forgives far more often than folklore suggests. Open a support case, be honest, show you've fixed the cause (key deactivated, budget now set). The person reading your case has seen a thousand of these. No promises — but it costs nothing to ask, and first-timers are treated kindly surprisingly often.

Try It Yourself in Ten Minutes

Today's lap is the cheapest possible kind: it's about not spending. Sign in (as your IAM user — the root login stays in its drawer) and open Billing and Cost Management from the console search bar. First, read your own bill: Bills in the left menu, current month, expand every service showing more than $0.00 — this is where Jake found his $3.65 tenant, and five minutes here teaches more than any diagram. Second, install the alarm: Budgets → Create budget. The template gallery is genuinely good — take the zero-spend budget if this account is supposed to cost nothing, or a monthly cost budget one notch above what you consider normal (Jake set $15), type the email address you actually read, and create. Third, if your account is on the new free plan: check the Explore AWS credit activities — you may earn $20 in credits for the budget you just made, which means this section had a negative price. Then close the laptop. The chai is, as ever, mandatory — today it tastes like a bill you'll never be surprised by.

Questions People Actually Ask

Does AWS have a spending limit I can set?

No — and it's the most important fact on this page. Budgets alarm when spending crosses your lines, and budget actions can stop specific instances, but no setting caps the bill itself. The single exception: the new free account plan can't charge you at all — when its credits end, AWS closes the account instead of billing it.

How does the AWS Free Tier work now?

Since July 15, 2025, new accounts pick a free or paid plan, both starting with $100 in credits — up to $100 more for finishing onboarding activities, one of which is literally creating a budget. The free plan runs six months or until credits run out. Thirty-plus always-free services continue on both plans, and pre-2025 accounts keep the old 12-month structure.

Can the AWS free plan charge my card?

No. AWS's own line is that a free-plan account won't see charges on its bills. When credits or the six months end, services stop and the account closes — no invoice. It's the first AWS account with a real off switch, which is why this series, which marks a bill trap in every post, is giving the new plan an honest compliment.

What happens when my AWS free plan expires?

The account closes, and AWS keeps your data for 90 days. Upgrade to the paid plan within that window and everything reopens intact; let it lapse and the account and its contents are permanently erased. Set a reminder for month five, and don't store anything precious in a free-plan account.

What is AWS Budgets, and is it free?

The bill's alarm system: draw a line, get emailed when actual or forecasted spending crosses it. Alert-only budgets are free (five alerts each); action-enabled budgets are free for the first two, then about a dime a day. A personal account needs one free budget and zero excuses.

Why is AWS charging me for a public IPv4 address?

Because the internet ran out of them. Since February 1, 2024, every public IPv4 address costs $0.005 an hour — about $3.65 a month — attached or idle, on every service. On a small bill it's often the biggest head-scratcher line, sitting there costing six times the drive.

Why does a stopped EC2 instance still cost money?

Stopping halts the compute meter, but the EBS drive underneath is a rented shelf that bills on or off, and a reserved Elastic IP keeps charging while idle. Zeroing out a machine means terminating it and deleting the drives and snapshots you no longer need — the shelf, not just the computer.

Will a budget stop AWS from charging me?

No — smoke alarm, not sprinkler. It reports the fire; you put it out. Billing data also trails reality by hours, so a fast surprise can outrun the email — the slow leaks are what budgets catch brilliantly. Budget actions add a partial brake (stopping instances, clamping permissions), but most meters run until you clean up.

What is next in this series?

Lambda — the computer that only exists while it's running. After a post full of meters that spin while you sleep, meet the service whose meter genuinely reads zero when nobody shows up: code that appears for a customer, runs for milliseconds, bills for milliseconds, and vanishes.

If You're Here for the Certification

The standing reminder, since this series grew out of our AWS certification learning series: billing and cost management is the Cloud Practitioner exam's favorite corner — a full exam domain — and it recurs on the associate exams dressed as scenarios. The bank of questions is exactly this post's furniture: "a company wants to be notified before monthly costs exceed a threshold" (AWS Budgets, forecast alert), "which tool visualizes historical spending?" (Cost Explorer — the graphs living one menu below Budgets), "can you cap AWS spending at a fixed amount?" (no — and now you know it deeply enough to explain why), and "what keeps charging after an instance stops?" (the shelf, the address, the snapshots). You can answer all of them from a story about a $3.65 street number. If you're planning a booking, check the AWS certification changes post first — 2026 moved deadlines that decide which exam version you should even sit.

Published August 2026. Part of the free AWS learning series — previous stop: What Is AWS IAM? Cloud Permissions in Plain English. I hope you learned something new! See you in next post.