I'm panicking over a $564 charge that appeared on my Mastercard after several months with essentially no usage. My usage history shows only about $0.66 in January and $0.02 in February, for roughly 8.2 GB-month of EC2-related storage. March through June show no usage, and I can't find any volumes, snapshots, instances, or other resources that would explain a large bill. The charge appeared on July 1 as "Amazon Web Services," using the same card and account associated with my previous small AWS charges, but there is still no matching invoice or bill in the billing console. I've opened several support cases but haven't received a response after three days. What could cause this, and how can I verify whether the charge is actually from AWS?
3 Answers
The usage shown doesn’t support a $564 charge. EC2-Other measured in GB-month is generally storage-related, such as EBS volumes or snapshots, and 8.2 GB-month would be around the cents-level amount shown in your table. Storage would not normally turn that into hundreds of dollars without a much larger amount of data or another billing category. Check whether the card transaction has a matching invoice number, billing account, and billing period. If there is no invoice in the account, question whether the card transaction is actually tied to this AWS account rather than merely using the same card.
AWS usage normally accumulates in the billing tools, then the billing period closes and an invoice is generated before or around the time the payment is collected. A card charge with no matching invoice is unusual. Check the billing console’s Payments, Invoices, Bills, and Cost Explorer sections separately, and confirm that you’re viewing the payer account and the correct date range. If this is a consolidated billing setup, the charge could belong to another linked account.
The console only shows the small EC2-Other amounts, and I don’t see any matching usage for volumes, EBS, snapshots, or other services. The card charge is far higher than the displayed costs.
A delayed charge or a consolidated payment is possible, but the amount should still be traceable to an invoice and account-level billing record. Make sure you have administrative access to the payer account, check linked accounts and alternate regions, and review Cost Explorer by service, usage type, and account rather than only the EC2-Other summary. If nothing matches, treat the card transaction as unverified rather than assuming the small storage charge somehow became $564.
The card descriptor says Amazon Web Services, and it’s the same Mastercard used for my earlier AWS charges. The amount appeared on July 1, but I still can’t find a corresponding invoice or line item in the console.