AWS billing glitch overcharged customers by billions — a reminder to audit cloud invoices

In mid-July it emerged that a technical fault in Amazon Web Services' billing system overcharged some customers several times their normal spend — totaling billions of dollars combined. AWS acknowledged the error and promised refunds, but the incident exposed a systemic issue: most businesses take cloud bills at face value and rarely check them line by line, since manual reconciliation eats hours of accounting time.

For Kazakhstani companies using cloud infrastructure — AWS, Azure, Google Cloud, or local providers — this is a reason to set up regular invoice reconciliation against actual usage, ideally monthly rather than after the charge has already hit the card. Billing errors aren't unique to AWS, and the larger the company, the more an oversight costs.

This is exactly the kind of surprise a recurring check protects against: in 1Cifer an agent compares periods and raises an invoice that has suddenly jumped out of its usual range — the day it arrives, not at quarter-end, after the money is already gone.