Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> AWS should have a cost cap. Set a max spend value and shut down all servers if you spent it.

That might make sense for some particular services (e.g., capping the cost on active EC2 instances) but lots of AWS costs of data storage costs, and you probably don't want all your data deleted because you ran too many EC2 instances and hit your budget cap.

Where exactly you are willing to shut off to avoid excess spend and what you don't want to sacrifice automatically varies from customer to customer, so there's no good one-size-fits-all automated solution.



I think if resources had an option of "At cap: Do nothing, Shut down, shutdown and erase data" that would cover most of the use cases.


Keeping the data for a week but completely inaccessible would not be a huge cost for AWS yet a big relief for startups.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: