EBS Volume being billed but not found

When you terminate an EC2 instance, the attached EBS volumes are not automatically deleted unless they were specifically configured to delete on termination. This is a common scenario where you continue to be billed for EBS volumes even after the instance is terminated.

Based on your situation, here are the key points to understand:

Why you're still being billed: EBS volumes exist independently of EC2 instances and continue to incur charges even when detached or after the associated instance is terminated. The volume persists in your account until you explicitly delete it.

Troubleshooting steps:

1. Check all regions: EBS volumes are region-specific resources. Even though you've checked us-east-1, the volume might exist in a different AWS region. Make sure to check all regions in your account, as you can only see resources in the region you're currently viewing in the console.

2. Verify the Cost Explorer details: Look at your AWS Cost Explorer or billing dashboard more carefully to identify which specific region is generating the EBS charges. The billing information should indicate the exact region where the volume exists.

3. Look for detached volumes: In the EC2 console under "Volumes," make sure you're looking for volumes with a state of "available" (detached) rather than just "in-use" volumes. Detached volumes still incur charges.

4. Check EBS snapshots: While you mentioned checking snapshots, note that EBS snapshots also incur storage charges separately from volumes, though typically at a lower rate.

Once you locate the volume in the correct region, you can delete it to stop the charges. Just be certain you don't need the data before deletion, as this action is irreversible.

If it's not clear on which region the EBS volume is, you can go to EC2 console and than navigate to AWS Global View. This will show you the whole summary of the account including number of EC2, EBS, etc in all regions. Example screen shot below.