Skip to main content

πŸ›‘οΈ AWS ELB Application Load Balancer is idle🟒

Logic​

Similar Policies​

Description​

Open File

Description​

This policy identifies AWS Elastic Load Balancers that are considered idle, including Application Load Balancers (ALBs) and Classic Load Balancers (CLBs). A load balancer is classified as idle if it has processed zero requests (that is, the RequestCount metric equals 0) over a 30 days period.

Rationale​

Idle load balancers continue to incur hourly charges even when they are not serving traffic. Identifying and decommissioning unused ALBs and CLBs helps reduce unnecessary costs, improve resource hygiene, and optimize overall AWS spending.

Audit​

This policy applies only to Application and Classic Load Balancers.

AWS Elastic Load Balancer is flagged as INCOMPLIANT if its 1-Month Request Count metric is less than or equal to 0.

An ELB is marked as INAPPLICABLE if its Created Time is less than 30 days ago.

Remediation​

Open File

Remediation​

Decommission idle Elastic Load Balancers​

Remove idle Application and Classic Load Balancers to eliminate unnecessary costs. Before deletion, verify that the load balancer is no longer required and is not associated with any active applications or dependencies.

From Command Line​
Application Load Balancers (ALB)​
aws elbv2 delete-load-balancer \
--region {{aws-region}} \
--load-balancer-arn {{application-load-balancer-arn}}
Classic Load Balancers (CLB)​
aws elb delete-load-balancer \
--region {{aws-region}} \
--load-balancer-name {{classic-load-balancer-name}}

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
πŸ’Ό Cloudaware Framework β†’ πŸ’Ό Waste Reduction28no data