Unexpected EC2 Charges

Question

I am reaching out to seek clarification regarding a charge of approximately $9 on my AWS bill for February 2025. I did not use any AWS services during this period, and I had already terminated all my EC2 instances prior to February. The only resources I had were two t2.micro instances in a stopped state, both of which fall under the free tier.

Given that I had no active usage, I’m unable to understand the reason behind these charges. I have already paid the bill, but I would appreciate it if you could help me identify the source of these charges. If this was an error, would it be possible to receive a refund?

re:Post Agent · Answer

I understand your concern about unexpected charges on your AWS bill. Even when you believe you have terminated all active services, there are several reasons why you might still see charges for EC2:

1. Stopped instances: While your t2.micro instances were stopped and fall under the free tier, the associated EBS (Elastic Block Store) volumes may still incur charges. Stopped instances continue to retain their EBS volumes, which can result in storage costs.

2. Elastic IP addresses: If you allocated Elastic IP addresses and didn't release them, these can result in charges even when not associated with running instances.

3. Snapshots: Any EBS snapshots you may have created will continue to incur storage charges, even if the original volumes or instances have been terminated.

4. Data transfer: There might be charges for data transfer between AWS regions or out to the internet, even if instances are not running.

5. Other EC2-related resources: Services like load balancers or NAT gateways, if created, can continue to generate charges.

6. Regional resources: Ensure you've checked for resources across all AWS regions, not just your primary region.

To identify the source of these charges:

1. Review your detailed bill in the AWS Billing Dashboard, focusing on the EC2 section.
2. Use the AWS Cost Explorer to break down charges by service and usage type.
3. Check each AWS region for any lingering resources like unattached EBS volumes, snapshots, or Elastic IPs.

Regarding a potential refund, AWS may consider refunding charges in certain circumstances, especially for new users or if there's been a misunderstanding about resource usage. I recommend contacting AWS Support directly to discuss your situation. They can provide a detailed breakdown of the charges and advise on the possibility of a refund.

For future prevention of unexpected charges:
1. Fully terminate (not just stop) instances you're not using.
2. Delete unnecessary EBS volumes and snapshots.
3. Release any unattached Elastic IP addresses.
4. Set up AWS Budgets or billing alerts to notify you of any unexpected usage.

Remember, it's crucial to regularly review your AWS account and clean up any unused resources to avoid unexpected charges.
      
**Sources**  
[Unexpected billing because of EC2, VPC, and Data Transfer | AWS re:Post](https://repost.aws/questions/QUkWDjz9JjS4Gyl3fFeEouXA/unexpected-billing-because-of-ec2-vpc-and-data-transfer)  
[Billing misunderstand | AWS re:Post](https://repost.aws/questions/QUovcjokJRTCup01P2vlD9Jw/billing-misunderstand)  
[Billing without active service | AWS re:Post](https://repost.aws/questions/QUMUfmaNGlTaywxjDNh04e_g/billing-without-active-service)  
[Charge for EC2 after i remove all resources | AWS re:Post](https://repost.aws/questions/QUYQGhxRNKQG6753BIWZib7g/charge-for-ec2-after-i-remove-all-resources)

Unexpected EC2 Charges

Add your answer

Relevant content