For AWS Community Builders Click here for details.
Setting up your account
Creating your account
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
Before you begin discovering and backing up your IBM Virtual Private Cloud resources, you must have:
Permissions for IBM Cloud classic and VPC.
A classic infrastructure API key and an IBM Cloud API key (VPC API key).
Note: 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.
An IBM Cloud Object Storage (COS) bucket and its Resource Instance ID (service credentials). The COS bucket will be used to store your images and volumes during the migration process and its Resource Instance ID will allow VPC+ to access it.
Before you begin discovering and backing up your IKS and OpenShift clusters, you must have the following permissions:
Make sure that the API key for the region and resource group that you plan to create the VPC Gen 2 cluster in is set up with the correct infrastructure permissions.