Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to find out the range of IP addresses that an Elastic Load Balancer could have from an EC2 instance which is behind it. This is so I can configure the HttpRealIpModule of nginx correctly.

I've found a list of EC2 public IP addresses but can't find any mention of the private IP range. My best guess is - does anyone know if that is correct?

share|improve this question
I'd imagine you could safely set it to the entire private address space -,, – ceejayoz Nov 16 '11 at 18:54

According to this AWS page, it can be any private IP per RFC1918, which is indeed, or, which is a pain. I whish they would restrict to, say, so that we can have 172.16 for our private app use, such as hosting OpenVPN

share|improve this answer
Just what I was looking for, thanks. Please let me know if this has changed in the 2 years since answering. – SteveEdson Apr 2 '14 at 10:09
You can read the linked page to find out. There doesn't seem to be any change. – Serge Wautier Apr 2 '14 at 11:46

I know the question is fairly old, but as I got here I'm sure somebody could use this: You can set up an VPC and then use the ELB inside the VPC so you can make sure the ELB is always in you private IP range of you VPC (i.e.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.