Idle Load Balancer
A load balancer bills an hourly charge for as long as it exists, on AWS and Google Cloud alike, even when it carries no traffic.
Free to start. No card. The playground just needs your work email.
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete idle load balancer. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
On AWS, after a guided review where you confirm the change, ZopNight deletes the load balancer, then checks the change took. On Google Cloud, the finding carries the steps to do it by hand.
- Applies to
- Load Balancers on AWS, Global LB on Google Cloud, Regional Load Balancers on Google Cloud
- The fix, by hand on AWS
- Verify no scheduled or seasonal traffic is expected.
- Check target groups for healthy targets.
- If confirmed idle, delete the load balancer and associated target groups.
- Update DNS records if applicable.
On AWS, ZopNight does this for you after a guided review.
- Category
- Idle resources. Resources running but doing no useful work: zero invocations, no connections, no traffic.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-012RC-122RC-1255- Full reference
Idle Load Balancer GKE Idle Load Balancer GCP Idle Global Load Balancer
Related checks
See the idle resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.