They could have given us a choice though. Sign in blood that you want to be shut off in case of over spend.

You could set a cloudwatch cost alert that scuttles your IAM and effectively pulls the plug on your stack. Or something like that.

▲

moduspol 3 hours ago | parent | prev [-]

As long as "shut off" potentially includes irrecoverable data loss, I guess, as it otherwise couldn't conclusively work. Along with a bunch of warnings to prevent someone accidentally (or maliciously) enabling it on an important account.

Still sounds kind of ugly.

	▲	DenisM 2 hours ago \| parent [-]
		Malicious or erroneous actor can also drop your s3 buckets. Account change has stricter permissions. The key problem is that data loss is really bad pr which cannot be reversed. Overcharge can be reversed. In a twisted way it might even strengthen the public image, I have seen that happen elsewhere.