Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Can't register EC2 instance in ELB

I'm trying to set up an AWS environment for the first time and have so far got a DNS entry pointing to a Classic ELB. I also have an EC2 instance running but I don't seem to be able to add the EC2 instance to the ELB in the UI. The documentation says that I can do this in the "Instances" tab in Load balancer screen but I don't have the tab at all. All I can see is Description | Listeners | Monitoring | Tags.

Does anyone have any ideas why the "Instances" tab night be missing from the UI?

like image 702
Andy Davies Avatar asked May 12 '17 09:05

Andy Davies


People also ask

How do I ssh into EC2 behind Load Balancing?

Right-click the instance ID for the Amazon EC2 instance running in your environment's load balancer, and then select Connect from the context menu. Make a note of the instance's public DNS address on the Description tab. Connect to an instance running Linux by using the SSH client of your choice, and then type ssh -i .

Why is my AWS instance not connecting?

The following are common reasons why EC2 Instance Connect might not work as expected: EC2 Instance Connect doesn't support the OS distribution. The EC2 Instance Connect package isn't installed on the instance. There are missing or incorrect AWS Identity and Access Management (IAM) policies or permissions.


1 Answers

There are now two different types of Elastic Load Balancer.

ELB/1.0, the original, is now called a "Classic" balancer.

ELB/2.0, the new version, is an "Application Load Balancer" (or "ALB").

They each have different features and capabilities.

One notable difference is that ALB doesn't simply route traffic to instances, it routes traffic to targets on instances, so (for example) you could pool multiple services on the same instance (e.g. port 8080, 8081, 8082) even though those requests all came into the balancer on port 80. And these targets are configured in virtual objects called target groups. So there are a couple of new abstraction layers, and this part of the provisioning workflow is much different. It's also provisioned using a different set of APIs.

Since the new Application Load Balancer is the default selection in the console wizard, it's easy to click past it, not realizing that you've selected something other than the classic ELB you might have been expecting, and that sounds like what occurred in this case.

like image 103
Michael - sqlbot Avatar answered Sep 30 '22 06:09

Michael - sqlbot