- Newest
- Most votes
- Most comments
I understand your frustration about seeing ECS charges even after removing your clusters and clearing your ECR repositories. This is a common issue that can happen for several reasons:
-
Billing lag: AWS may charge for resources that were active earlier in the billing cycle, even if they're no longer running. There can be a delay between resource deletion and when charges stop appearing.
-
Hidden resources: When you delete ECS clusters, there might be associated resources that aren't automatically deleted, such as:
- Load balancers that were created for your services
- Network interfaces with public IP addresses
- EBS volumes
- Elastic IP addresses
- Resources in other regions: Make sure to check all AWS regions for any remaining ECS-related resources that might be using services and generating charges.
To resolve this issue, I recommend:
-
Use the AWS Billing and Cost Management Dashboard to identify exactly which ECS-related services are generating charges.
-
Check for any lingering resources across all regions, including network interfaces, load balancers, and other components that might have been created by your ECS clusters.
-
Use the EC2 Global View to check for network interfaces across all regions that might be retaining public IP addresses (which now incur charges).
-
If you're still unable to locate the source of these charges after following these steps, contact AWS Support directly. They can provide a detailed analysis of your account and help identify any hidden resources causing these charges.
Remember that simply stopping or deleting the main service doesn't always stop all associated charges - you need to ensure all related resources are properly terminated as well.
answered 9 months ago
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 2 years ago

To confirm, you are checking daily charges and not monthly charges?