An AWS billing bug caused some customers to see cloud-cost estimates worth billions or even trillions of dollars. The incorrect figures appeared in Amazon’s AWS Billing and Cost Management Console on July 17.
Amazon temporarily paused billing estimates after detecting the issue. Although the displayed amounts caused widespread alarm, the company said AWS services continued to operate normally.
Some users shared screenshots of the false charges online. One estimate reached almost $495 billion, despite the customer paying only $1.63 in the previous month.
Customers Panicked Over Massive AWS Bills
The AWS billing bug affected an undisclosed number of customers. In some cases, estimates rose from ordinary monthly costs to sums that no individual or business could realistically owe.
One user said their account showed a bill of nearly $495 billion. Another reported an estimate of around $1.5 trillion. Meanwhile, a customer with an inactive personal AWS account received an alert for more than $26.5 million.
Naturally, the unexpected alerts caused panic. Several customers said they initially believed something was seriously wrong with their accounts or cloud environments.
AWS bills can change quickly when customers accidentally leave expensive resources running. Therefore, users often take high-cost alerts seriously and act immediately to avoid further charges.
Amazon Paused Billing Estimates
Amazon noticed the problem on July 17 and confirmed that some customers were receiving inflated estimates through the AWS Billing and Cost Management Console.
The company then paused the affected billing estimates to stop additional inaccurate figures from appearing. Its engineering teams traced the problem to the console’s billing computation subsystem.
However, finding the source of the fault did not immediately resolve it. Amazon needed several hours and more than one attempt before the AWS billing bug was fully fixed.
By July 18, the company said the console was working properly again.
AWS Services Remained Online
Amazon said the billing issue did not disrupt the underlying AWS platform. Customers could still access and use their cloud services while the company worked on the fix.
The company later apologised for the alarm caused by the incident. It also said it would conduct a detailed review to reduce the risk of similar problems in the future.
Amazon added that it would improve its response procedures for billing-related incidents. However, it did not disclose how many accounts were affected.
The company also did not say whether any users had their AWS accounts suspended or paused because of the incorrect estimates.
False Estimates Could Still Cause Business Problems
Although the enormous bills were not real, the AWS billing bug could still have had practical consequences for some organisations.
A business that sees an unexpected charge may immediately turn off cloud resources, databases, applications, or other services. That decision could prevent further spending if the charge were genuine. On the other hand, it could also cause website outages, interrupted operations, and lost revenue.
For this reason, organisations should verify unusual AWS charges through their cost and usage data before disabling critical resources. They should also use billing alerts, budget controls, and internal escalation procedures to assess potential incidents quickly.
In this case, the displayed figures were clearly unrealistic. Still, the incident shows how even a temporary billing error can create major concern for cloud customers.
0 responses to “AWS Billing Bug Shows Customers Fake Bills Worth Billions”