Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > Dashboard Users Guide > Manage > Deployments > Concepts > Benefits of Using Deployments

Benefits of Using Deployments

Define Common Input Parameters

Deployments provide a useful way of managing a common group of instances.  For example, if you set common input parameters at the deployment level, all servers in the deployment will inherit the same parameters unless they are overwritten at the server level.  (Input parameters that are defined at the deployment level will overwrite the values that are defined at the ServerTemplate level.  It's useful to define common input parameters at the deployment level for all servers such as AWS and database credentials.  You cannot define Inputs for the Default deployment.  You can only define deployment-wide inputs for a deployment that you create.

Multiple Deployments

Deployments are especially useful for creating unique or identical work environments.  Remember, deployments are free; you only have to pay for server usage.  Therefore, you might want to use deployments to organize custom server environments (production, staging, testing, backup, marketing, etc.).  Each deployment can have different users with different permission rights.   See Create a Staging Deployment.

Clone Deployments

The ability to instantly clone a deployment with one click is a very simple, but very powerful feature. Now you can create an exact copy of an existing deployment.   For example, clone your "staging" deployment for your quality assurance team so they can perform GUI and regression tests without impacting the developers' environment.  Create a clone of your production-ready deployment as a backup that will be ready to launch in a different availability zone if problems arise.  See Designing Failover Architectures on EC2.  Remember that in the cloud you are not limited by hardware resources and can create working environments that are always available for you on demand.

Lock a Deployment

You should lock a deployment in order to prevent a deployment from being deleted. It also prevents servers from being removed from a deployment, but it does not prevent a user from adding servers or performing actions on any existing servers, such as launching/stopping servers.

Additional Considerations

  • Each Amazon EC2 deployment must use the same AWS Credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY).
You must to post a comment.
Last modified
22:47, 16 May 2013



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.