AWS Estimated Billing Data Error: A $1.7 Billion Mistake

Executive Summary:

• AWS is facing a $1.7 billion estimated billing data error due to unit errors in pricing plans.
• Customers have reported receiving inflated bills, with some exceeding millions of dollars.
• AWS is expected to fix the issue soon, but the error has already caused emotional distress and financial concerns for many users.

The Internet’s Verdict: 80% Angry, 20% Amused

The Issue Explained

According to forum voices, the error occurs when the unit type in the pricing plan is incorrect, causing the metering data conversion to fail.

Ive dealt with this error at AWS. It’s a unit error. In my case we _meant_ to charge like 5¢/GB, but missed the unit (GB), and then the billing system defaults to bytes. 5¢ per Byte of data transferred meant some customers were seeing MM bills within hours.

Customer Reactions

Customers have taken to forums to express their shock and frustration at receiving inflated bills.

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

Another customer reported waking up to a billing alarm email with a charge of $437 billion, which they found amusing but also alarming.

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

Focus Keyword: AWS Billing Error