AWS migrations Linux VMs -Enable Secure Shell (SSH) for remote access. -Make sure that your host firewall (such as iptables) allows access to SSH. Otherwise, you will not be able to access your instance after the migration is complete. -Make sure that your Linux VM uses GRUB (GRUB legacy) or GRUB 2 as its bootloader. -Make sure that the root volume of your Linux VM uses one of the following file systems: -EXT2 -EXT3 -EXT4 -Btrfs -JFS -XFS Programmatic Modifications to VMs -When importing a VM, AWS modifies the file system to make the imported VM accessible to the customer. The following actions may occur: -[Linux] Installing Citrix PV drivers either directly in OS or modify initrd/initramfs to contain them. -[Linux] Modifying network scripts to replace static IPs with dynamic IPs. -[Linux] Modifying /etc/fstab, commenting out invalid entries and replacing device names with UUIDs. If no matching UUID can be found for a device, the nofail option is added to the device description. You will need to correct the device naming and remove nofail after import. As a best practice when preparing your VMs for import, we recommend that you specify your VM disk devices by UUID rather than device name. Entries in /etc/fstab that contain non-standard file system types (cifs, smbfs, vboxsf, sshfs, etc.) will be disabled. -[Linux] Modifying grub bootloader settings such as the default entry and timeout. When writing a modified file, AWS retains the original file at the same location under a new name. License types Auto (default) Detects the source-system operating system (OS) and applies the appropriate license to the migrated virtual machine (VM). AWS Replaces the source-system license with an AWS license, if appropriate, on the migrated VM. BYOL Retains the source-system license, if appropriate, on the migrated VM. aws sms create-replication-job --license-type Linux operating systems support only BYOL licenses. Choosing Auto (the default) means that AWS SMS uses a BYOL license. Migrated Red Hat Enterprise Linux (RHEL) VMs must use Cloud Access (BYOL) licenses. For more information, see Red Hat Cloud Access on the Red Hat website. Migrated SUSE Linux Enterprise Server VMs must use SUSE Public Cloud Program (BYOS) licenses. For more information, see SUSE Public Cloud Program—Bring Your Own Subscription. Limitations When migrating VMs managed by Hyper-V/SCVMM, SMS supports only Generation 1 VMs (using either VHD or VHDX disk format). AWS SMS does not support VMs on Hyper-V running any version of RHEL 5 if backed by a VHDX disk. We recommend converting disks in this format to VHD for migration. A VM's boot volume must use Master Boot Record (MBR) partitions and cannot exceed 2 TiB (uncompressed) due to MBR limitations. Additional non-bootable volumes may use GUID Partition Table (GPT) partitioning but cannot be bigger than 4 TiB. An imported VM may fail to boot if the root partition is not on the same virtual hard drive as the MBR. An SMS replication job will fail for VMs with more than 22 volumes attached. AMIs with volumes using EBS encryption are not supported. On VMware, AWS SMS does not support VMs that use Raw Device Mapping (RDM). Only VMDK disk images are supported. A migrated VM may fail to boot if the root partition is not on the same virtual hard disk as the MBR. AWS SMS creates AMIs that use Hardware Virtual Machine (HVM) virtualization. It can't create AMIs that use Paravirtual (PV) virtualization. Linux PVHVM drivers are supported within migrated VMs. Migrated Linux VMs must use 64-bit images. Migrating 32-bit Linux images is not supported. Migrated Linux VMs should use default kernels for best results. VMs that use custom Linux kernels might not migrate successfully. When preparing Amazon EC2 Linux VMs for migration, make sure that at least 250 MiB of disk space is available on the root volume for installing drivers and other software. For Microsoft Windows VMs, configure a fixed pagefile size and ensure that at least 6 GiB of free space is available on the root volume. Multiple network interfaces are not currently supported. After migration, your VM will have a single virtual network interface that uses DHCP to assign addresses. Your instance receives a private IP address. A VM migrated into a VPC does not receive a public IP address, regardless of the auto-assign public IP setting for the subnet. Instead, you can allocate an Elastic IP address to your account and associate it with your instance. Internet Protocol version 6 (IPv6) IP addresses are not supported. VMs that are created as the result of a P2V conversion are not supported. A P2V conversion occurs when a disk image is created by performing a Linux or Windows installation process on a physical machine and then importing a copy of that Linux or Windows installation to a VM. AWS SMS does not install the single root I/O virtualization (SR-IOV) drivers except with imports of Microsoft Windows Server 2012 R2 VMs. These drivers are not required unless you plan to use enhanced networking, which provides higher performance (packets per second), lower latency, and lower jitter. For Microsoft Windows Server 2012 R2 VMs, SR-IOV drivers are automatically installed as a part of the migration process. AWS SMS does not currently support VMware SEsparse delta-file format. Because independent disks are unaffected by snapshots, AWS SMS does not support interval replication for VMDKs in independent mode. Windows language packs that use UTF-16 (or non-ASCII) characters are not supported for import. We recommend using the English language pack when importing Windows Server 2003, Windows Server 2008, and Windows Server 2012 R1 VMs. AWS SMS does not support VMs that have a mix of VHD and VHDX disk files.