- Newest
- Most votes
- Most comments
Even when using AWS Free Tier resources, you might still see charges for several reasons. Looking at your bill, the "EC2 - Other" category is likely the source of your charges, despite staying within the 750 hours of t2.micro usage.
Here are the most common reasons for unexpected charges while on the Free Tier:
-
EBS volumes: While you mentioned using 8GB of EBS storage, the Free Tier typically covers only standard EBS volumes. If you're using a different type (like gp2 or gp3), you might incur charges.
-
Elastic IP addresses: If you allocated an Elastic IP address but didn't attach it to a running instance, this would generate charges.
-
Snapshots: Any EBS snapshots you created would be billed separately.
-
Data transfer: While some data transfer is included in the Free Tier, exceeding those limits results in charges.
-
Resources in multiple regions: If you have resources deployed across different AWS regions, the Free Tier limits apply cumulatively.
To resolve this issue:
-
Check your AWS Billing Dashboard for a detailed breakdown of what's generating the "EC2 - Other" charges.
-
Ensure you've terminated (not just stopped) any instances you're not using.
-
Delete any unnecessary EBS volumes, snapshots, or release unattached Elastic IPs.
-
Set up AWS Budgets or Free Tier usage alerts to be notified before exceeding limits in the future.
If you believe the charges are incorrect, you can contact AWS Support through the Support Center by creating a case with "Billing" as the issue type to request a review of the charges.
Sources
Been Bill, but on the Free Tier | AWS re:Post
Getting billed for free tier ? | AWS re:Post
I have a 3 $ bill even after using only free Tier resources | AWS re:Post
Why have I been billed without running any instances? | AWS re:Post
Billing misunderstand | AWS re:Post
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
