Find any Amazon Application Load Balancers (ALBs) and Network Load Balancers (NLBs) that appear to be idle and remove them from your account to help lower the cost of your monthly AWS bill.
By default, an AWS ALB resource is considered "idle" when it meets the following criteria:
- The sum of the requests made to the load balancer in the past 7 days is less than 100. The CloudWatch metric used to detect idle Application Load Balancers is RequestCount (Sum). This metric records the number of HTTP/HTTPS requests processed over a predefined time frame. It includes only the requests with a response generated by a target of the load balancer.
And an AWS NLB resource is considered "idle" when it meets the following criteria:
- The sum of the TCP connections initiated in the past 7 days is less than 100. The CloudWatch metric used to detect idle Network Load Balancers is NewFlowCount (Sum). This metric records the number of TCP connections (flows) established from clients to targets within a predefined time frame.
Note 1: Knowing the role and the owner of an AWS load balancer before you take the decision to terminate it is very important. For this rule, Cloud Conformity assumes that your ELBv2 resources are tagged with "Role" and "Owner" tags, which provide visibility into their usage profile and help you decide whether its safe or not to remove these resources from your account.Note 2: You can change the default threshold (i.e. 100) for this rule on the Cloud Conformity console and set your own value for the RequestCount/NewFlowCount metric to configure your load balancers idleness.
Regularly checking your AWS load balancers for the number of HTTP(S) requests and TCP connections completed, will help you efficiently identify and remove any idle ELBv2 resources from your AWS account in order to stop accumulating unnecessary service charges.
Case A: To find any idle Application Load Balancers within your AWS account, perform the following actions:
Case B: To find any idle Network Load Balancers within your AWS account, perform the following:
Remediation / Resolution
Option 1: Terminate the idle load balancers. To delete any Application Load Balancer or Network Load Balancer that is currently running in idle mode, perform the following actions:
Option 2: Disable the rule check. If the selected idle load balancer is needed (its role within your application stack is essential and the owner confirms it), you should turn off this conformity rule check for your AWS load balancers (ELBv2) from the Cloud Conformity console
- AWS Documentation
- Elastic Load Balancing FAQs
- CloudWatch Metrics for Your Application Load Balancer
- CloudWatch Metrics for Your Network Load Balancer
- Elastic Load Balancing Metrics and Dimensions
Unlock the Remediation Steps
Free 30-day Trial
Automatically audit your configurations with Conformity
and gain access to our cloud security platform.
You are auditing:
Idle Elastic Load Balancers (ELBv2)
Risk level: High