For AWS Community Builders Click here for details.
Setting up your account
Adding your cloud accounts
Planning your migration
Migration Overview
Migrating From IBM Classic Cloud to IBM cloud VPC
Editing Your Migration Workspace
Creating a VPC From Scratch
Using Templates to Create Your VPC
Ongoing Management
Managing and Editing your VPC
Connecting Your New and Old Environments
Transit Gateways
Overview
VPC+ DRaaS
Getting Started
Supported Migration Use Cases
Setting up Migrators
Setup Migrators for Content Migration
Migration Process
Database Migration
Migration Completion
Completing the Migration Process
Getting Started with VPC+ DRaaS
Learn More About DRaaS
About VPC+ DRaaS
Introduction
Prerequisites for VPC+ DRaas
IBM Cloud Virtual Private Cloud and IKS & OpenShift Clusters
Disaster Recovery
Taking a backup of your VPCs
Restore your IKS Clusters
Restoring IKS Cluster Backups
IBM Power VS
Overview
The information you need to start your migration process will depend on your source and destination cloud environments but will generally consist of the following:
You can get a detailed overview of gathering the information you need for IBM Cloud classic to IBM Cloud VPC at the IBM Cloud docs page here.
| Account information | Details |
|---|---|
| 1. IBM Cloud Username | You will need your IBM Cloud username to add your cloud account. |
| 2. API keys | A classic infrastructure API key and an IBM Cloud API key (VPC API key). Your IBM Cloud API key (VPC API key) must have “Reader, Writer” access. You can verify the level of access in IBM Cloud console by clicking Manage > Access (IAM) and selecting Authorizations. |
| 3. IBM Cloud Object Storage and resource instance ID (service credentials) | Your Object Storage bucket is used to store your images and volumes during the migration process and its resource instance ID allows VPC+ by Wanclouds to access your IBM Cloud Object Storage and import the images that you want to migrate. For more information, see IBM Cloud Object Storage getting started tutorial and Service credentials. |
| 4. (Optional) VRA (Vyatta 5600) configuration file | If you want to migrate your Access Control Lists, VPN gateways, and public gateways, you need a VRA configuration file. Use a .txt file format. JSON format is not supported. |