Total forecasted cost for current month
$477,000,039,440.24
Insane
AWS: Inaccurate Estimated Billing Data – $1.7 billion
141–150 of 793 posts
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#142From their status page
>The second path involves rolling back a recent change to the billing computation subsystem.
Want to bet AI code was involved?
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#143Woke up to a 100 billion dollars in S3, which is above the USD 4 alarm threshold I had set (I pay $0.55 monthly) . Some AI decided to prune the most impressionable of us.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#144Hey man AI makes mistakes sometimes that’s why you need to double check the output.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#145The panic was real. We read about keys getting stolen all the time. Was about to nuke my set up too.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#146Woke 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
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.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#147My estimate was over 2T. Talk about waking up quickly...
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#148They sent 3 warnings to my email, ok, I understand bugs happen (probably vibe-coded). But they didn't even send any notification that it's a bug. Going to leave AWS after that.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#149Is AWS in their "move fast and break things" era ?
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#150I've had a mysterious Neptune cluster appear on my billing. Never used it, no API key access (or IAM instance profile access, OIDC etc), nothing in my console shows I've ever had one in any region. Raised a case with support, they ignored it.