Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > Dashboard Users Guide > Clouds > AWS Regions > EC2 Elastic IPs > Actions > Assign an Elastic IP at Launch

Assign an Elastic IP at Launch

The most common way to use an Elastic IP (EIP) is to assign it to a server when it's launched for the first time.  You can also assign an Elastic IP to a current running instance.  If you select an EIP, but uncheck the "Associate IP at launch" option, the instance will be randomly assigned a Public IP address at launch time; the Elastic IP will not be assigned to the instance.

There are several different ways to configure a server so that a specific Elastic IP will be associated and used by the instance at launch time. 

Add a Server to a Deployment



Modify Inactive Server

You can also change the configuration of a server to associate an EIP at launch time.  You can only apply this setting to an inactive server that has not been launched.  So, if there is a "Current" server that's already running, you'll need to modify the "Next" server.  



WARNING!  You can steal an Elastic IP from a running instance!  Be sure to check and make sure that a running instance is not using the EIP that you want to assign to a new server.


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


This page has no custom tags.


This page has no classifications.



© 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.