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

I have gotten WIAB to properly run on my localmachine, but am a bit confused on the process for setting it up to work with AWS EC2. Currently the is running without any problems, however I don't believe I have it configured properly. Should wave_server_domain, http_frontend_public_address, http_frontend_addresses all be hooked up to my elastic IP, or is it something else?

share|improve this question

You don't really need Elastic IP, you can use the public DNS instead. To get some info on the settings setup - please read the server.config.example property file. Basically it goes like this: wave_server_domain - can by anything you like, usually the same as your domain ( http_frontend_public_address - this is the public address your WIAB server can be reached, for example: You can use your public DNS or Elastic IP instead of the domain name "" http_frontend_addresses - the comma separated list of addresses the WIAB server ninds itself to. Usually your local IP address that you can get from "ifconfig", or from the properties of the instance as shown in the console.

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.