Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
AWS re:Postre:Post

Obtain client IP address through a network load balancer (TCP socket server, Python)

0

Hi All,

I run a couple of TCP socket server on EC2, behind a network load balancer (NLB). even I've set the target_group to preserve client IP address. I am not able to obtain the actual client IP address in my Python TCP socket server. All I am getting seems to be a few fixed IP address, likely belong to the load balancer or some edge computing node ?

when I bypass the load balancer, my server app is able to obtain the proper client IP address.

any idea, what I am missing here ?

Argomenti
ComputazionaliNetworking e distribuzione di contenuti
Tag
Edge computingAmazon EC2Networking e distribuzione di contenutiEquilibratore di carico elastico
Lingua
English
rePost-User-7359932
posta 2 anni fa3430 visualizzazioni
2 Risposte
3

More info on this topic:

  • For Network Load Balancers, register your targets by instance ID to capture client IP addresses without additional web server configuration. For instructions, see Target group attributes instead of the following resolutions (refer the link)

  • For Network Load Balancers when you can register only IP addresses as targets, enable proxy protocol version 2 on the load balancer. For instructions, see Enable proxy protocol instead of the following resolutions.

Reference: https://aws.amazon.com/premiumsupport/knowledge-center/elb-capture-client-ip-addresses/

profile pictureAWS
ESPERTO
Tushar_J
con risposta 2 anni fa
profile picture
ESPERTO
Antonio_Lagrotteria
verificato un mese fa
  • sourav
    2 anni fa

    Yes,I've tested, it's working in my setup

  • rePost-User-7359932
    2 anni fa

    thanks, but this is not relevant to me , I am using Network Loadbalancer

  • Tushar_J ESPERTO
    2 anni fa

    Thanks for the clarification, I modified the answer, the link I provided has information for NLB as well.

  • rePost-User-7359932
    2 anni fa

    thank you.

0

Behaviour depends on the type of ELB - NLB preserves Source IP (except for IP Address targets), whereas servers behind CLB & ALB see load balancer IPs as Source IPs in client requests and rely on x-forwarded-for header to indicate true source.

ESPERTO
skinsman
con risposta 2 anni fa
  • rePost-User-7359932
    2 anni fa

    this is where the confusing part is:

    I am using NLB, and I am seeing a few IP addresses (all my client connection seems all come from these few IP address based on the TCP server log). but reality is I have thousands of client accessing, and they are definitely not from these few IP addresses.

    when I by pass the NLB, I see the correct IP address for the Client

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente