Live data from Hacker News

AWS: Inaccurate Estimated Billing Data – $1.7 billion

news.ycombinator.com

191–200 of 793 posts

Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion

#192

My estimate was only $21M (vs ~$0.01 average bill). Wish I had checked status sooner and saved myself the panic! My process went: verify email is not phishing (it was), login to console and check dashboard (same amount), attempt to understand cost (cost management kept contradicting itself), try to log support ticket and only on that part did I notice the status notification. At least I can breathe again now!

A friend of mine went through the same - he got an alert for bill over budget, he logged in and boom 107M$.

I was on the phone with him and we checked that he didn’t leak any APIs keys but no traffic at all. I even thought of a breach at a vendor he uses for some s3 stuff before I found this thread on HN.

Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion

#194
post #178

Earlier quoted context omitted.

I wonder how many people may have gotten an actual heart infarct because of that. There may be a person out there that may be dead as a result. It's entirely irresponsible of Amazon to even display such values to the user.

Reminds me of the time a Robinhood user killed themselves after Robinhood erroneously showed their account balance at -$730k. https://www.bbc.com/news/world-us-canada-55990461

In that case, they settled with Robinhood and FINRA fined Robinhood 70 million dollars.

https://edition.cnn.com/2021/07/01/business/robinhood-lawsui...

Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion

#195
post #138
post #98

Woke up to a billing alarm email. Thought I had leaked my AWS keys accidentally and somehow run up 437 billion dollars of charges. Joke's on them though, I don't have 437 billion dollars Anyways I didn't need coffee. That produced an adrenaline release unlike any I've experienced before. Thanks AWS

If you owe AWS 437k bucks, that’s a big problem for you If you owe AWS 437B bucks, that’s a big problem for AWS

Far less scary than a smaller amount

Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion

#198
post #96

Earlier quoted context omitted.

Can you not set spending limits in AWS?

No you can't. Spending limits imply realtime billing backend flows and they also imply deleting all your data so that you don't pay for storage.

I heard this false justification already in 2007, in spite of many customers asking for it.

Incidentaly, smaller competitors solved this issue decades ago, while the big cloud decided it is more convenient never to implement it.

Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion

#200

Earlier quoted context omitted.

I wonder how many people may have gotten an actual heart infarct because of that. There may be a person out there that may be dead as a result. It's entirely irresponsible of Amazon to even display such values to the user.

Ah, there'll be something in the TOS absolving them of responsibility.

Well... That depends on the country jurisdiction. And any ToS is bounded by law and can be questioned.
Post reply on HN