[raverbashing]

> AWS has to think of everyone.

Sure. That's why you make it optional. And configurable in a way

But at a very basic idea, blocking new services from being started and throttling of existing ones would go a long way in helping. A very long way.

[andrewguenther]

You can implement this on top of budget actions today: https://aws.amazon.com/blogs/aws-cost-management/get-started...

[jiggawatts]

I have small and medium scale customers that have hundreds of distinct service types in Azure or AWS. Sometimes both. Several have had spending blowouts where a hard limit would have helped.

None have the engineering capacity to figure out how to cap the spending on each one of the individual services, each with their unique and special API.

You're arguing that Amazon can't afford the difficult engineering of spending caps, but the very customers that need spending caps because their budgets are so constrained are so well moneyed that they should all individually be able to invent a solution, engineer it, and manage it?