8.3 Planning for Migrating Workloads to Amazon Web Services

Migration of Windows Cluster workloads is not supported.

Windows and Linux UEFI workloads are migrated as BIOS workloads.

Use PlateSpin Migrate Web Interface to migrate workloads to AWS. The PlateSpin Migrate Client no longer supports migration of workloads to AWS.

PlateSpin Migrate supports AWS target instances with up to 26 disks (EBS volumes) for Windows and 40 disks (EBS volumes) for Linux with each disk not exceeding 15 file system 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 plus about 1 GB.

If an AWS instance has ephemeral disks, then PlateSpin Migrate neither discovers or migrates such ephemeral disks.

Migrate supports AWS instance types based on x86 and x86_64 processor architectures.

AWS requires a minimum of Microsoft .NET Framework 4.5 for migration of Windows workloads to Nitro System based VM instances. To use Nitro System based instances, ensure that .NET 4.5 Framework or later is installed on the source Windows workload prior to Migrate discovery.

Migration of Windows Domain Controller servers to AWS requires Nitro System based instance types such as c5, m5, r5, t3, c5d, m5d, and z1d. Ensure that you select a Nitro System based instance when you configure the migration.