cannot find any active c5.xlarge instances

Question

Why am I being billed for c5.xlarge EC2 instances on AWS when I cannot find any active c5.xlarge instances in my account or console, even after checking all regions?

usXCloudSec · Accepted Answer

This issue usually happens because the **EC2 instance is running in a different AWS region** **than the one you are currently viewing in the console.** AWS resources are isolated by region, so you need to check all regions to find where the c5.xlarge instance is running. Once **you identify the correct region**, you can go to that region in the AWS Management Console and delete or stop the instance to stop further charges.

re:Post Agent · Answer

There are several reasons why you might be seeing charges for c5.xlarge EC2 instances even when you can't find any active instances in your console:

1. Stopped but not terminated instances: If you have EC2 instances that are stopped but not fully terminated, you'll still be charged for the associated EBS volumes.

2. Recently terminated instances: You may still see charges for instances that were running earlier in the billing period but have since been terminated.

3. Hidden resources across regions: Ensure you've checked all AWS regions for resources. You can use EC2 Global View to see all your EC2 resources across all regions.

4. EBS volumes and snapshots: Even if instances are terminated, any detached EBS volumes or snapshots will continue to incur charges.

5. Elastic IP addresses: If you've allocated Elastic IPs but they're not associated with running instances, you'll be charged for them.

6. Account suspension/recovery issues: If your account was suspended and then recovered, instances might not be visible in the console but could still be accruing charges.

To investigate and resolve this issue:

1. Check your billing dashboard and expand the Elastic Compute Cloud section to see which regions have EC2 resources.

2. Use the AWS Cost Explorer to identify specific services and regions incurring charges.

3. Look for stopped instances, as these won't appear in the default "Running instances" view.

4. Verify your IAM permissions to ensure you have access to view all EC2 resources.

5. Check CloudTrail logs for any events related to stopping, terminating, or modifying your instances.

If you still can't locate the source of the charges after these steps, consider opening a support case with AWS Billing Support for further assistance.  
**Sources**  
[I'm being charged with no active EC2 instances | AWS re:Post](https://repost.aws/questions/QUsFlr3l9iQ4SSrrFlIb2scQ/i-m-being-charged-with-no-active-ec2-instances)  
[Billing without active service | AWS re:Post](https://repost.aws/questions/QUMUfmaNGlTaywxjDNh04e_g/billing-without-active-service)  
[EC2 Instance not visible on EC2 Dashboard on my account | AWS re:Post](https://repost.aws/questions/QUb0u6KVb0SfS5z6JkJjy7yw/ec2-instance-not-visible-on-ec2-dashboard-on-my-account)  
[Charge for EC2 after i remove all resources | AWS re:Post](https://repost.aws/questions/QUYQGhxRNKQG6753BIWZib7g/charge-for-ec2-after-i-remove-all-resources)  
[Why have I been billed without running any instances? | AWS re:Post](https://repost.aws/questions/QUFnCy9p2VTCaQKc6Irvi7kA/why-have-i-been-billed-without-running-any-instances)

cannot find any active c5.xlarge instances

Add your answer

Relevant content