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 have created a Windows Server 2012 EC2 instance and I have bound an Elastic IP address to the server. The problem is, the IP address isn't showing up in IIS 8 and I can't seem to get web sites to respond if I manually type in the IP address.

How can I get IIS to recognize the IP address and respond on that? I am about to connect to the server via RDP via the elastic ip so I know it is bound to the server.

share|improve this question
up vote 2 down vote accepted

Amazon Elastic IPs are forwarded to the private IP you choose and for the most of it the server doesn't know what it's public IP address is. It's available at metadata if you really need it.

You should bind IIS to the private IP address.

Assuming you have Elastic IP bound to you should setup in IIS the (or just bind to all addresses).

share|improve this answer
Thanks for that! What happens if I want to add multiple SSL certificates and they require a seperate ip address each? – Base33 Dec 17 '13 at 9:53
I haven't used IIS in a while but you have two choices: - One that works is if you only need a few SSL certificates (there is a limit that depends on the instance size at AWS) is to have a private IP address for each of the SSL sites; - The second one, isn't compatible with older browsers/OS, is to use SNI (…). I've never used this at IIS but works well on nginx/apache. – Manuel Sousa Dec 17 '13 at 9:56

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.