How to Set Up AWS Billing Alerts So You Never Get a Surprise Bill

Set up two things in the AWS Billing console — a $0 (or low-dollar) AWS Budget with an 80% alert, and a billing alarm in CloudWatch — and AWS will email you the moment your spending starts drifting, long before the invoice arrives. It takes about fifteen minutes, it costs nothing, and it is the single cheapest insurance policy any AWS account can have. The steps below walk through both, plus the one setting most people forget that makes alerts actually work.

AWS bills are famously quiet until they are not. A forgotten EC2 instance, a test database left running, an S3 bucket filling up with logs — each one is a few dollars a day, and each one is invisible until the month ends and the invoice lands. The stories of $1,000 surprise bills all share the same root cause: nobody was watching the meter. Billing alerts are how you watch it without thinking about it.

What Are AWS Billing Alerts, Exactly?

AWS billing alerts are email notifications triggered when your spending crosses a threshold you choose. They come in two forms, and you want both, because they catch different problems.

AWS Budgets let you set a spending limit — say $50 a month — and AWS emails you when your actual or forecasted cost crosses 80%, 100%, or any percentage you pick. Budgets are the main tool: they understand your services, they can forecast, and they send the alert before you cross the line.

CloudWatch billing alarms are the older, simpler mechanism. They watch a single metric — your estimated charges — and fire when it passes a dollar amount. They are less flexible than Budgets, but they are a good backup because they fire on raw spend regardless of how your budget is configured.

Together they cost nothing extra. AWS Budgets are free for the first two budgets per account, and CloudWatch billing alarms are free within the basic monitoring tier. There is no reason any account should run without them.

Step 1: Turn On Billing Alerts (The Setting Everyone Misses)

Before anything else, enable billing alerts on the account. This is the step people skip, and then they wonder why no alert ever arrives.

1. Sign in to the AWS Management Console with the root account (or an IAM user with billing permissions).
2. Click your account name in the top right, then choose Account (or Billing Dashboard).
3. Under Billing preferences, find Alert preferences and check Receive Billing Alerts — or, on newer consoles, toggle Billing alerts to Enabled.
4. Save.

This setting is off by default on many accounts, and it is per-account, not per-user. If you created the account and never touched this page, your alerts are off. Do this first, then move on — every step below depends on it.

One more thing to check on the same page: confirm the email address AWS will send alerts to. AWS sends billing alerts to the root account’s email by default. If that inbox is one nobody checks, add a second recipient in the Budgets setup below, or set up an email rule that forwards AWS billing messages to the person who actually manages the account.

Step 2: Create Your First AWS Budget

Now create the budget that will watch your monthly spend:

1. Go to the AWS Billing console and choose Budgets in the left menu.
2. Click Create budget.
3. Choose Cost budget (the default) and click Next.
4. Set the Budget period to Monthly.
5. Set the Budget amount. If your normal bill is $30 a month, set the budget to $40 — close enough to catch real drift, far enough from your normal spend to avoid noise.
6. Under Budget scope, leave it as All services for your first budget. You can add service-specific budgets later.
7. Add two alert thresholds: 80% of budgeted amount, Actual cost — the early warning; and 100% of budgeted amount, Forecasted cost — the “you are on track to blow the budget” warning.
8. Enter the email address (or addresses) that should receive the alerts.
9. Review and click Create budget.

That is the whole setup, and it is enough for most accounts. But there is one improvement worth making immediately: set the 80% alert on actual cost and the 100% alert on forecasted cost. The forecasted alert is the clever one — AWS projects your month-end total from your spending so far, so it can warn you on the 10th that you are heading for a $90 month when your budget is $50. That gives you three weeks to fix it instead of three days.

Step 3: Add a CloudWatch Billing Alarm as a Backup

Budgets are excellent, but they can be slow: a budget alert fires once a day when AWS updates its cost data. A CloudWatch alarm on estimated charges checks more frequently and catches a sudden spike — a runaway instance, a misconfigured auto-scaling group — hours earlier.

1. Go to the CloudWatch console and switch the region to US East (N. Virginia) — billing metrics only live in us-east-1, even if your workloads run elsewhere.
2. In the left menu, choose Alarms, then Create alarm.
3. Click Select metric, then browse to Billing → Total Estimated Charge, and select the EstimatedCharges metric with Currency = USD.
4. Set the condition: Greater than your threshold — for example, $60 if your budget is $50.
5. Set the period to 6 hours (the billing metric updates roughly every six hours).
6. Under Notification, create or select an SNS topic and add the email address that should get the alert. Confirm the subscription email SNS sends you — the alarm will not reach you until you do.
7. Name the alarm something obvious, like `billing-over-60-dollars`, and create it.

Test it once: temporarily set the threshold below your current month-to-date spend and confirm the email arrives, then set it back. An alert you have never seen fire is an alert you cannot trust.

Step 4: Set Up AWS Cost Anomaly Detection (Free, and Worth It)

AWS Cost Anomaly Detection watches your spending patterns and alerts you when something looks unusual — a service that suddenly costs three times its normal amount, for example. It is the tool that catches the problems a fixed budget cannot, because it notices changes rather than totals.

1. In the Billing console, choose Cost Anomaly Detection.
2. Click Create monitor and choose AWS services monitor (the default covers everything).
3. Set the alert threshold — $10 or 10% above normal is a good starting point for a small account.
4. Add the email recipient and create the monitor.

Anomaly detection takes a few days to learn your baseline, so do not expect alerts in the first week. After that, it is the quietest, most useful alert you will ever set up — it only speaks when something is genuinely wrong.

The $0 Insurance Policy: Five Habits That Make Alerts Work

Alerts alone do not prevent surprise bills — they only tell you something is wrong. These five habits turn the alerts into real protection:

1. Check the Billing Dashboard every Monday. Two minutes, once a week. Look at the month-to-date total and the top three services. You will spot drift before any alert fires.
2. Tag everything you create. A resource without a cost-allocation tag is a cost you cannot attribute. When an alert fires, tags tell you who or what caused it.
3. Delete what you are not using. Old snapshots, unattached EBS volumes, idle load balancers, and forgotten test instances are the most common surprise-bill ingredients. A monthly cleanup of the obvious ones takes ten minutes.
4. Use the AWS Free Tier alerts. If you are on the Free Tier, AWS can alert you when you approach a free-tier limit — enable this in the Billing preferences page, right next to the billing alerts setting.
5. Never ignore the 80% alert. Treat it like a smoke alarm. The 80% alert exists so you have time to act; if you wait for the 100% alert, you are already paying.

What to Do When an Alert Fires

Getting the email is the easy part. Here is the five-minute drill for the moment it arrives:

1. Open Cost Explorer (Billing console → Cost Explorer) and look at the cost by service for the last seven days. The service that spiked will be obvious.
2. Check the last 48 hours by day. Cost Explorer’s daily view shows exactly when the spike started.
3. Find the resource. If EC2 spiked, check the EC2 console for running instances you do not recognise. If S3 spiked, check for a bucket growing fast. If data transfer spiked, look for a public-facing service moving unusual volumes.
4. Stop or resize it. Terminate the forgotten instance, delete the unattached volume, or turn down the service. You can investigate the root cause afterwards — stopping the spend comes first.
5. Raise or adjust the alert if the spend was legitimate. If you launched something on purpose and the budget was simply too low, update the budget so the next alert means something.

I ran this drill myself the first time an anomaly alert fired on a test account: Cost Explorer showed EC2 costs had doubled overnight, the daily view pointed to a single day, and the EC2 console showed a t3.large I had launched for a benchmark and forgotten to stop. From alert to terminated instance took four minutes. The bill that month was $18 instead of the $60 it was heading for — and that was a test account with almost nothing in it.

FAQ

Are AWS billing alerts free?

Yes. The first two AWS Budgets per account are free, CloudWatch billing alarms fall within the free monitoring tier, and Cost Anomaly Detection is free. There is no charge for the alerts themselves, and no reason to skip them on cost grounds.

Why didn’t I get a billing alert when my bill was high?

The most common cause is that billing alerts were never enabled in Billing preferences — the setting is off by default on many accounts. The second most common cause is that the alert email went to the root account’s inbox, which nobody checks. Enable the setting, confirm the recipient address, and add a second recipient in the budget setup.

What is the difference between AWS Budgets and CloudWatch billing alarms?

AWS Budgets track your spending against a limit you set and can alert on forecasted costs — they warn you before you cross the line. CloudWatch billing alarms watch the raw estimated-charges metric and fire when it passes a dollar amount. Budgets are the smarter tool; alarms are the faster backup. Use both.

Can I set billing alerts for a specific AWS service?

Yes. When you create a budget, use the Budget scope options to filter by service — for example, a $20 budget for EC2 alone. Service-specific budgets are useful when one service is the usual culprit: set a tight budget on it and a looser one on the account overall.