Over a million developers have joined DZone.

Configuring the Elastic Load Balancer of Your Elastic Beanstalk Application

Combine Spring Boot, AWS EC2, and Elastic Beanstalk to build a performant Java web service.

· Cloud Zone

Download the Essential Cloud Buyer’s Guide to learn important factors to consider before selecting a provider as well as buying criteria to help you make the best decision for your infrastructure needs, brought to you in partnership with Internap.

In my previous post, I showed how to run a Spring Boot application on AWS using AWS Elastic Beanstalk. In that post, I mention that it is possible to bypass the default NGINX instance on the EC2 instance and have the Elastic Load Balancer communicating with a custom port on your EC2 instance(s) directly. In this post, I show how to achieve that.

The first step is to let my Spring Boot application listen for port 8888 instead of 5000. To do this, simply change the following line in the ‘application.yml’ file:

  port: 8888

When we now deploy the application with the Elastic Beanstalk, it won’t work anymore and we will see the 502 Bad Gateway again.

To modify the ports of the Elastic Load Balancer (and the corresponding Security Groups), I add the folder ‘.ebextensions’ to my Spring Boot project. In this folder, I put configuration files that will be used by the Elastic Beanstalk to configure the resources it creates. Because I deploy my application as a jar file and use Maven to create it, I add the folder to the ‘src/main/resources’ folder so it ends up in the root of the jar file.

The first file I add is the one to configure the security group:

    Type: AWS::EC2::SecurityGroupIngress
      GroupId: {"Fn::GetAtt" : ["AWSEBSecurityGroup", "GroupId"]}
      IpProtocol: tcp
      ToPort: 8888
      FromPort: 8888
      SourceSecurityGroupName: {"Fn::GetAtt" : ["AWSEBLoadBalancer" , "SourceSecurityGroup.GroupName"]}

As you can see, I add the inbound port 8888 to the ‘default’ security group with the allowed source of the traffic being the Elastic Load Balancer. That way, port 8888 is only available from the Elastic Load Balancer. The next file will configure the Elastic Load Balancer so it forwards the incoming traffic on port 80 to 8888 on our EC2 instance:

    Type: "AWS::ElasticLoadBalancing::LoadBalancer"
        - {LoadBalancerPort: 80, InstanceProtocol: "TCP", InstancePort: 8888, Protocol: "TCP"}
        HealthyThreshold: "3"
        Interval: "30"
        Target: "HTTP:8888/hello"
        Timeout: "5"
        UnhealthyThreshold: "5"

As you can see also the HealthCheck is modified since our EC2 instance now listens to port 8888. After adding these files my resources folder looks like this:

Screenshot at Jul 12 20-08-12
When we rebuild the application and perform the ‘eb create’ with these settings it will create the Elastic Beanstalk with the following security group:

Image title

 And the Elastic Load Balancer contains the following listener:

Image title

 So with this configuration our Elastic Load Balancer is directly talking with our EC2 instance(s) and bypassing the Nginx running at port 80.

The Cloud Zone is brought to you in partnership with Internap. Read Bare-Metal Cloud 101 to learn about bare-metal cloud and how it has emerged as a way to complement virtualized services.

elastic load balancer,elastic beanstalk

Published at DZone with permission of Pascal Alma, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}