3 Answers
- Newest
- Most votes
- Most comments
0
Did you configure your target groups corectly? https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html
answered 2 years ago
0
Hello,
Please check at https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-nlb.html I would suggest you to choose Application Load Balancer instead of Network Load Balancer, Network load balancer is ideal for transport layer (layer 4) TCP listeners.
Note
Unlike a Classic Load Balancer or an Application Load Balancer, a Network Load Balancer can't have application layer (layer 7) HTTP or HTTPS listeners. It only supports transport layer (layer 4) TCP listeners. 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. The configuration varies per platform. See Configuring your application to terminate HTTPS connections at the instance for instructions. Then configure your Network Load Balancer to add a listener that maps to a process listening on the appropriate port.
answered 2 years ago
0
Yes, Application load balancers is recommended for Layer 7 (HTTP) end points.
Network load balancers is more for (Layer 4) protocols which forward TCP & UDP traffic to your instances.
answered 2 years ago
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- How do I determine the active SSL security policy associated with my ELB listener using the AWS CLI?AWS OFFICIALUpdated 2 years ago
- I host a website on an EC2 instance. How do I allow my users to connect on HTTP (80) or HTTPS (443)?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
I need to use NLB for my usecase. I tried removing the TLS listener for port 443 and added a regular TCP listener for both port 80 and 443 but it still doesn't work.