Transfer an Elastic IP to a running instance

1. 1.1. Things to Consider
2. Instructions
1. 2.1. Change EIPs at the Deployment Level
2. 2.2. Change EIPs at the Instance Level

Once you have a running production deployment, you might run into a scenario where you need to replace one of your load balancers because it's corrupted, outdated, or failed.

There are several places inside the Dashboard where you can easily transfer an Elastic IP to another running instance.

Things to Consider

It will take several minutes for an EIP to transfer to another instance.
When a new instance is assigned an EIP at launch, it will wait for the EIP to settle before trying to handle any traffic. But, if you transfer an EIP to an instance that is already running, it will not wait for the EIP to settle before handling traffic.
HAproxy will maintain any connections to the old server in order to prevent users from dropping their connection. "Sticky sessions" will persist until there are no more connections to the old server or until you manually shut down or terminate the instance.

Instructions

Verify that the instance that you are transferring the EIP to is stable and ready to receive incoming traffic.

Change EIPs at the Deployment Level

If your instance is running, you can associate an EIP at the deployment level. Go to your deployment's home page (Manage -> Servers -> Deployments). Click on the Servers tab. To change an instance's EIP, click the Edit button and select an EIP from the list and click the OK button .