An AWS user received a budget alert indicating forecasted charges of $3,005,575,870.47. Amazon's support AI suggested this might indicate a billing or metering error, prompting the user to seek clarification.
An AWS user reported receiving a budget alert indicating a forecasted charge of over $3 billion. This was unexpected, as the user had not actively utilized AWS in the past year. The budget threshold set by the user was just $5, highlighting the discrepancy.
In response to the inquiry, the AWS support AI suggested that the consistent daily costs observed since July 1 could point to a billing or metering error. It resulted in the generation of a support ticket by the AI, but the user awaited further feedback from AWS support.
To ensure security, the user disabled all AWS IAM roles and deleted known AWS resources, suspecting the billing anomaly might be linked to unauthorized usage. However, the user found no evidence of account hacking, creating further concern about the significant forecasted charges.
This incident raises questions about billing accuracy on AWS, especially if multiple users encounter similar issues. It highlights the importance of monitoring AWS usage and understanding billing forecasts to prevent potential overcharges.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
An AWS user received a budget alert indicating forecasted charges of $3,005,575,870.47. Amazon's support AI suggested this might indicate a billing or metering error, prompting the user to seek clarification.