AWS Elastic Load Balancers support the load balancing of applications using HTTP, HTTPS, protocols. In a previous guide we demonstrated how to configure an ELB listener.

In this guide we will show you how to edit or delete an existing listener from an AWS Elastic Load Balancer. We will show how to configure ELB to listen on HTTP and to redirect requests to the EC2 instances listening on HTTPS. To demonstrate that we created an ELB with the name “AWSHttpsELB”, currently configured to listen on HTTP and HTTPS.

1. Click on the tab “Listener”. The ELB is currently configured to listen on HTTP and HTTPS protocols.

2. To modify the current Cipher settings, click on “Change” under “Cipher”.

[Newvem analyzes your baseline disaster recovery (DR) status, reflecting how well AWS DR best practices have been implemented, and recommends AWS features and best practices to reach optimal availability, increase outage protection, and quick recovery. Learn More about Newvem's features]

3. An ELB provides sample cipher policies, ELBSample-ELBDefaultCipherPolicy and ELBSample-OpenSSLDefaultCipherPolicy. You can select one of the sample policies or customize your own ciphers. A default policy will be used if none is specified. Select either a sample policy or a custom policy as shown below and click “Save”.

4. Like mentioned, we previously configured the ELB to listen on HTTPS port and redirect requests to the EC2 instances on HTTP. Here we configure the ELB to listen on HTTP protocol and forward requests to instances on HTTPS.

Modify the existing HTTP protocol as shown below -

5. The ELB is now listening on HTTP while the instances are listening on HTTPS protocol. The above configuration does not require a CA authorized certificate for ELB, instead you have to configure your EC2 instance to listen to HTTPS by providing a private / public SSL certificate.

6. If you want to test the above setup, test one of the instances with HTTPS protocol. As shown below. You can call the instance entering with https://<public DNS>/ .

7. Access the instance trough the ELB by calling the “A-record” of the ELB as shown below -

8. As shown above, the instance is listening on HTTPS protocol while the ELB on HTTP. All requests are sent to the ELB on HTTP and are redirected by the ELB on HTTPS protocol to the instances.

Delete an Existing Listener from an Elastic Load Balancer

> Using the AWS UI Console

9. To remove the existing listener, follow the steps below -

10. Go to the tab “Listeners” and click “Remove” under “Actions”.

11. The listener will be removed immediately.

> Using the AWS CLI

12. If you want to remove the listener using command line tools, follow the steps below.

13. First set the CLI.

14. Set the AWS Region with the following command:

Set AWS_ELB_URL=https://elasticloadbalancing.us-west-2.amazonaws.com

15. Run the command below to remove the listener.

elb-delete-lb-listeners AWSHttpsELB --lb-ports 80

16. The above command will remove the ELB listener configured to receive requests on port 80 of the ELB.

17. The actual output of each command is shown below.

[Newvem analytics tracks you AWS cloud utilization:

• Hourly Utilization Pattern Analysis 
• Reserved Instances Decision Tool 
• Resource Resizing Opportunities

Create Your Free Account or Learn More about Newvem]

Keywords: Amazon web services, Amazon AWS console, AWS S3, Amazon Cloud Services, AWS Management Console, AWS ELB, Elastic Load Balancer, CLI, Command Line Tools, AWS API, AWS UI Console, Secure data traffic, HTTP, HTTPS, SSL Certificate, AWS Instances, ELB Listener COnfiguration