Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

When setting up haproxy, you obviously have to set which web servers you want to participate in the round robin etc.

With ec2, I understand you get an internal i.p address that is randomly assigned, and you can also attach an public i.p address if you want.

If I use the internal i.p address, and for whatever reason I reboot my instance I believe I might get another internal i.p address.

What options do I have to get around this issue?

share|improve this question
Why not use the AWS load balancers? It would be a LOT easier than any possible solutions I can see – Smudge May 16 '11 at 0:55

The internal IP should never change.

If you are worried about that you can use amazon's VPC to define your own internal subnet and which server's get what IPs on that subnet.

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.