Can AWS Refund Unexpected Charges from an Idle Resource?
Asked by
MellowPine47
I'm a student and recently discovered that AWS charged me about $1,100 over roughly 17 months—around $60 per month. Billing notifications were going to an email address I wasn't actively checking, so I didn't notice the charges building up. I believe an Elastic Container Service resource I started while learning or experimenting may have been left running, although I'm still working out exactly what caused the bill. This is my first billing issue, and I've now reviewed the account and shut everything down. Has anyone dealt with something similar? Is AWS likely to offer a courtesy credit or partial refund, and what's the best way to explain the situation in a billing support case?
Answers
Gather evidence before contacting support, such as CPU utilization, network traffic, task or container history, and screenshots showing that the service was mostly dormant. That can help demonstrate that the charges came from an overlooked experiment rather than intentional usage. Also set up a billing budget and alerts on an email address you actively monitor.
Reply to this answer
Open a billing support case and clearly explain that you’re a student, the notification email wasn’t being monitored, and this was an accidentally forgotten resource. Ask directly whether they can provide a one-time courtesy credit. There’s no guarantee, but the worst outcome is that they decline. Make sure you mention that you’ve already shut down the resources.
Reply to this answer
Support is the right channel for this. Keep the request factual and polite, identify the specific service and dates involved, and explain that this is your first billing incident. If you can pinpoint the resource, include its region and when it was stopped so the billing team can investigate more efficiently.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions