Skip to main content

Triage AWS Classic Load Balancer NO_INSTANCES_ATTACHED

  1. Configure AWS Classic Load Balancer
  2. Use Case for AWS Classic Load Balancer
  3. Triage Guides by Violation Type
    1. Triage AWS Classic Load Balancer NO_INSTANCES_ATTACHED

Triage Guide for NO_INSTANCES_ATTACHED

0) Understand​

Why should I care about fixing this issue?

Classic load balancers without any attached instances still incur costs. Eliminating these will reduce unnecessary expenditures.

1) Validate​

How am I sure that this alert is true and accurate?

  • Data Source: This policy uses AWS ELB API to fetch the load balancer details.
  • Manual Retrieval: You can manually verify by using AWS CLI: aws elb describe-load-balancers --load-balancer-names classic-load-balancer-1.
  • Scan Schedule: This is a reactive policy and evaluates whenever executed.

2) Triage​

What is the impact if it is unfixed?

  • Impact: If unfixed, you will continue to incur costs for an unused load balancer.
  • Progression: Costs will accumulate over time if the issue is not addressed.
  • Remediation Risk: Deleting an unused load balancer typically does not cause downtime, but ensure it is indeed unused.

3) Act​

What do I do to fix this alarm?

  • Step-by-Step:
    1. Confirm the load balancer is not in use by checking its traffic and attachment details.
    2. If confirmed unused, delete the load balancer using AWS Management Console or CLI: aws elb delete-load-balancer --load-balancer-name classic-load-balancer-1.

4) Reflect​

What should I do if this alarm wasn't a good use of time?

  • Adjust Thresholds: If you encounter false positives frequently, consider modifying the evaluation criteria or handling specific cases with exceptions if your operational scenario justifies temporary disuse.