Explanation
Why the waste happens and who it affects.
This often happens after application migrations, architecture changes, or testing activities. Even if no connections or traffic are passing through the CLB, it continues to incur baseline charges until manually deleted. Identifying and removing unused load balancers helps eliminate waste without impacting operations.
Billing model
The pricing dimensions that drive this cost.
Classic Load Balancers are billed per hour of operation and per GB of data processed, whether or not they are actively handling traffic. Inactive CLBs that continue to run without handling meaningful traffic still accrue hourly charges, resulting in unnecessary ongoing costs.
How to detect
5 checks to find it in your estate.
- Identify Classic Load Balancers with no active connections or data transfer over a representative time period
- Confirm there are no health checks, listener rules, or target instances relying on the load balancer
- Review application and infrastructure dependencies to ensure decommissioning will not disrupt services
- Check metadata, tags, or configuration history to determine whether the CLB was associated with a temporary or deprecated workload
- Validate findings with application owners or system architects before deletion
How to fix
How to remove the waste.
If confirmed to be inactive, delete the load balancer through the AWS Console, CLI, or API to stop further billing. Where possible, document the reason for decommissioning and update tagging or inventory systems to prevent reaccumulation of unused resources.
Documentation
Vendor references for pricing and configuration.