Thread

1. joshdavham · 1791078994 · focus · HN ↗

   It’s incredible that in 2026, AWS and GCP are only just now introducing this. It’s possibly one of the most obviously needed features for a cloud provider.

   Also, does anyone know why it’s taken this long? I suspect it’s a technical reason. While one could be cynical, I doubt it’s an intentional business/product decision. Hard spending caps are both excellent product differentiators and could possibly save these providers money as they don’t have to forgive their users when they accidentally over-use a service.

   1. bpodgursky · 1791082101 · focus · HN ↗

      How do you hard-cap S3 and other persistent data storage?

      "Sorry, you had a hard cap on AWS spend so we deleted all your S3 data on August 27th". Yeah not going to fly.

      1. 3eb7988a1663 · 1791083951 · focus · HN ↗

         There is a huge difference between "stop accruing new spend" and "nuke everything".

         The horror stories I have seen are of the type: some big artifact was getting pulled in a loop, causing TBs of network traffic or access keys were leaked and malware spun up 1000 xxxlarge instances.

         The ability to stop the bleeding is the bare minimum people want. Not, "Well, you made a boo-boo so now you lost everything."

Unofficial Hacker News client; not affiliated with Y Combinator.