3 ms·

>I would rather my whole system shut down and be unusable while I investigate vs. auto-scale and charge me a bill I can't cover. Sure, but most large companies

>I would rather my whole system shut down and be unusable while I investigate vs. auto-scale and charge me a bill I can't cover. Sure, but most large companies (the kind which AWS gets a lot more revenue from and cares about a lot more) want the exact opposite. Most large companies have the extra cash to spend in the case that a runwaway auto-scale was in error, but on the other hand, completely shutting down operations whenever a traffic spike happens could resort in millions of lost revenue. >However, searching around it seems like I can only get alerts when a $$$ threshold is passed, but AWS won't take any action to stop computing or anything. Please prove me wrong. The general advice is to use the various kinds of usage alerts (billing alerts, forecasts, etc) to trigger Lambda functions that shut down your instances as you desire. It takes a little configuration on your part, but again, AWS intentionally errs on the side of not automatically turning off your instances unless you specifically tell it to.

ISL 7y ago
If the customer dies, the lifetime value of the customer is almost-certainly lower. Great companies find ways to help their customers thrive.
- perl4ever 7y ago
  I don't know what Amazon actually does, but what I think of as normal is the customer calls the help desk and they reverse the charge. This seems simpler than worrying about how to code algorithms that will deal with all possibilities. People make mistakes with transferring money in the millions of dollars all the time, and it's not uncommon for people to be just like "oops, back that out". It's obviously going to be in the news when that doesn't happen though.
gray_-_wolf 7y ago
> Sure, but most large companies (the kind which AWS gets a lot more revenue from and cares about a lot more) want the exact opposite. It does not have to be all or nothing. You could for example setup separate account per department and/or purpose and impose hard cap on spending for experimentation, but not on production.

ISL 7y ago

If the customer dies, the lifetime value of the customer is almost-certainly lower. Great companies find ways to help their customers thrive.

perl4ever 7y ago
I don't know what Amazon actually does, but what I think of as normal is the customer calls the help desk and they reverse the charge. This seems simpler than worrying about how to code algorithms that will deal with all possibilities. People make mistakes with transferring money in the millions of dollars all the time, and it's not uncommon for people to be just like "oops, back that out". It's obviously going to be in the news when that doesn't happen though.

gray_-_wolf 7y ago

> Sure, but most large companies (the kind which AWS gets a lot more revenue from and cares about a lot more) want the exact opposite. It does not have to be all or nothing. You could for example setup separate account per department and/or purpose and impose hard cap on spending for experimentation, but not on production.