Charge for EC2 after i remove all resources

There are a few potential reasons why you might still be seeing charges for EC2 after removing all visible resources:

1. Billing lag: Even after terminating resources, charges may still appear on your bill for the current billing period. AWS charges for the time resources were active, even if they're no longer running.

2. Hidden resources: Some resources may not be immediately visible in the EC2 dashboard. Check for:

   • EBS volumes that weren't deleted when instances were terminated
   • Snapshots of EBS volumes
   • Elastic IP addresses not associated with running instances
   • NAT gateways or other networking components

3. Regional resources: Ensure you've checked for resources across all AWS regions, not just your primary region.

4. Reserved Instances: If you purchased Reserved Instances, you'll be billed for these regardless of whether you're using them.

5. Data transfer charges: You may incur charges for data transferred out of AWS to the internet or between regions and Availability Zones.

To resolve this:

1. Use the AWS Cost Explorer to identify specific services and regions incurring charges.
2. Check your billing dashboard and expand the Elastic Compute Cloud section to see which regions have EC2 resources.
3. Use the AWSSupport-ListEC2Resources tool to find any hidden resources.
4. If you still can't locate the source of charges, consider opening a support case with AWS for further assistance.

Remember, most AWS services charge on an hourly basis, so you'll only be billed for the time resources were active. If you're within Free Tier limits, you shouldn't be charged at the end of the month unless you launch new resources.
Sources
Keep being charged after closing EC2 services | AWS re:Post
Why am I being charged for Amazon EC2 when all my instances were terminated? | AWS re:Post
Stop being charged for EC2 with no instances - Please Help | AWS re:Post
I'm being charged with no active EC2 instances | AWS re:Post