1 Answers
0
Accepted Answer
Server 2 will see the connection initiated from one of the NLB private IP address. If you need the IP addresses of the service consumers (server1) and their corresponding interface endpoint IDs, enable Proxy Protocol on your NLB and get the client IP addresses from the Proxy Protocol header.
Relevant questions
NLB Preserving Client IP
Accepted Answerasked 2 years agoNLB Distribution unevenly with wildfly and pgBouncer
asked 5 months agoAccessing a RDS database in another account using AWS PrivateLink
Accepted Answerasked 4 years agoRestricting incoming NLB traffic to internal IP addresses
Accepted Answerasked 2 years agoUsing PrivateLink NLB to ALB Port Redirection
asked 6 months agoSource IP using PrivateLink and NLB
Accepted AnswerStatic IP for NLB endpoint
Accepted Answerasked a year agoDoes the IP address created for PrivateLink Interface Endpoint can change?
Accepted Answerasked 4 years agoObtain client IP address through a network load balancer (TCP socket server, Python)
asked a month agoNetwork load balancer and privatelink for static ip
Accepted Answerasked 3 years ago
This link seems to be out of date. This one contains details on how to enable Proxy Protocol
I am facing a similar issue. I have enabled Proxy Protocol on my Network Load Balancer and my ingress understands Proxy Protocol. However, the IP Address seen is only a local address from within the VPC. How do I get the client's IP Address?