Re:Mistakes I've Made in AWS
by alexeldeib on Saturday September 11, 2021 @12:50PM
(#28493465)
https://docs.microsoft.com/en-us/azure/cost-management-billi...
e.g. "virtual machines are stopped and de-allocated. The data in your storage accounts are available as read-only."
Most control plane operations will also be blocked. It gets complicated with more complex resource types, but it gets the job done anyway.
Note that this functionality is sort of required to support pre-paid plans without allowing them to exceed specific limits, which do exist on Azure. So there's a business dependency on this functionality today, it's not a hypothetical.
Re:Mistakes I've Made in AWS
by yjftsjthsd-h on Saturday September 11, 2021 @07:50PM
(#28497219)
Give me a page in billing listing everything that can use money, let me enable/disable them manually (this is mostly to allow restricted dev accounts) and select which, if any, should be allowed over the bill total I set. Opt-in, but yes, do let me kill every EC2 instance if I choose.
Since I enjoy tilting at windmills--how do you propose this works? Like, in detail.
Because every time I try and drill into details of this with someone, it winds up what they really want is "pay what you want" cloud services.
AWS is much, much more than just a place to run a virtual server and many resources accrue on-going costs with no way to "turn them off". When you hit your hard circuit breaker, do they delete all your EBS volumes and data in S3? Your private SSL root? Your user directory? Encryption keys? DNS zones?
The number of people that would want all of that removed when they hit their $X/mo limit is likely minuscule in comparison to the number of people that would turn this on not understanding what it really meant and then publishing angry blog posts about how Amazon killed their startup right when they got popular and traffic spiked.