3 ms·
It might be really hard to add in retroactively. Otherwise there’s no excuse, it’s such an annoying vulnerability for a customer, even if you can email support
by thundergolfer 4y ago
It might be really hard to add in retroactively. Otherwise there’s no excuse, it’s such an annoying vulnerability for a customer, even if you can email support and get a refund. Where I work, modal.com, we have enforced budget limits for accounts.
- brundolf 4y ago> It might be really hard to add in retroactively I don't see how? if (cap != null && service.currentBill > cap) { service.deactivate() }
- lozenge 4y agoSo do you want all your S3 buckets deleted when you reach the cap? How about that pet EC2 with ephemeral storage?
- brundolf 4y agoSure, it gets more complicated with storage. But I think we're mostly talking about stateless services here And for storage or storage-having services you could easily have a "shut it down but preserve the data for a comparatively-small recurring fixed storage charge"