This article describes provisioning Rackspace Cloud services when migrating from Amazon Web Services (AWS). It assumes you are familiar with the equivalent services between AWS and Rackspace Cloud and that you are generally familiar with the steps involved in a migration.
Before migrating from AWS you should prepare your destination services on Rackspace Cloud.
Provision a new cloud server.
Copy and save the password that is displayed in the Root Admin Password window. You need this password to log on to your server, and the password is not displayed again.
Note: You can also create a custom password by clicking the Actions cog on the server's page, selecting Change Password, and entering your own password.
(Optional) Add Cloud Block Storage if required.
If you want more to add more storage space to your server, or if you had additional Amazon EBS volumes attached, you can add additional Cloud Block Storage volumes as follows:
(Optional) Create a Cloud Files container if required.
If you will use a Cloud Files container for the application, to backup files, or to assist with your application migration, create any needed container or containers now.
(Optional) If you won't be setting up your own database server, create a Cloud Database instance:
Connect to the Cloud Server.
If you're connecting from a Windows machine, use PuTTY or a similar SSH command to connect to your server's IP address.
With your Rackspace Cloud services provisioned, it's time to build our your applications and transfer your data from AWS. We offer detailed descriptions of migration scenarios for applications built on a LAMP stack, .NET applications, Java web applications, and Node.js applications.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License