Counter argument, this is the sort of thing that, especially for a smaller business or individual, can be the difference between a bad night and bankruptcy.

Sure it sucks that critical services blinked out at 2am. But what sucks even more is finding out the image on my ASG had a vulnerability that allowed someone to install a bunch of bitcoin miners which kept me fully scaled from midnight to 2am.

Or more likely, that a mistake in terraform 1000xed my spending.

Most people have predictable spending and could easily say "don't spend more than 10x what I normally spend". Or 1.5x, or 2x, 3x, etc. All depending on how they want to balance a runaway cloud expense.

▲

twoodfin 6 hours ago | parent [-]

For a large enterprise spending millions on AWS, 1.5X is already a budgetary disaster. Unfortunately, shutting off critical IT infra because it hit 1.4X spend this month is a business disaster.

There’s no magic wand that produces good outcomes when planning or execution goes awry at scale.

	▲	cogman10 5 hours ago \| parent [-]
		> especially for a smaller business or individual, can be the difference between a bad night and bankruptcy. Just because this isn't a good solution for everyone, doesn't mean it's not a good solution for a large number of people and businesses. A lot of businesses can tolerate outages. In fact, even very big businesses come out mostly unscathed when they have multi-hour outages. (how many is it for github this year?) An outage causes a reputational black eye. It does not necessarily translate to lost income.