[heipei]

At the very least allow users to roughly define what happens when the threshold is reached: S3 will still store data but maybe not serve anything, Lambdas will still be defined but not run, EC2 instances will keep running, etc. It's not supposed to be a hard cap as in "don't spend a penny more than my $5" but more as in "do everything possible and reasonable so the customer doesn't wake up to a sudden $20k overnight AWS bill".

[sathyabhat]

This sort of possible

> AWS Budgets now allows you to configure actions — responses to cost and usage in your account or set of accounts— that will be applied automatically or via a workflow approval process once a budget target has been exceeded. There are three action types: Identity and Access Management (IAM) policies, Service Control policies (SCPs), or target running instances (EC2 or RDS). Actions can be configured for actual (after they’ve occurred) or for forecasted (before they occur) budgeted amounts.

https://aws.amazon.com/blogs/aws-cost-management/get-started...

[andrewguenther]

You can do this by monitoring billing alerts and automatically shutting down non-critical infrastructure you have. "Do everything possible" is up to a customer to define because it depends on their infrastructure, AWS cannot define this in a way that would make anyone happy.