Home > Guides > Dashboard Users Guide > Clouds > AWS Regions > EC2 Elastic IPs > Actions > Transfer an Elastic IP to a running instance

MindTouch
Copyright (c) 2006-2014 MindTouch Inc.
http://mindtouch.com

This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).

At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.

A complete copy of the MSA is available at http://www.mindtouch.com/msa

Transfer an Elastic IP to a running instance

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 -> Deployments ->  DeploymentName).  Click on the Servers tab.  If the "Public IP" column is not displayed, you will need to make it visible by using the "Show/Hide Columns" option.  To change an instance's EIP, click the Edit icon and select an EIP from the list and click the OK icon.

screen-ChangeEIP-RunningServer-v1.png

Change EIPs at the Server Level

If your instance is running, you can associate an EIP at the "Current" Server level. Under the Info tab, select an EIP for the "Current Elastic IP" parameter.

screen-AssociateEIPServerLevelEdit-v1.png


screen-AssociateEIPServerSelect-v1.png

You must to post a comment.
Last Modified
22:14, 16 May 2013

Tags

This page has no custom tags.

Classifications

This page has no classifications.

Announcements

None

Glossary | 用語용어 Site Map | Site Help Community Corporate Site Get Support Dashboard Login
Doc Feedback Product Feedback Resources MultiCloud Marketplace Forums

Dashboard Status


© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.