Live data from Hacker News

AWS bill capping feature request thread still unanswered after 10 years

forums.aws.amazon.com

71–80 of 170 posts

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

#72

Earlier quoted context omitted.

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.

Ho do you know?

I can easily believe it, and I can easily believe that AWS employees have heard such stories, but I'd love to have it be more than an anecdote.

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

#73
This is one of the reasons I really like Vultr. They have a simple interface and their pricing has always been solid for me. I don't ever go to sleep worried I'm going to wake up with a $10k bill.

At one of the companies years ago a developer accidentally leaked an API credential on GitHub and the company woke up with a $30k bill.

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

#74
post #70

I'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 ;)

I use a few free APIs with usage limits. Maybe I pay 10 cents a year. I’m always afraid to one time open an invoice to find out it’s way more than that for whatever reason.

The problem is that AWS markets itself as “pay what you use” and generally that’s extremely little for me, but if I screw up with Glacier I suppose I could get a $100 bill because I restored some backups the wrong way.

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

#75

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…

> There's no reasonable way to implement this.

Oh, really? Azure wants to have a word with you ... Yes, currently they don't enable this for subscriptions with commitment plans or with pay-as-you-go pricing, but it is not because it is not possible or feasible, as you argue - the technical infrastructure in the form of spending limits, spending budgets and quotas is there [1-3] and is available for select plans [4].

[1] https://docs.microsoft.com/en-us/azure/cost-management-billi...

[2] https://docs.microsoft.com/en-us/partner-center/set-an-azure...

[3] https://docs.microsoft.com/en-us/azure/azure-resource-manage...

[4] https://azure.microsoft.com/en-us/support/legal/offer-detail...

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

#76

Earlier quoted context omitted.

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

And perhaps most useful rule is to move them to cheaper tiers of storage. For example, Glacier Deep Archive is super cheap for storage since it's $0.99 per terabyte-month.

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

#77

Yes this would be a super useful feature especially for dormant accounts. One of my old aws account was recently hacked and racked up bills in thousands of dollars. The AWS support was super nice and took care of it for me but it gave me some sleepless nights until it was resolved. If this was a feature I would have most definitely capped my account at 1k (my max bill being $50). They can always send alerts to increa…

They could easily factor natural growth and ping you when it feels like bills are getting too close to the cap. Even “bursts” could be allowed x% above the cap if you get an email within an hour.

The lack of caps is just laziness or a dark pattern by Amazon. There’s no excuse to not implement them, it’s not a hard problem.

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

#78

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.

I'm using caps right now, they work- it shuts down all resources attached to the billing account if it goes over. There are many levels of alerts before it hits that though.

its on the "total spend" of a billing account level though, and obviously you'd have to be a billing administrator, so to work with it would is awkward; many billing accounts across disparate projects is basically the only way.

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

#79
post #25

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…

That is an argument for why these overages occur. It isn't an argument for why customers should eat that cost rather than Amazon. In fact Amazon is in a much better position than customers to absorb those costs. Sure, they'd have to increase rates slightly to cover it. But it would give customers peace of mind. And if the costs become exorbitant, Amazon is in a better position to improve their own systems to reduce t…

Should they simply automatically eat the costs then it would undoubtedly result in abuse. Just look at GitHub Actions.

Oh I didn't think I was starting 1000 instances of miners in the EC2 GPU cloud, it certainly exceeded my configured budget, please give my money back..

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

#80

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

I had been in the same position for about ten years until I set up a limited liability company. It does take some effort to set up and costs about $20/month[1], but to me the peace of mind is well worth it.

[1]: https://www.ukpostbox.com/address/business-address-service

Post reply on HN