I'm in agreement with the cloud providers over those of you wanting a hard shutdown.
Businesses, the entities that are paying the most money to AWS, will NOT want a hard shutdown. When you generate revenue off of your SaaS service maybe you'll understand.
No, I won't be pushing my TAM to enable a forced shutdown due to budget metrics.
Not to mention, how does AWS decide what to shutdown and what to delete? It's not like it's only running resources that cost money, what about all my data that's stored???
> Businesses, the entities that are paying the most money to AWS, will NOT want a hard shutdown.
I don't think anyone is arguing that any account MUST take advantage of hard shutdowns. Only that it should be an option for those who truly do want it.
> How does AWS decide what to shutdown and what to delete?
That's a much more interesting question. It tends to be services, rather than storage, that are the root cause of these outlandishly large surprise bills. But if, by chance, it's S3 that's running up the bill, what would a hard shutdown mean? Which data does Amazon delete first to get the account down to its hard limit?
Businesses, the entities that are paying the most money to AWS, will NOT want a hard shutdown. When you generate revenue off of your SaaS service maybe you'll understand.
No, I won't be pushing my TAM to enable a forced shutdown due to budget metrics.
Not to mention, how does AWS decide what to shutdown and what to delete? It's not like it's only running resources that cost money, what about all my data that's stored???