- Newest
- Most votes
- Most comments
Is it the compute section that is showing you are near your Free Tier limit, or something else (you also get EBS storage and public IPv4 addresses under Free Tier)?
It's worth checking you don't have any EC2 instances running in other regions https://repost.aws/knowledge-center/find-ec2-instance
EC2 Global View will show all EC2 resources in all regions https://console.aws.amazon.com/ec2globalview/home?region#
Have you been running any EC2 instances earlier in the month? 85% of your Free Tier allowance of 750 hours = 637.5 hours, so if you had (for instance) run 2 EC2 instances for 319 hours each at the start of the month, and then terminated both of them, cumulatively your total usage would be at that figure.
By following this reasons you can find the answer: =>If you don't have any active EC2 instances but are still seeing usage in your billing section, there could be a few reasons: Stopped Instances Still Incurring Charges: While stopped EC2 instances do not incur charges for the instance itself, you may still be charged for associated resources, such as Elastic IPs, EBS volumes, or data transfer.
Previous Usage: The usage reported might include activity from earlier in the month before you terminated or stopped the instances.
Other AWS Services: The 85% MTD usage might reflect usage from other services beyond EC2, such as RDS, Lambda, S3, or any other AWS service that you might have used.
Free Tier Limits: If you are within the AWS Free Tier, and your usage exceeds the free limits, you might see charges even if no active instances are running.
Reserved Instances or Savings Plans: If you have any reserved instances or savings plans, the billing might show usage even without active instances, as you are paying for reserved capacity.
Monitoring Services: Tools like CloudWatch that monitor your infrastructure can also incur costs.
You can check your AWS billing dashboard to get a detailed breakdown of your charges and usage by service. This will help you identify the exact source of the charges.
Hello,
1/ I would confirm if your last known EC2/EBS usage did not occur in the same billing month.
2/ Check all regions and confirm there isn't any EC2/EBS usage.
3/ Confirm if the usage is for EC2 or EC2-Other (EBS and EC2 related charges). You can filter this in Cost Explorer.
4/ Consult this public documentation: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/checklistforunwantedcharges.html#checkec2instances
Hope this helps!
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 14 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago