Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS bill capping feature request thread still unanswered after 10 years

forums.aws.amazon.com

Post reply on HN
Print view View original

51–60 of 170 posts

Re: AWS bill capping feature request thread still unanswered after 10 years

#51

Post by philliphaydon »

capableweb wrote: post #42
lacker wrote: post #19

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

> You basically never want storage to be automatically deleted even if your program suddenly uses a surprising amount In most use cases you're right. But never? Not true, not all storage is used the same way. And the thing is, why should Amazon decide which use case is valid or not? I might care more about being able to afford the service than to keep the data around, depending on what kind of service I offer my user…

There are rules in S3 to move files or delete them after a period of time.

Re: AWS bill capping feature request thread still unanswered after 10 years

#52

Post by Agingcoder »

andrewguenther wrote: post #15
runnerup wrote: post #11

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

We talked about caps with the Google reps at my day job.

The short answer was 'we can, but don't want to' (note : this may be completely unrelated to what Google thinks internally, and is just what the fairly high up the food chain rep told us)

Re: AWS bill capping feature request thread still unanswered after 10 years

#53

Post by Hermel »

andrewguenther wrote: post #13

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

That still does not explain why they refuse to answer the question.

Re: AWS bill capping feature request thread still unanswered after 10 years

#55

Post by johnwheeler »

andrewguenther wrote: post #13

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

Re: AWS bill capping feature request thread still unanswered after 10 years

#56

Post by Havoc »

andrewguenther wrote: post #13

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

>Everyone's conflicting ideas

There is no reason why an absolute "don't ruin me financially" button can't be implemented in addition to everything you mention.

>There's no reasonable way to implement this.

Azure VS enterprise credits work this way. 150 hard cap with no credit card on the individual account.

Re: AWS bill capping feature request thread still unanswered after 10 years

#58

Post by anigbrowl »

andrewguenther wrote: post #13

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

This sort of dismissive attitude coupled with a circular justification is the epitome of user hostility, and an unattractive norm in the tech community.

Re: AWS bill capping feature request thread still unanswered after 10 years

#59

Post by detaro »

andrewguenther wrote: post #23
neolog wrote: post #17

Earlier quoted context omitted.

Having to make some design decisions doesn't mean it's impossible to design.

Budget alerts were the design decision made. You can set up your own infra to listen to budget alerts and cap your own costs. This is a feature that only makes sense to put in the customer's control because a general solution would work for no one. It's a great solution to the problem imo.

Isn't the AWS Budget stuff recalculated only every few hours, or do the alerts somehow get quicker updates?
Post reply on HN