Overview
- The Billing and Cost Management console and Cost Explorer began showing wildly inflated estimated charges on late Thursday, July 16, with reported figures ranging from millions to trillions of dollars.
- AWS identified the error as a unit‑pricing problem in its estimated billing computation subsystem and paused estimated computations while it rolled back changes and recomputed estimates.
- AWS said the displayed estimates did not reflect real usage or invoices and reassured customers they would not be billed for the erroneous amounts.
- The false estimates triggered panic that led some users to disable IAM roles, delete resources, or close dormant accounts despite AWS saying metering and actual invoicing were unaffected.
- The incident highlights concentration risk from reliance on a single cloud provider and underscores the need for independent cost monitoring, granular tagging, and stronger FinOps practices.