Hacker News new | ask | show | jobs
by catlifeonmars 220 days ago
I agree the best effort approach seems sane. Storage cost is typically dwarfed by compute and network I/O anyway. Overall AWS has very few guardrails and it would be useful to ask the user if they want to opt in to guardrails when they open an account. I’m thinking there are a handful of use cases that would have different defaults:

- student, learning how to use AWS: set a maximum spend limit and hard cutoff

- small business, running a website: ddos protection and compute limits, pause compute and alert user if spend goes over, giving them the option to raise the limit and/or resume

Etc etc