Provisioning cloud resources when migrating from Amazon Web Services
This article describes how to provision your Rackspace Cloud services when migrating from Amazon Web Services (AWS). For the purposes of this article, it is assumed that you are familiar with the equivalent services between AWS and Rackspace Cloud and that you are generally familiar with the .
Perform the following procedures to provision and configure your cloud instances:
- Provision a cloud server
- Create a customer password (optional)
- Add Cloud Block Storage (optional)
- Create a Cloud Files container (optional)
- Create a Cloud Database instance (optional)
- Connect to the cloud server
- Migrate your data
Provision a new cloud server
Log in to the Rackspace Cloud Control Panel
On the Cloud Servers page, click Create Server.
Name the server and select a region for it.
Select an OS that matches your OS from AWS.
Note: If your Amazon Elastic Compute Cloud (EC2) instance is Amazon Linux, select CentOS 5.0 or later. Amazon Linux is based on Red Hat Enterprise Linux 5.
Select the size (flavor) that matches your EC2 instance (RAM and disk space), and click Create Server. For information about instance size mapping, see Mapping of Amazon Web Services resources to Rackspace resources.
Note: You can add more storage to your cloud server after it is created by adding a Cloud Block Storage volume. For instructions, see Add Cloud Block Storage (below).
- When your root admin password is displayed, copy the password to a secure location, and then click Dismiss Password.
It is important that you copy and save your root admin password for future reference. You need this password to log in to your server. After you click Dismiss Password, the password will not be displayed again.
Create a custom password (optional)
You can create a custom password for you sever.
- On the Cloud Servers page in the Cloud Control Panel, click the gear icon next to the server in the server list and select Change Password.
- Enter a new password and click Change Password.
Add a Cloud Block Storage (optional)
If you had additional Amazon Elastic Book Store (EBS) volumes attached to your server, or if you prefer to have more storage space for your server, add additional Cloud Block Storage volumes as follows:
- In the Cloud Control Panel, open the server's detail page.
- In the Storage Volumes section, click Create Volume.
- Name the volume, select its type (SATA or SSD), and select the size.
Click Create Volume.
Create a Cloud Files container (optional)
If you plan to use a Cloud Files container for the application, to back up files, or to assist with your application migration, create your container now.
At the top of the Cloud Control Panel window, click Storage.
In the popup menu, under Object Storage and CDN, select Files.
On the Cloud Files/Containers page, click Create Container.
Name the container, assign it to the same region as the server that you created, and select the container type.
Click Create Container.
Create a Cloud Databases instance (optional)
If you will not be setting up your own database server, create a Cloud Databases instance.
At the top of the Cloud Control Panel window, click Databases.
In the popup menu, select Database Instances.
3.On the Cloud Databases page, click Create Instance.
Name the instance and assign it to the same region as your server.
Select the type of database instance (datastore), and specify its size (in RAM and disk space).
(Optional) Add your first database by assigning it a name, user name, and password. Note:You cannot name your user as root.
Click Create Instance.
Connect to the Cloud Server
On the Cloud Servers page in the Control Panel, click the name of your server.
Under Networks, note the PublicNet (Internet) IPv4 address.
Using SSH, connect to your cloud server by using the following command and the PublicNet address:
If you're connecting from a Windows computer, use PuTTY or a similar SSH command to connect to your server's IP address.
Enter your root password to log on.
Migrate your data
After your Rackspace Cloud services are provisioned, you can build your applications and transfer your data from AWS. The following articles provide detailed descriptions of migration scenarios:
Applications built on a LAMP stack - Migrating an Application Built on a LAMP Stack from Amazon Web Services
.NET applications - Migrating a .NET application from Amazon Web Services
Java web applications Migrating a Java Web Application from Amazon Web Services
Node.js applications - Migrating an Application Based on Backbone.js, Node.js, and MongoDB from Amazon Web Services
Carry on the conversation in the Rackspace Community.
© 2015 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER