Cloud Cost Analyzer detects load balancers with no targets and those with near-zero traffic, plus orphaned target groups, and estimates the monthly cost of each so you can retire them with confidence.
$ cca scan --provider awsRead-only, runs in about 5 minutes. Free tier, no credit card.
Read the deep dive: Idle load balancers you forgot to delete →
An Application or Network Load Balancer costs roughly $16 to $27 per month in base hourly charges alone, before capacity units. An idle balancer with no traffic still incurs the full base charge until you delete it.
Check for no registered or no healthy targets and near-zero request count over a representative period. Cloud Cost Analyzer surfaces both signals so you can confirm a balancer is truly unused before removing it.
Often yes. A single Application Load Balancer can front many services using host-based and path-based routing rules, replacing several balancers and their per-balancer base charges.
Idle gateways and avoidable data-processing charges, one per AZ.
Over-provisioned classes, non-Graviton, and Multi-AZ on non-prod.
Orphaned volumes, old snapshots, and gp2 you never moved to gp3.
Cold data sitting in Standard with no lifecycle policy.
Idle and oversized instances, previous-gen types, 24/7 dev boxes.
Oversized instances, Serverless v1, and I/O-Optimized breakevens.
Idle cache clusters and oversized, non-Graviton nodes.
Idle distributions and price classes wider than your audience.
On-demand billing on steady workloads, and unused indexes.
Over-provisioned memory and x86 functions that could be arm64.