Learn how to set up AWS Load Balancer Redirects HTTP To HTTPS. Our AWS Support team is here to help you with your questions and concerns.

AWS Load Balancer Redirects HTTP To HTTPS | Set Up Guide

Did you know that we can use the Application Load Balancer to redirect HTTP requests to HTTPS?

Our experts have put together this handy guide to help us out. The process involves these four:

1. First, we have to confirm the version of the Load Balancer.
2. Then, we must create an HTTP listener rule that redirects HTTP requests to HTTPS.
3. Next, we have to create an HTTPS listener.
4. Finally, verify that the security group of the Application Load Balancer allows traffic on 443.

Now let’s take a closer look at each of these steps.

Confirming The Load Balancer Version

1. First, we have to launch the terminal for Amazon Elastic Compute Cloud (Amazon EC2).
2. Then, we must select Load Balancers from the sidebar’s Load Balancing section.
3. After that. we must locate the load balancer for which a listener rule is being created. This is done by heading to the Type column, and checking if the version is stated as application, classic, network, or gateway.

The instructions that follow only apply to Application Load Balancer. According to our experts, we have to build a target group before moving on to the next section.

Creating An HTTP Listener Rule That Redirects HTTP Requests To HTTPS

1. First, we have to launch the Amazon EC2 console.
2. Then, select Load Balancers from the sidebar’s Load Balancing section.
3. Next, choose a load balancer and click Add Listener under Listeners.
4. After that, we must select HTTP for Protocol: port. Either the default port will be used, or a custom port can be specified.
5. Then, select Add action, redirect to, and then type port 443 for Default actions. Select the checkmark icon to save. Note: If you followed steps 3-5 above to establish a new HTTP listener, skip to Create an HTTPS listener.
6. At this point, choose HTTP Listener after choosing a load balancer.
7. Now, select View/edit rules under Rules.
8. Then, we can change the default rule that forces all HTTP queries to go to HTTPS, by selecting Edit Rule.
9. Here, we have to delete the current condition under “Then”. Afterward, include the Redirect to action with the updated condition.
10. Next, we have to enter port 443 for HTTPS.
11. We can leave the remaining choices, leave them as is.
12. Select the checkmark icon to save.

Creating The HTTPS Listener

1. Now, choose Listeners, Add Listener.
2. Then, select HTTPS for Protocol: port. Keep using the default port or enter a different one.
3. For Default actions, choose Add action, Forward to.
4. Select a target group that hosts application instances.
5. Choose a pre-configured security strategy that fits the configuration the best.
6. Choose Default Security Certificate.
7. Select Save.

Verifying That The Security Group Of The Application Load Balancer Allows Traffic On 443

1. Choose the description of the load balancer.
2. Select Security group ID under Security.
3. Look over the inbound rules. The security group has to have an inbound rule that allows HTTP and HTTPS traffic.

We can follow these instructions to add inbound rules if there aren’t any already. To add inbound rules

1. To change the security group, select Actions and then Edit Inbound Rules.
2. Select Add rule.
3. Select HTTPS as the Type.
4. Select Custom (0.0.0.0/0 or Source CIDR) for Source.
5. Select Save.

[Looking for a solution to another query? We are just a click away.]

Conclusion

In conclusion, our Support team has provided the steps to use AWS Load Balancer that redirects HTTP to HTTPS.