Earlier quoted context omitted.
AI slop. Or just a distracted dev
>> Or just a distracted dev And a distracted tester? And a distracted pipeline of regression tests? No, the truth is way worst...
AWS: Inaccurate Estimated Billing Data – $1.7 billion
311–320 of 793 posts
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#312I feel much better after seeing the $B estimates here; I only have an estimate of $34M so far Folks can track it directly on AWS Health: https://health.aws.amazon.com/health/status
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#313I realized recently that Whole Foods no longer automatically and reliably detects your Chase Amazon Prime credit card when paying. So they don’t give you the discounted pricing automatically. I wonder how many customers are checking out the way they always do and are paying full price when, for years and decades, this worked fine. The customer service people I talked to in the grocery store said this changed sometime…
Either that or 1000’s of small claims court cases.
Even with arbitration, the overhead of dealing with that would be crippling. Hopefully someone over there decides to do the right thing, and auto-refund.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#314Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#315Earlier quoted context omitted.
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.
Realtime billing seems entirely within the abilities of AWS. "Limits except for Storage" seems even easier - I don't think I've ever heard of a storage-based billing story, although I'm sure one or two exist
Also many places I’ve worked, storage is a huge part of the spend but that depends a lot on what you do. e-commerce doesn’t use a ton of it, but if you handle user-generated content or do any kind of training (LLM, computer vision, etc) then you can very much end up in a place where storage becomes a top line number for infra spend.
GitHub pre-Copilot was probably like that. They host a shitload of data, most of which is just at rest the majority of the time. Storage and networking are probably the majority of their infra costs.
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#316Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#317Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#318Earlier quoted context omitted.
That job description feels so far beyond parody that I could scarcely believe it until opening the link! What a world.
It gets worst: "Senior Software Development Manager, AWS Global Bill Generation" https://www.amazon.jobs/de/jobs/10471948/senior-software-dev... "We're transforming from monthly batch processing and manual war rooms to continuous billing, autonomous agents, and self-healing infrastructure. We believe operational burden is a technical problem, not a staffing problem" This looks clearly...a staffing problem...
Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#319Re: AWS: Inaccurate Estimated Billing Data – $1.7 billion
#320Earlier 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.
That would mean an outage but that is still better than going bankrupt and teach you a thing or two about monitoring.