Earlier quoted context omitted.
It seems like a hard technical problem to shut down gracefully. But it's an easy product problem. Just suspend the account. AWS must do this already for some cases. No one running a real business on AWS wants a hard ceiling instead of billing alerts and service by service throttling. Which Amazon has. So, this is just the nuclear option for people's pet projects. It's not a bad thing to have but I wouldn't expect it…
> No one running a real business on AWS wants a hard ceiling instead of billing alerts and service by service throttling. Which Amazon has. I know startups that I could bankrupt with a few lines of code and a ~$60 server somewhere long before they'd be able to react to a billing alert if it wasn't for AWS being reasonably good about forgiving unexpected costs. I'm not so sure no one running a "real business" would li…
If you can't afford downtime you probably can afford to wait for the alert and choose your own mitigation strategy. A system that can't tolerate downtime probably has an on-call rotation and these triggers ought to be reasonably fast.
If you can't react or can't afford to react, you probably can afford some downtime / data loss.
So the system doesn't need to have granular user defined controls. Just two modes. That was my point.
I think I triggered people with the phrase "real business" and I apologize for that.