AWS is finally putting a brake on its biggest problem. After years of hearing stories about people whose projects went wild and racked up five-figure bills overnight, Amazon has launched a feature that pauses a project when it hits a spending limit. The company announced it on 16th September, and the move arrives at a moment when the author argues the feature is needed more than ever.
The feature is called spending limits. When you set one, a project pauses when its usage reaches the cap. It is a simple switch, but it changes the economics of building on AWS entirely. The company’s announcement page explains that users can set a monthly spend limit “based on your usage patterns,” and that if a project’s usage reaches that limit, “your project is paused for that month.”
Why Hard Caps Matter
The author of the post argues that soft caps — the kind that send an email warning but let spending keep going — are useless. They protect nobody. Instead, he wants hard budget caps to be the default, with a clear opt-in for anyone who wants to live dangerously.
“After $X/month, cut this thing off and return errors.”
That is the feature he wants to see everywhere. He calls it a product feature the world will need a lot more of over the coming months and years.
The Problem AWS Created
The author has heard plenty of stories from people who refuse to use AWS for personal projects because of justified fear that a runaway service might bankrupt them. He has also heard stories from people who did not anticipate this and ended up seriously burned.
Midnight emails warning about a budget limit are common. By the time the email arrives, the damage is done. Several hundred dollars, several thousand dollars, several ten-thousand-dollar bills are waiting for you in the morning.
What Google Got Right First
Google Cloud launched a similar feature in July, called Spend Caps. It lets you “set a monthly financial cap on specific services within a project.” The feature is available now, and it works in much the same way as AWS’s spending limits.
The comparison is telling. Both companies are moving in the same direction, but Google got there first. The announcement page warns that “We’re currently releasing our new experience to a limited number of customers.”
That limitation matters for anyone who wants to use the feature today.
The Case for Default Hard Caps
The author’s central argument is that hard budget caps need to be the default. If someone wants to live dangerously, they should be able to do that, but it needs to be on an opt-in basis. He suggests a clear, prominent checkbox:
“Remove the budget cap. My application will not be shut down if I exceed the configured budget limit, and I will be responsible for subsequent charges.”
That checkbox is a simple design decision, but it changes the relationship between a user and a cloud provider. With a hard cap, the service stops. With no cap, the service keeps running and the bill keeps growing.
The author makes the case bluntly: most businesses and individuals would prefer errors to a surprise $10,000+ bill. That is the trade-off at the heart of the feature. You can have a service that fails gracefully when it hits a limit, or you can have a service that keeps working until it bankrupts you.
Who Is Behind the Post
The post does not name its author, but it reads as a personal account from someone who has spent significant time building on AWS and watching others suffer from it. The stories he tells are not abstract statistics. They are real experiences, and they carry weight because they are specific.
He describes people who refuse to use AWS for personal projects out of justified fear. He describes people who were burned. Those stories are the foundation of his argument.
The post also references recent articles on OpenAI DevDay 2026 and 2026 in LLMs, which suggests the author follows the AI industry closely. The timing of the post — published on 3rd October 2026 — puts it after both of those events.
What Comes Next
AWS’s spending limits are a step in the right direction, but they are not the end of the road. The feature is rolling out to a limited number of customers, and it is not yet available to everyone.
The author’s broader vision includes several elements:
- Agents — coding agents wrapped in a less threatening UI — to help with this
- Agents biasing towards recommending providers with hard budget caps
- Agents warning new and inexperienced builders against deploying applications using uncapped services that might get them into trouble
That vision is a ways off. But the fact that AWS has moved is significant.
The Verdict on AWS’s Move
The move is welcome, but it is not complete. The feature is rolling out to a limited number of customers, and it is not yet available to everyone.
The author’s argument holds up. Hard budget caps should be the default, with an opt-in for anyone who wants to take the risk. The fact that AWS is doing this at all is evidence that the problem is real.
The post closes with hope that the feature hits general availability for existing accounts soon. That is the right wish to have. Until then, the lesson is simple: check the box carefully, and know what you are getting into.
The author’s final wish is that the feature becomes widespread. He sees it as a trend, and he wants to accelerate it. His post is a call to action.
The post’s argument is simple, but it is powerful. The problem is real, and the solution is obvious. AWS has taken the first step. The rest of the industry should follow.
Source material: “We're going to need default hard budget caps on pretty much everything,” simonwillison.net.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.