Looking for how to create additional listeners for AWS Elastic Beanstalk environments? We can help you with this!

As a part of our AWS Support Services, we often receive similar requests from our AWS customers.

Today, let’s see the steps followed by our Support Techs to help our customers to create additional listeners for Beanstalk environments.

Create additional listeners for AWS Elastic Beanstalk environments

We can’t create additional listeners using the aws:elbv2:listener:listener_port option setting or the Elastic Beanstalk console if we are using a shared load balancer with Elastic Beanstalk. This is because the load balancer is not managed by Elastic Beanstalk.

For creating additional listeners for an Elastic Beanstalk environment with a shared load balancer, we can use .ebextension custom resources.

Now let’s see the steps to create additional users by using .ebextension:

1. Firstly, we need to create an Application load balancer that includes a default listener and target group.

2. Secondly, we need to create a configuration file called additional-listener.config file and which should include the following:

Resources:
AdditionalHttpListener:
Type: AWS::ElasticLoadBalancingV2::Listener
Properties:
LoadBalancerArn:
"Fn::GetOptionSetting":
Namespace: "aws:elbv2:loadbalancer"
OptionName: "SharedLoadBalancer"
DefaultActions:
- Type: forward
TargetGroupArn:
Ref: AWSEBV2LoadBalancerTargetGroup
Port: 8080
Protocol: HTTP

3. Then we have to place this configuration file under the folder .ebextensions, and it is a part of the application source bundle.

4. After that, need to create a ZIP file of our updated application source bundle.

5. Using this ZIP file from the above step, update an existing Beanstalk environment or create a new Elastic Beanstalk environment.

For the Elastic Beanstalk environment with load balancer, the configuration file from step2 creates an HTTP listener on port 8080. Then the listener forwards all traffic to the default process. By using the AWS::ElasticLoadBalancingV2::ListenerRule resource definition of CloudFormation we can further extend this configuration file to add additional rules to the listener.

Note: It is always better to associate additional listeners with the lifecycle of the environment, and to remove the listeners if we terminate the environment.

[Need help with more AWS queries? We’d be happy to assist]

Conclusion

To sum up, today we discussed the steps followed by our Support Engineers to help our customers to create additional listeners for AWS Elastic Beanstalk environments.