4 ms·
A kill switch seems a practical and trivial solution. E.g. something toggled when a monthly bill exceeds a configurable amount. I’m guessing many hobby users w
by merelysounds 3y ago
A kill switch seems a practical and trivial solution. E.g. something toggled when a monthly bill exceeds a configurable amount.
I’m guessing many hobby users would set that to $100, end of story.
I don’t understand why it’s so unpopular to offer that. I’d imagine the providers would benefit too in the long run.
- andrasbacsai 3y agoIt would be practical for the user, but not for the company. Why does this not exist after years (more than a decade since EC2) of cloud computing? Because it is not good for the VC investors.
- catlifeonmars 3y agoAWS Lambda has had this knob for quite a few years, it’s called “provisioned capacity”, and it defines an upper bound to function concurrency.
- merelysounds 3y agoWhile helpful, this is not the same. E.g. a global kill switch could be harder to overlook and easier to manage.
- webprofusion 3y agoYou can set a hard budget on most cloud providers, including Azure etc. I actually did this thinking I was just setting a budget alert and that was a new and interesting way to interrupt production.
- merelysounds 3y ago> You can set a hard budget on most cloud providers Note that the submission references serverless providers, specifically netlify and vercel. I don’t think these support an easy to configure kill switch - in any case it wasn’t easy to configure in the scenarios listed on the page.
- kikimora 3y agoThis is a highly welcomed feature however, I don’t think AWS has it.