Network Load Balancers are Layer 4 load balancers (TCP/UDP) - they do not understand HTTP and are not capable of making routing decisions by paths or any other aspect of the incoming request.
Customers who need solutions to perform Layer 7 load balancing (HTTP) should be advised to use Application Load Balancers. However, the ALB must terminate TLS in order to determine which target group to send requests to based on the payload. It can, of course, re-encrypt the backend requests with TLS in order to provide security in transit.
Putting ALb-NLB-ALB route for requests is giving 502 for applicationasked a month ago
NLB support for TLS passthrough on EKS based on URI pathsAccepted AnswerMODERATORasked 2 years ago
Adding a static IP to ELBasked 3 years ago
AWS EKS Internal Network load balancer (NLB) timed out while trying to connect from underlying eks worker nodeasked 15 days ago
Using a single Elastic IP and routing on FQDN with UDP requestsasked 4 months ago
NLB stops responding on one IPAccepted Answerasked a year ago
Unexpected URI while testing API gateway to NLBasked 5 months ago
TLS 1.3 support for NLBAccepted Answerasked 5 months ago
Certificate signing in EKSAccepted Answerasked a year ago
Load Balancer [NLB] - Listeners - Inconsistentasked 6 months ago