AWS now has four cost controls that sound alike and behave very differently. Budgets alert, budget actions apply a policy or stop EC2 and RDS instances, Cost Anomaly Detection flags unusual spend, and spend limits pause an entire project at a hard cap. What each one actually stops, how fast, and where each fits.
What separates them is whether anything stops. Three of these controls tell you, or take a narrow action. Only a spend limit guarantees the bill can't pass a number, and it does so by taking everything offline.
Spend limit behaviour from the AWS team's AMA answers, November 2026; the rest from AWS Budgets and Cost Anomaly Detection documentation.
Learning, side projects and AI experiments in a new account: a spend limit. An outage is cheaper than a surprise bill.
Production: budgets for alerts, Cost Anomaly Detection for the unexpected, and budget actions that deny launching expensive resources rather than stopping running ones.
Sandboxes in an organization: one account per sandbox, with budget actions applying a deny-everything service control policy at the limit.
Any account: no long-lived access keys and MFA on the root user, because the costliest runaway bills start with stolen credentials.
We'll review your accounts and set alerts and actions that stop the expensive mistakes without stopping production. 30 minutes, free.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Building Your Own Spend Cap on an Existing AWS Account: Budget Actions, Service Control Policies and Quotas
Spend limits don't cover existing AWS accounts yet. You can build most of the same protection today: budget actions that apply a deny policy or stop instances at a threshold, service control policies that keep accounts away from the most expensive services, lower quotas, and anomaly alerts. The setup, in order, and the gaps it leaves.
Read
AWS Spend Limits: How the Hard Monthly Cap Works, What Pauses, and Who Can Use It
AWS now has a hard spending cap. A project in the new AWS experience pauses when it reaches its monthly limit instead of billing past it: every resource stops, S3 included, and data is kept for 90 days. It covers all of the project's charges, egress too, but only for projects created through the new signup experience. Not existing accounts, and not Organizations, yet.
Read
As of November 9, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.