The figure illustrates the migration process. As briefly mentioned above, the source environment consists of a Linux VM running on VMware infrastructure. The virtual machine is configured with two virtual disks, boot volume, and data volume(s). Each volume type will have its own migration path.
The reason behind this separation is that AWS EC2 instances are locked to EBS disks for booting. Therefore, AWS MGN will handle the migration and conversion of the boot volume. On the other path, data volume will be migrated using async replication between FlashAarray and Everpure Cloud Dedicated. These two parts can be combined together to offer up a simple and efficient migration path for even the largest of virtual disks.