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.
For twenty years the answer to "can I cap my AWS bill?" was no: budgets alert, and you act. Spend limits change that for one part of AWS. You set a monthly limit on a project, and when the project's charges reach it, AWS pauses the project rather than charging more. The team that built it answered questions in a public AMA in November 2026, and their answers settle most of what people want to know.
All of the project's pre-tax charges: compute, S3 and database storage, and outbound data transfer. Runaway egress, the cost people fear most, counts like anything else.
From the AWS spend limits team's answers in their r/aws AMA, November 2026. The team compared a paused project to a closed AWS account.
Two optional controls try to keep a project away from its limit, acting days early and more gently than the pause:
From the AWS spend limits team's answers in their r/aws AMA, November 2026.
Projects created through the new AWS signup experience.
Not existing AWS accounts. The team said this is on the roadmap.
Not across accounts in an organization. The team said they are looking at it for organizations.
Not per resource: you can't yet say "keep production running, stop the rest". The team took it as feedback.
How quickly the pause follows the limit. AWS billing data has always lagged usage by hours, so spend in that window may still land.
Whether someone with access to a compromised account could raise or remove the limit, which decides how much it protects against a hijacked account.
Whether the feature has its own price.
Spend limits don't cover existing accounts yet. We'll set up the closest equivalent with Budgets actions and guardrails. 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
AWS Spend Limits vs Budgets, Budget Actions and Cost Anomaly Detection: Which Stops a Runaway Bill
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.
Read
AWS Spend Limits: The Limitations, and What to Do About Each
Spend limits only work on projects created through the new AWS signup experience, can't cover an existing account or an organization, can't spare production while stopping the rest, and pause everything at once. Each limitation, what it means in practice, and the workaround until AWS extends the feature.
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.