Let us take a closer look at the ELB listener aws and how to configure it with the support of our AWS support services Bobcares.

ELB Listener AWS: Configuration

We must first configure one or more listeners for the Classic Load Balancer before using the Elastic Load Balancing. A listener is a process that monitors for connections.

It is set up with a protocol and a port for front-end connections (client to load balancer) and a protocol and a port for back-end connections (load balancer to back-end instance).

Elastic Load Balancing is compatible with the following protocols:

• HTTP
• HTTPS (secure HTTP)
• TCP
• SSL (secure TCP)

To establish secure connections across the HTTP layer, the HTTPS protocol employs the SSL protocol. The SSL protocol can also be used to establish secure connections via the TCP layer for ELB listener aws configuration.

If the front-end connection employs TCP or SSL, the back-end connections may also employ TCP or SSL. If the front-end connection is HTTP or HTTPS, the back-end connection can also be HTTP or HTTPS.

Back-end instances can listen on ports 1-65535 and the load balancers can listen on the following ports:

• [EC2-VPC] 1-65535
• [EC2-Classic] 25, 80, 443, 465, 587, 1024-65535

Contents

InstancePort

The port on which the instance is listening. The type of the port is Integer and its valid range is a minimum value of 1. And the Maximum value is 65535. and it is necessary for ELB listener AWS.

InstanceProtocol

HTTP, HTTPS, TCP, or SSL should be used to route traffic to instances. The back-end protocol must be TCP or SSL if the front-end protocol is TCP or SSL. The back-end protocol must be HTTP or HTTPS if the front-end protocol is HTTP or HTTPS.

If another listener with the same InstancePort uses a secure InstanceProtocol (HTTPS or SSL), the listener’s InstanceProtocol must be secure as well.

If another listener with the same InstancePort uses HTTP or TCP, the listener’s InstanceProtocol must also be HTTP or TCP. The type is String in this case, and it is not required.

LoadBalancerPort

The port that the load balancer is listening on for elb listener aws. We can specify any port from 1-65535 on EC2-VPC. We can provide any port from the list on EC2-Classic: 25, 80, 443, 465, 587, 1024-65535.

Type: Integer

Required: Yes

Protocol

HTTP, HTTPS, TCP, or SSL is the load balancer transport protocol to utilize for routing. It is of the String type and is necessary.

SSLCertificateId

The server certificate’s Amazon Resource Name (ARN). We don’t need it, as the type is String.

AWS::ElasticLoadBalancing(ELB)::LoadBalancer Listeners

A listener for the Classic Load Balancer is specified for elb listener aws. In the AWS CloudFormation template, we may declare this object using the following syntax:

JSON

{
"InstancePort" : String,
"InstanceProtocol" : String,
"LoadBalancerPort" : String,
"PolicyNames" : [ String, ... ],
"Protocol" : String,
"SSLCertificateId" : String
},

YAML

InstancePort: String
InstanceProtocol: String
LoadBalancerPort: String
PolicyNames:
- String
Protocol: String
SSLCertificateId: String

Properties

InstancePort

The port on which the instance is listening.

Minimum: 1

Maximum: 65535

InstanceProtocol

HTTP, HTTPS, TCP, or SSL should be used to route traffic to instances. The back-end protocol must be TCP or SSL if the front-end protocol is TCP or SSL. The back-end protocol must be HTTP or HTTPS if the front-end protocol is HTTP or HTTPS.

If another listener with the same InstancePort uses a secure InstanceProtocol (HTTPS or SSL), the listener’s InstanceProtocol must be secure as well.

If another listener with the same InstancePort uses HTTP or TCP, the listener’s InstanceProtocol must also be HTTP or TCP.

LoadBalancerPort The port to which the load balancer listens. We can specify any port from 1-65535 on EC2-VPC. We can provide any port from the following list on EC2-Classic: 25, 80, 443, 465, 587, 1024-65535.

PolicyNames

The policy names to associate with the listener.

Protocol,

HTTP, HTTPS, TCP, or SSL is the load balancer transport protocol to utilize for routing.

SSLCertificateId

The server certificate’s Amazon Resource Name (ARN).

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude we have now learned more about the ELB Listener AWS and the configurations necessary to set it up with the guidance of our AWS support Services at Bobcares.