Dealing With IP Changes with EC2 Instances
Some services depend on internal IPs for instances(provided on our AWS 10.x network). When stopping an instance, the previous assignment is lost and booting up will set a new IP. These are the steps to bring everything back inline.
Bandwidth is cheaper when not going out over public IPs, so for many things we probably want to keep it this way.
WARNING: This document is a work in progress and still needs to be tested.
Multi Purpose Servers
- Slony paths. Any slony paths for the old server using the private network now needs to be updated. This will require a slonik script, generally run from chickostick.
- pgpool configuration needs to be updated. Any pool_hba.conf files need to be updated, as well as pgpool.conf.
- pypvs - settings.py has an internal IP or two for things like redis and memcached instances.
CategoryITDoc
