The following steps are to be checked or done prior to starting the migration process:
- Deployment of Pure Storage Cloud Dedicated for AWS. Pure Storage Cloud Dedicated can be deployed from the AWS console via AWS Marketplace (See ), or it can be deployed using Terraform ( See Deploy Everpure Cloud Dedicated using Terraform).
- Connectivity established between on-premises FlashArray and Cloud Block Store.
-
Source VM prerequisites:
- Confirm source machine OS is supported by AWS MGN. Check Supported operating systems.
- Verify source machine has at least 2 GB of free disk space on the root directory or boot disk (i.e. c: driver on Windows). also 300 MB of free RAM in order to run the AWS replication agent.
-
VMware prerequisites:
- VM volumes are contained on a vVol datastore or on raw device mapping (RDM) disks and backed by on-premises FlashArray. If VMFS datastores are in use, please convert them to vVols.
- Install Pure Storage vSphere Plugin.
- Verify network communication over TCP ports 443 and 1500 between the source machine and the Staging area subnet. See Appendix B.
-
AWS prerequisites:
- Verify AWS region is supported by AWS MGN. Check Supported AWS regions.
- Create or use an existing Virtual Private Network (VPC).
- Create staging area subnet. This subnet within the Replication and Converter Server will be launched.
- Create launch area subnet(s) and security groups. This subnet and security group where the migrated servers, EC2 instance will be launched.
- Generate or retrieve AWS account credentials, AWS Access key, and secret key. Those will be used during the replication agent installation. Check generating AWS credentials.