If you owe the bank $100, that's your problem. If you owe the bank $1.7 billion, that's the bank's problem.
Not if you’re Elon Musk
AWS: Inaccurate Estimated Billing Data – $1.7 billion
261–270 of 793 posts
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#262Earlier quoted context omitted.
Worth a shot to give them a call and explain that. They can probably adjust it down to 100 billion.
What is this, US health care negotiations?
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#263Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#264Apparently what used to be `GB of storage consumed` is confused with `Bytes of storage consumed`, leading to a cool off by 2*30 error. > You're right to question my calculation. The MCP server failed to connect when I tried to look up the field definition. I guessed instead of validating. This is on me. But look at all the revenue!
AI slop. Or just a distracted dev
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#265Tale as old as time. When I was coming up it took a $20-40/m investment to get a "dedicated" server that you could start tinkering around on. When you couldn't afford that, you bricked the family PC trying to figure out how to configure your own LAMP stack.
Nowadays you just have to risk accidentally billing your parents CC the tune of multi-generation wealth to get that real-world experience.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#266My 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!
[deleted]
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#267Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#268I got 3 consecutive emails warning that my budget crossed its $18 threshold. Opened it up: cost was 78 million. Thought it was a phishing attempt, logged into my actual account, and... still 78 million. EMOTIONAL DAMAGE.
Wanna bet the description of this job post will be updated by the end of the day?
"Software Development Engineer II, AWS Invoicing"
https://www.amazon.jobs/de/jobs/10428480/software-developmen...
"...Our platforms are powered by generative AI, large language models, knowledge graphs, and agentic architectures that dynamically compose specialized agents based on context. We apply these capabilities across three reinforcing areas: intelligent launch readiness — where autonomous AI agents analyze, generate, and validate the information needed to go live in a new market; cloud-native service orchestration — where configuration-driven microservices replace per-launch bespoke engineering with centralized, reusable capabilities so that expanding into a new country becomes a zero-code configuration change rather than a development cycle; and continuous validation..."
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#269I got a 20K bill once and it was actually drafted from my bank account. It took me a couple of months and involving the office of the AG of my state to get the issue resolved and get my money back. Since then I never touched any AWS product, moved my small stuff to Azure. It’s been years since AWS have these issues with billing, you can find the stories online, students billed 60K for a compromised account launching…
That’s why you always use a spend limited card with variable cost providers.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#270My estimate was over 2T. Talk about waking up quickly...
For science I hope people are trying to figure out now how they could manage to rack up a 2T bill in a month.
My immediate thought was that someone managed to get an access key, stuffed a ton of data in there, and then was doing a ridiculous amount of egress. That was the only way I could conceivably coming up with anywhere near that much cost.