Azure Blob Storage to Amazon S3 Migration Guide
- This is the complete onboarding task flow for migrating data from Azure Blob Storage to AWS S3 storage.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
Prepare the Source Environment
- Buy an Azure subscription. KB004996
- Create an Azure storage account. Note: You will enter storage account information when you create your MSPComplete Destination endpoint. KB004832
- Obtain Access Key: Log on to Azure portal > Dashboard > All Resources > All subscriptions > Click on Storage Account name > Settings > Access Key. Note: Make a note of the Storage Account Name and the Primary Access key. These will need to be entered when you create your MSPComplete Destination endpoint.
Prepare the Destination Environment
Create an account with AWS S3 read-only access.
- When creating the user account, there is a tab labeled Attach existing policies directly. This contains a policy named AmazonS3ReadOnlyAccess. This is the policy that needs to be attached to this user account. KB005203
- When creating this account, the final page will show the Access Key ID and Secret Access Key. Note: In order for the Secret Assess Key to be displayed, you need to click on Show. Important: Write down the key, or download the key file to your computer before you press "Close" or "Cancel"; otherwise, you will not be able to retrieve the Secret Key in the future. Later, if you cannot retrieve the Secret Key, you will have to delete the Keys you created, and then create new Keys.
- The Access Key ID and the Secret Access Key need to be entered when creating your MSPComplete Destination endpoint.
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter the endpoint name > For endpoint type, select Azure Blob.
- Enter the Storage Account Name and Access Key in the fields provided. Note: These were created and obtained when following the steps in this guide under Prepare the Destination Environment.
- For the Destination endpoint:
- Click on EndPoints > Add Endpoint > Enter the endpoint name > For the endpoint type, select Amazon S3.
- Enter the AWS Access Key ID and AWS Secret Access Key in the fields provided. Note: These were generated and obtained when following the steps in this guide under Prepare the Source Environment.
- Steps to determine how much storage has been used on Azure are documented in a TechNet article here.
- Purchase enough licenses to cover your migration. Each license allows up to 10GB of data per bucket to be migrated. Therefore, if you have two (2) Azure containers, one with 45GB of data, and one with 58GB of data, then you need a total of 11 licenses: 5 licenses for the first container, and 6 licenses for the second.
- Create the Cloud Storage Migration project. KB005070
- Create the Cloud Storage Migration project > Select the customer > Select Source endpoint > Select Destination endpoint. Click the Save button.
- Set the value for maximum licenses to consume per item, per pass. The default value is one license per item, which allows up to 10GB to be migrated. However, If you have Azure containers with more than 10GB of data, then you will need to increase the licensing count to a number that will cover your migration. In the example above (under Purchase licenses), the largest container is 58GB. Therefore, this licensing count should be set to 6, since this is set in increments of 10GB. KB004890
- Important: Leave the Source: Azure Blob bucket name field as migrationwiz and the Destination: AWS S3 bucket name field as MigrationWizArchive. These are the default values.
Decommission the Azure blob storage.