Earlier quoted context omitted.
Well luckily it's very obvious when I still have a car in my driveway. It's not obvious that a script got caught in a loop and decided to write up a $5000 bill overnight.
The previous post didn't say a script got caught in a loop overnight, it was that the engineer didn't understand the difference between stopped and terminated. Even so, I don't think it is AWS's fault that buggy code was left to run unattended overnight in the example you give.
It is absolutely 100% Amazon's decision to give you little to no tooling to prevent this in many scenarios other than going to their billing department and beg for a correction.
I do not use any service that can proceed to bankrupt me for personal use for what could be considered a normal use case. At work I'd pass the issue off to my manager who'd pass it off to a rep and deal with it that way, but there is no way I want to take that responsibility on myself to correct.