It's never too late. 21 years after being reported, Firefox finally has native macOS context menus in the nightly version. https://bugzilla.mozilla.org/show_bug.cgi?id=34572
Ah, maybe in 10 years they'll use the native file pickers.
AWS bill capping feature request thread still unanswered after 10 years
61–70 of 170 posts
Re: AWS bill capping feature request thread still unanswered after 10 years
#62You really need to implement limits service-by-service, and with as many services as AWS has, it would make sense if some of them hadn't implemented limits yet. Think about the details... if you are paying something for both storage and bandwidth, and get a sudden surge of bandwidth, do you really want items in storage to be deleted? You basically never want storage to be automatically deleted even if your program su…
I don't think you ever want storage to be deleted as part of an automatic bill cap system. Just refuse access, or allow reads but not writes until the customer reviews it. There's even an HTTP code for it: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402 (non standard, but I know for a fact it's used by Azure).
Actually deleting things should be done after a period of time specified in writing in the contract with the customer, and I'd hope you'd try to contact them first.
But I think an automatic bill cap absolutely makes sense for storage, and I can't really see any reasons it couldn't work.
Re: AWS bill capping feature request thread still unanswered after 10 years
#63You really need to implement limits service-by-service, and with as many services as AWS has, it would make sense if some of them hadn't implemented limits yet. Think about the details... if you are paying something for both storage and bandwidth, and get a sudden surge of bandwidth, do you really want items in storage to be deleted? You basically never want storage to be automatically deleted even if your program su…
Exactly. I have heard stories of bill capping that ended up with infra and data being deleted, so I can really see why they wouldn't implement it. What they could do however would be to allow usage limit based on IAM policies for example (Deny s3:Getobject Condition: monthly bandwidth >= x)
Re: AWS bill capping feature request thread still unanswered after 10 years
#64It hasn't been implemented because it is nonsensical. So you hit your limit. Is all your storage deleted? You can't receive an alert because that costs something (even if it's a fraction of a cent) to send. Are your domains forfeit? Audit logs destroyed? There's no reasonable way to implement this. Billing alerts are the best you can do on this problem and I think it would be a good faith move for AWS to enable some…
What the hell good is a budget alert when you’ve launched 2000 high memory instances because your programmer screwed up?
Because those alerts are hookable and could shut down the instance.
Re: AWS bill capping feature request thread still unanswered after 10 years
#65You really need to implement limits service-by-service, and with as many services as AWS has, it would make sense if some of them hadn't implemented limits yet. Think about the details... if you are paying something for both storage and bandwidth, and get a sudden surge of bandwidth, do you really want items in storage to be deleted? You basically never want storage to be automatically deleted even if your program su…
I don't think you ever want storage to be deleted as part of an automatic bill cap system. Just refuse access, or allow reads but not writes until the customer reviews it. There's even an HTTP code for it: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402 (non standard, but I know for a fact it's used by Azure). Actually deleting things should be done after a period of time specified in writing in the cont…
[deleted]
Re: AWS bill capping feature request thread still unanswered after 10 years
#66My understanding is that this is a difficult problem to solve "perfectly" due to lag between incurring a cost and recording the cost. I believe GCP currently has the best feature for this. You can set both billing alerts as well as caps. However, I also believe that it can take up to 24 hours between incurring a cost and it showing up on your billing report. So even on GCP (which is the most forward-thinking cloud se…
GCP doesn't support a cap, only alerts. You can use those alerts to implement your own cap mechanism, same as how it works on AWS except AWS billing is only on a one hour delay I believe so I'd say AWS wins here.
App Engine used to support caps. They're no longer supported, because for every customer pleasantly surprised, there were five customers incandescent with rage that their service had gone down at the worst possible moment due to a spike in actual demand.
Re: AWS bill capping feature request thread still unanswered after 10 years
#67My understanding is that this is a difficult problem to solve "perfectly" due to lag between incurring a cost and recording the cost. I believe GCP currently has the best feature for this. You can set both billing alerts as well as caps. However, I also believe that it can take up to 24 hours between incurring a cost and it showing up on your billing report. So even on GCP (which is the most forward-thinking cloud se…
Just offer to switch existing usage to flat rate services instead of consumption based services. This isn’t rocket science. We know how to control costs.
Cloud vendors obviously don’t want this.
Re: AWS bill capping feature request thread still unanswered after 10 years
#68As a junior developer I'm always afraid using any AWS service to make a mistake that cost me a lot of money. I'm not talking about millions, simply 2k would be really bad for me.
Re: AWS bill capping feature request thread still unanswered after 10 years
#69It's never too late. 21 years after being reported, Firefox finally has native macOS context menus in the nightly version. https://bugzilla.mozilla.org/show_bug.cgi?id=34572
I've been using Firefox for a long time (first in its "Camino" guise), but I've never noticed.
Re: AWS bill capping feature request thread still unanswered after 10 years
#70I'm told some really fancy restaurants would not show the prices on the rational that "if you need to know the price, then it's too expensive for you"
Well, I think the same point can be made here: if you need a price cap, then AWS is too expensive for you ;)