Reputation: 131
In Classic Load Balancer(CLB) and Application Load Balancer(ALB) there is option to redirect all http traffic to https listener.
I do not find the option to redirect tcp port 80 traffic to tls port 443 from NLB (Network Load Balancer)
Any help is much appreciated.
Upvotes: 12
Views: 22527
Reputation: 427
As of now at least there is a way to manage that with an network loadbalancer and an application load balancer. This is what I did You can have to listeners in the each load balancer.
That worked for me
Upvotes: 0
Reputation: 1
If you use a Network Load Balancer and your HTTP (Port 80 Generally) requests also configured for NLB, Add this code in your last line of .htaccess file:
RewriteCond %{HTTPS} off RewriteRule ^(.*)$
https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Upvotes: -1
Reputation: 81
As of September 2021 this is now possible by creating an Application Load Balancer-type Target Group.
AWS documentation on Application Load Balancer-type Target Groups:
https://docs.aws.amazon.com/elasticloadbalancing/latest/network/application-load-balancer-target.html
Upvotes: 8
Reputation: 3638
AWS Network Load Balancer cannot handle layer 7 thus cannot redirect HTTP to HTTPS by itself.
Workaround I did is:
In this way, the network load balancer can still terminate TLS. And if HTTP requests come to the LB, it will forward to port 8080 and the app/web server will redirect it to your https site.
Upvotes: 8
Reputation: 59946
No, You can not redirect to HTTP/HTTPS as Network LB does not have application layer.
HTTP and HTTPS traffic can be routed to your environment over TCP. To establish secure HTTPS connections between web clients and your environment, install a self-signed certificate on the environment's instances, and configure the instances to listen on the appropriate port (typically 443) and terminate HTTPS connections.
Upvotes: 4
Reputation: 35188
This is not a feature of Network Load Balancers, the feature you're talking about is a layer 7 feature.
Network Load Balancers operate at layer 4, to reproduce this functionality your application would need to implement this instead.
If your application is a public web based application you could get around this by adding a CloudFront distribution in front that can perform HTTP to HTTPS redirect, or migrate to an application load balancer (as you mentioned).
Upvotes: 2