You’re in a meeting when a misconfigured Lambda starts spinning up thousands of invocations. AWS Budgets sends an alert to the email address you registered three years ago — the one that filters AWS notifications into a folder you check on Fridays. By the time you see it, the bill is $400 higher than it should be.
This is how most AWS cost surprises play out. Not because alerts weren’t configured, but because the alert sat in an inbox nobody was watching.
Why AWS Budgets Alone Isn’t Enough
AWS Budgets does what it promises: it monitors your spending and sends notifications when thresholds are crossed. The problem isn’t the monitoring — it’s the delivery.
Email goes to spam. Budget alert emails come from budgets@costalerts.amazonaws.com. Gmail, Outlook, and most corporate filters treat these as promotional or low-priority. AWS community forums on re:Post are full of posts from people who never saw their alerts because the emails were silently filtered.
Billing data is delayed. AWS Budgets refreshes data up to 3 times per day, with updates typically arriving 8–12 hours after the previous refresh. There can be a billing delay of up to 24 hours between when a charge is incurred and when a budget alert fires. That Lambda running wild at 2 AM? You might not get the alert until the next afternoon.
No push to your lock screen. Even if the email arrives on time and avoids your spam filter, it sits passively in your inbox alongside newsletters and meeting invites. You have to go looking for it. There’s no tap on the wrist, no sound, no banner on your lock screen while you’re walking the dog.
How to Set Up AWS Budget Alerts (The Right Way)
Open the AWS Console, navigate to Billing & Cost Management → Budgets, and create a cost budget. The setup is straightforward, but the threshold strategy matters more than most people think.
Don’t create 10 thresholds. Create 3 or 4 that actually mean something:
| Threshold | Type | Purpose |
|---|---|---|
| 50% | Actual | Early awareness — spending is on track or not |
| 80% | Actual | Warning — time to investigate if unexpected |
| 100% | Actual | Critical — budget exceeded, take action |
| 90% | Forecasted | Predictive — AWS projects you’ll exceed budget this month |
ACTUAL alerts fire after the spend has already happened. FORECASTED alerts fire when AWS predicts you’ll exceed the threshold by end of month, based on your spending pattern. Forecasted alerts need roughly 5 weeks of historical data before they start working, so set them up early.
Because of the 24-hour billing lag, set your budget amount below your actual pain point. If $1,000 is your real limit, set the budget to $800. This gives you a buffer between when the alert fires and when the spending actually happened.
Each budget supports up to 10 alert thresholds, with up to 10 email addresses and 1 SNS topic per alert. For Slack notifications, connect the SNS topic to AWS Chatbot — it supports Slack, Chime, and Teams. The first 2 budgets per account are free; each additional budget costs ~$0.62/month.
One thing AWS Budgets will never do: stop the charges. It notifies. That’s it. AWS keeps billing past the threshold. The alert is your signal to act, not a circuit breaker.
Add Cost Anomaly Detection (It’s Free)
AWS Cost Anomaly Detection is the complement Budgets can’t be. Where Budgets watches thresholds you defined, Anomaly Detection uses machine learning to catch spending spikes you didn’t anticipate — a service you forgot about, a region you didn’t know was active, a config change that tripled your data transfer.
Enable it in the AWS Console under Cost Explorer → Cost Anomaly Detection. Create a monitor scoped to your account or to individual services. There’s no cost to enable it — it’s a genuinely free service.
Anomaly Detection doesn’t replace Budgets. A budget tells you “you’ve spent 80% of your $500 limit.” Anomaly Detection tells you “your CloudWatch spend jumped 300% compared to your normal pattern.” You want both.
The Missing Piece: Alerts on Your Lock Screen
You’ve now set up Budgets with smart thresholds and Anomaly Detection for unexpected spikes. The monitoring is solid. The notification channel is not.
Every alert still arrives as an email — or at best, a Slack message in a channel with 200 unread messages. When a cost spike happens at 11 PM on a Saturday, you won’t see it until Monday morning. When it happens during a meeting, you won’t see it until the meeting ends and you remember to check.
Push notifications to your phone’s lock screen change this fundamentally. Your phone is the one device you always have, always check, and always respond to. A budget alert that appears as a banner on your lock screen while you’re grabbing coffee gets seen in seconds, not hours.
How CostPulse Fills the Gap
CostPulse connects to your AWS account and converts budget alerts and anomaly detections into native iOS push notifications. The same alerts that would sit in your email land on your lock screen instead.
- Native push notifications — budget thresholds and anomaly warnings appear as iOS notifications with sound and badges, not buried in email
- Anomaly detection alerts — ML-powered cost spike detection pushed directly to your phone
- Budget tracking with configurable thresholds — set limits per account and get notified before you exceed them
- Multi-account support — monitor up to 3 AWS accounts from a single app
- No credentials shared — one CloudFormation stack deploys least-privilege IAM roles. No access keys, no secrets
- Setup in under 2 minutes — tap one link to deploy the stack, slide to confirm your account
Free plan includes 1 AWS account with the full cost dashboard. The Plus plan ($4.99/month) adds budgets with push alerts, anomaly detection, and home screen widgets.
Quick Setup Checklist
AWS-native setup:
- Create a cost budget in Billing & Cost Management → Budgets
- Set thresholds at 50% (info), 80% (warning), 100% (critical), 90% (forecasted)
- Set the budget amount below your real limit to account for 24h billing lag
- Add your email and/or an SNS topic to each alert
- Enable Cost Anomaly Detection in Cost Explorer → Cost Anomaly Detection
- Create an anomaly monitor scoped to your account
Push notifications via CostPulse:
- Download CostPulse from the App Store
- Link your AWS account (one CloudFormation stack, no credentials)
- Configure budget thresholds in the app
- Enable push notifications in iOS Settings → CostPulse
Start Getting Alerts That Actually Reach You
The best cost alert is the one you actually see. Download CostPulse and set up push notifications for your AWS spending in under two minutes — free plan included, no credit card required.