A recent AWS billing error raised a question for me. Alerts can warn people about unexpected costs, but they don't necessarily stop them. Should customers be able to choose a spending limit that automatically stops services, and what would be the downsides?
Should AWS offer an optional hard cap on cloud spending?
Answers
I'd want that option for a small personal account. An alert in the middle of the night isn't much of a backstop if usage keeps accumulating while nobody is there to respond. Let customers choose a threshold and accept that their services might stop.
Reply to this answer
The tricky part is what happens when the billing data itself is wrong. If a bad number triggers an automatic shutdown, a billing glitch could turn into an outage. A cap would need careful safeguards against that, plus a clear way to restore service.
There is also a difference between a spending backstop and a guaranteed maximum invoice. Any proposal should spell out what happens if usage is reported after the threshold has already been crossed.
Reply to this answer
Before treating the recent numbers as actual losses, check whether they were estimates, invoices, or charges. People disagreed about the nature of the error, so an alarming displayed amount alone doesn't establish that money was taken.
That doesn't make the broader concern go away. Unexpected usage and compromised accounts are separate reasons someone might want stronger cost controls.
Reply to this answer
Consumer protection rules are worth discussing, especially for people learning on small budgets. A useful request to officials would distinguish billing errors from genuine runaway usage and ask for an opt-in backstop, rather than assuming one shutdown policy fits every customer.
Reply to this answer
Add your answer
Answers are reviewed before publication.
p502+windlass_8:
Optional is the key word. A shutdown could be much more costly than the extra spend for an account running something critical.