Best REgards,

B.

great article! i cloudn’t resist to try it out with my ec2 account. but at first it didn’t work for me,
i was getting ’502 Bad Gatway’ error which meant that nginx was not able to talk to the router.
so after looking into the log files (bin/vcal tail) i saw that after editing the 4 config files the components were not able to communicate with each other.

the reason is that inside of the ec2 instance the ellastic ip is not reachable (which is the same as the public ip) you have to use the local ip.

the other problem is the domain name (let’s say its api.mydomain.org) is resolved to the ellastic ip (same as the public ip) as well. so you have to enter the local ip in /etc/hosts.

here is the script i was able to get it right:

cd ~/cloudfoundry/vcap/

URI=api.lalyos.info
FILES=”cloud_controller/config/cloud_controller.yml router/config/router.yml health_manager/config/health_manager.yml dea/config/dea.yml”
LOC_IP=$(wget -qO – http://169.254.169.254/latest/meta-data/local-ipv4)

# editing the 4 config files, creating a backup
sed -i.bak “s/api.vcap.me/$URI/;s/127.0.0.1/$LOC_IP/;s/localhost:4222/$LOC_IP:4222/” $FILES

# faking /etc/hosts to be able to ping $URI locally in the ec2 environment
sudo sh -c “echo \”$LOC_IP $URI\” >> /etc/hosts”

# restarting
bin/vcap restart