Skip to main content
Every load balancer has an hourly charge, whether or not it handles any requests. Load balancers are often left behind after an application is moved or retired. nOps finds Application, Network, Gateway and Classic Load Balancers that have been billed for months without any traffic, and shows their hourly charge as the saving.

Why it matters

An idle load balancer does nothing but cost money, and it is easy to miss among dozens of active ones.

How nOps finds it

nOps reads the last 90 days of billing for each load balancer. One is flagged when its hourly charge was billed on at least 85 of those days and in the last 2 days, and no line on the load balancer recorded any usage (processed bytes, capacity units or data transfer) in the whole 90 days. The saving is the hourly charge billed in the last 30 days, and must be at least $1.

Before you start

Permission to delete the load balancer (elasticloadbalancing:DeleteLoadBalancer). Find out who owns it, and whether it was created by Kubernetes, CloudFormation or Terraform.

How to implement

  1. Check the load balancer’s tags. If it has elbv2.k8s.aws/cluster, kubernetes.io/cluster/... or aws:cloudformation:stack-name tags, remove it from its owner (the Kubernetes Ingress or Service, or the stack) instead of deleting it directly.
  2. Confirm it is not a standby or disaster-recovery load balancer, and that no DNS record points to it.
  3. Turn off deletion protection if it is on.
  4. Delete it: EC2 → Load Balancers → Actions → Delete, or aws elbv2 delete-load-balancer --load-balancer-arn ARN (aws elb delete-load-balancer --load-balancer-name NAME for a Classic Load Balancer).
  5. Remove it from Terraform or CloudFormation so it is not recreated.

Risks and considerations

  • Deleting a load balancer cannot be undone. A new one gets a new DNS name.
  • A load balancer deleted by hand that Kubernetes or a stack manages is recreated, or leaves that tool out of sync.
  • Target groups are not deleted with the load balancer; remove them separately if they are no longer used.

FAQs

Yes, for example a disaster-recovery standby. That is why nOps asks you to confirm before deleting.