Does AWS have a spending limit?
7 mins read
Does AWS have a spending limit?
Quick answer: Yes, since September 2026, with catches. AWS Spend Limits let you set a monthly ceiling per project. Reach it and AWS pauses the project. They only exist in the new AWS Settings experience, which new accounts get first, and the minimum sits above your normal spend. Older accounts still have budget actions, which stop only what you name, hours late.
For years the answer was a flat no. Now it is a yes with footnotes. Here is what changed, what it covers, and what it does not.
What are AWS Spend Limits?
A number you set per project. The most you will pay that month, before tax and credits. If the project's usage reaches it, AWS pauses the project and stops its resources. Your data stays. You raise the limit to turn it back on.
AWS calls it a type of AWS Budgets, and that is the right way to think about it. It is a budget that acts on its own, with the whole project as the blast radius.
It arrived on 16 September 2026 as part of the new AWS Settings, the redesigned console for new accounts. AWS is releasing it "to a limited number of customers", so you may not see it yet. You need a Paid Plan. You can set limits on up to 10 projects.
AWS's own words on who it is for: "designed for experimentation, learning, and sandbox workloads". Production is allowed "when it is acceptable to have a brief pause of your resources".
What happens before you hit the limit?
You get warnings at 50%, 75% and 90% of the limit, and when AWS forecasts you will reach it within 10 days.
Then there are three optional controls that act earlier, in this order:
About 7 days before you would reach the limit, new resources stop launching. AWS applies a service control policy. What runs keeps running, but autoscaling cannot add instances.
About 5 days before, idle resources are paused. EC2 instances under 5% CPU for two weeks, RDS databases with no connections, SageMaker endpoints with no calls.
About 4 days before, your biggest cost drivers are paused. EC2, RDS, Lambda, Bedrock and SageMaker. AWS says this one "can be a disruptive experience". It is also the one that stops a runaway Lambda.
Each is opt-in. Turn on all three and the limit becomes a slope rather than a cliff.
What are the catches?
Three.
It is for new accounts. Spend Limits live in the new AWS Settings. If you opened your account before the rollout, you do not have them, and AWS has not said when you will. Most teams reading this are on the old console.
The floor is above your normal spend. The minimum limit is the greater of $20 or "a conservative estimate of your likely spend", based on this month, last month and what you have running. That is deliberate: AWS does not want normal usage to hit the limit. It also means the limit protects you from a disaster, not from a bad week. A 40% jump can sit under it for days.
Reaching it stops everything. The project pauses. All of it. For a sandbox that is the point. For a service with users it is an outage you chose in advance. And if you leave a paused project alone for 90 days, AWS deletes its data.
What can older accounts do instead?
Budget actions. You set a budget in AWS Budgets and attach an action to a threshold. At 90% of forecast, say. It can apply a deny IAM policy, apply a service control policy, or stop EC2 and RDS instances you list by name. The first two budgets with actions cost nothing. After that, $0.10 a day each.
The catch is speed. AWS updates budget data up to three times a day, 8 to 12 hours apart. One team watched a stolen key spend about $62,000 in under 24 hours. That is roughly $2,600 an hour. Twelve hours between budget checks is $31,200 before the action has a chance to run.
And it stops only what you named. Lambda, S3, data transfer, NAT gateways and model calls keep going. A new admin user the attacker created is not on your deny list. How a leaked key plays out.
The free plan. Accounts opened since July 2025 can pick it. It never charges. It ends after six months or when credits run out, and then the account closes. A real cap, and also the end of the account. Fine for learning. Not for anything with users.
Is a cap the same as an alert?
No. They do different jobs, and you want both.
A cap is a sprinkler. It goes off when the room is already on fire, and it soaks everything. A good cap is set high enough that it almost never fires.
An alert is a smoke detector. It goes off at the first change, names the room, and leaves the decision to you. The cheap way out of a bad bill is to notice it in the first hour, not to pull the plug on day four.
Spend Limits make the sprinkler real for new accounts. Nobody has made the smoke detector built in.
How does watchmy.cloud help here?
We do not stop anything. We tell you, fast, so a person decides.
Connect AWS. Read-only billing access. No keys. No access to what you run. One CloudFormation template, about two minutes.
Send it where work happens. Slack for fast triage. Jira for follow-up. SMS for the 3 AM one.
Stop worrying about it. We watch AWS spend for you, so you don't have to keep checking it.
We check your spend every hour. An hour that costs three times what that hour normally costs fires an alert. So does a day 30% over your 7-day average. The alert names the account, the dollars over, and the services behind it. A flat $49 a month, on any account, old or new. Here is how it works, and how we differ from AWS Budgets. We are a small team, and this is all we do.
FAQ
Does AWS have a hard spending limit?
Yes, since September 2026. AWS Spend Limits set a monthly ceiling per project and pause the project when usage reaches it. They are available only in the new AWS Settings experience, which is rolling out to a limited number of customers, mostly new accounts, on a Paid Plan.
Can I set a spend limit on an existing AWS account?
Not today, unless your account has the new AWS Settings experience. AWS has not published a date for older accounts. Older accounts can use budget actions, which apply a deny policy or stop named EC2 and RDS instances at a threshold.
What is the minimum AWS spend limit?
The greater of $20 or a conservative estimate of your likely monthly spend, based on this month, last month and what you have running. AWS sets the floor there so normal usage does not trip the limit.
What happens when an AWS spend limit is reached?
AWS pauses the project and stops all its resources. Data is kept. You raise the limit in AWS Settings to reactivate, and some resources need a manual restart. If you take no action for 90 days, AWS deletes the project's data.
Do AWS Spend Limits stop a leaked key?
Eventually. With the early controls on, new resources stop about 7 days before the limit and top cost drivers pause about 4 days before. The limit itself is set above your normal spend, so a key that spends thousands an hour can run for a while before the project pauses.
Do I still need alerts if I have a spend limit?
Yes. A spend limit fires near a ceiling set above your normal spend. An hourly alert tells you the moment spend changes, with the service behind it, while the bill is still small. Most teams want the alert first and the cap as the backstop.
See it before you connect anything: live demo, no sign-up.
OLDER / NEWER
Older post
Newer post
