Source IP using PrivateLink and NLB
0
Setup: Server1 (VPC-A) -> PrivateLink (VPC-B)-> NLB (VPC-B) -> Server2 (VPC-B)
The application (server 2) needs to know the source IP of the consumer (server 1). What will be the visible source IP on server2? Is it the private IP of server1 or the NLB if not, then how can we get it?
1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
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.
Relevanter Inhalt
- Wie lösche ich meinen Network Load Balancer, der VPC-Endpunkt-Services (PrivateLink) zugeordnet ist?
AWS OFFICIALAktualisiert vor 2 Jahren - AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
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?