Unexpected Charges for Terminated EC2 Instance

Hello.

Have you checked to see if there are any remaining EBS volumes or snapshots in another region?
If it is an EBS volume, you can check which region it remains in by opening the global view from the URL below.
In the case of snapshots, you cannot view them from the global view, so you need to check each region by changing them.
https://us-east-1.console.aws.amazon.com/ec2globalview/home?region=us-east-1#

When was the last time you deleted EC2 or EBS?
If the deletion occurred during August, it would not be strange for it to be listed on the August bill.
If you cannot find any resources related to EBS after searching further, I recommend that you open a case with AWS Support under "Account and billing".
Inquiries under "Account and billing" can be made free of charge.
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html

Hello @Riku_Kobayashi @Parthasardi and Thanks for your answer,

@Riku_Kobayashi based on Cost explorer interfaces the charges are in US East (N. Virginia), us-east-1 and the screenshots in my question is for us-east-1. I've checked also your link and i found no resources enabled.

@Parthasardi there is no volumes or snapshots under Elastic Block Store.

Hello,

please try this solution it will be helpful for you.

To Resolve your issue with unexpected charges for terminated EC2 instances.

Check for Unused EBS Volumes:

1. Sign in to the AWS Management Console.
2. Navigate to the EC2 Dashboard.
3. Click on Elastic Block Store in the left sidebar, then select Volumes.
4. Look for any volumes that are not attached to any instances.

Delete Unused Volumes:

1. Select the unattached volumes.
2. Click on Actions and then Delete Volume.
3. Confirm the deletion when prompted.

Check Snapshots:

1. Go to Elastic Block Store and select Snapshots.
2. Review and delete any old snapshots you no longer need.

Review Billing Details:

1. Go to Cost Explorer in the AWS Management Console.
2. Look under Usage Type to find details related to "EBS .gp3".
3. This will help you understand if there are any other associated costs.

if you want more information please go through the AWS Document.

https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/checklistforunwantedcharges.html

Remember that while the EC2 instance has been terminated, the associated Elastic Block Store (EBS) volumes weren't automatically deleted. By default, when you terminate an EC2 instance, its EBS volumes may continue to exist unless you specifically check the option to delete them upon termination.

Please check the following:

Check for Remaining EBS Volumes: Head over to the EC2 Dashboard and look under Volumes. If there are any remaining volumes, they could still be generating charges. You can delete them manually if they’re no longer needed.

EBS Snapshots: Similarly, if you’ve created any snapshots of the instance, those will also incur charges. You can review your snapshots under the Snapshots section in the EC2 Dashboard and delete any that are no longer necessary.

Elastic IPs: If you were using an Elastic IP with the instance, make sure it was released. Otherwise, AWS continues to charge for unused but allocated Elastic IPs.

You can also use AWS Cost Explorer to break down the charges further and confirm that they are indeed from EBS volumes or other resources linked to the terminated instance.