8.3 Planning For Migrating Workloads to Amazon Web Services

PlateSpin Migrate allows you to use the PlateSpin Migrate Client to migrate Windows and Linux workloads to AWS. For a list of supported workloads, see Supported Workloads For Migration to Amazon Web Services.

NOTE:Migration of AWS source workloads to AWS target containers is not supported.

Consider the following points before you use the PlateSpin Migrate Client to migrate workloads to AWS:

  • Migration of Windows Cluster workloads is not supported.

  • Windows and Linux UEFI workloads are migrated as BIOS workloads.

  • Use PlateSpin Migrate Client to migrate workloads to AWS. The PlateSpin Migrate Web Interface does not support migration of workloads to AWS.

  • PlateSpin Migrate provides a configuration parameter named AWSActivateWindows on the PlateSpin Configuration page. By default, this parameter is set to True to allow AWS to activate Windows license on a Windows target workload. However, if you want to use your own Microsoft license for which you are responsible for complying with Microsoft licensing, then set this parameter to False. For more information about the AWSActivateWindows and its related parameters, see Section 5.7, Configuring Alternate IP Addresses for PlateSpin Server.

  • PlateSpin Migrate supports AWS target instances with up to 26 volumes (EBS volumes) for Windows and 40 volumes (EBS volumes) for Linux with each disk not exceeding 15 volumes.

  • Migrate recommends an AWS instance size that meets or exceeds the source workload's settings for cores, memory, volumes, and NICs. However, you can choose a smaller or larger instance size based on your requirements for the target workload, as limited by the maximum instance sizes available in the AWS region.

  • The size of the disk created on the AWS instance is the size of the source disk partition plus about 1 GB.