Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

My load balancer target group shows up as "Not available" - how do I debug this further?

I've created a Network Load balancer and a target group. Then I try to create a listener for the load balancer, but the target group is showing up as "Not available" in the pulldown menu.

What can be my next step to debug this? Much appreciate the help.

Picture: https://ibin.co/w800/3vKxtcYYs3mg.jpg

like image 984
do-leap Avatar asked Mar 18 '18 20:03

do-leap


People also ask

How do I add a target group to an existing load balancer?

In the navigation pane, under Load Balancing, choose Target Groups. Choose Create target group. For Choose a target type, select Instances to register targets by instance ID; IP addresses to register targets by IP address; or Application Load Balancer to register an Application Load Balancer as a target.

What is difference between load balancer and target group?

Yes, the load balancer is an EC2 instance to provide the networking and compute services needed for load balancing. This also means that there is a per hour charge for the load balancer EC2 instance. A Target Group is used to route requests to one or more registered targets (your backed EC2 instances).

How many target groups can be attached to a load balancer?

You can specify up to 10 target groups. To get the ARN of a target group, use the Elastic Load Balancing DescribeTargetGroups API operation.

What is target group in load balancer?

A target group tells a load balancer where to direct traffic to : EC2 instances, fixed IP addresses; or AWS Lambda functions, amongst others. When creating a load balancer, you create one or more listeners and configure listener rules to direct the traffic to one target group.


1 Answers

The UI appears to have changed, but I had a similar problem (NLB showing an unassigned target group grayed out in the listener's dropdown). When starting over, I had to make sure that the target group protocol was TCP or whichever protocol the balancer would be forwarding to.

screenshot of AWS Load Balancer's Add Target Group form, with protocol/port selectors

The Add Listener page also has Protocol and Port fields, and any groups with the wrong protocol were unavailable. Selecting an available target group and then changing to a different protocol caused the page to show an error like "TCP_UDP listeners cannot forward traffic to TCP target groups. You must select a compatible target group or change the listener protocol."

screenshot of the protocol/port selectors in AWS Load Balancer's Add Listener form

like image 145
MBer Avatar answered Sep 20 '22 00:09

MBer