Hacker News Reader

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.

View on HN

It 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.

AWS Lambda has had this knob for quite a few years, it’s called “provisioned capacity”, and it defines an upper bound to function concurrency.

While helpful, this is not the same. E.g. a global kill switch could be harder to overlook and easier to manage.

You 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.

This is a highly welcomed feature however, I don’t think AWS has it.

> 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.

Reply on news.ycombinator.com