Protecting Virtual Machines from a vCenter Server : Protecting Virtual Machines on a vCenter Server to AWS
  
Protecting Virtual Machines on a vCenter Server to AWS
 
You can protect virtual machines to Amazon Web Services (AWS). The procedure is the same whether you intend to protect one virtual machine or multiple virtual machines.
The data for virtual machines in the VPG that is to be replicated is stored in AWS S3. The virtual machines in the VPG are recovered in AWS EC2.
Only virtual machines that are supported by AWS can be protected by Zerto Virtual Replication. Refer to AWS documentation for the supported operating systems.
A VPC must exist, and a security group and subnet must be assigned to it and to all other VPCs you want to use for recovered virtual machines.
For Linux, AWS supports virtual machines with up to 12 volumes, including the boot disk.
For Windows, AWS supports virtual machines with up to 22 volumes, including the boot disk.
GBT formatted disks are supported for data volumes only.
The following table describes the limitations per Import Method:
 
Import Method
OS
AWS Import
zImport for Data Volumes
zImport for all volumes
Boot Volume
Additional Volume
Boot Volume
Additional Volume
Boot Volumes
Additional Volumes
Linux
1 TB
1 TB
1 TB
16 TB
2047 GiB*
16 TB
Windows
1 TB
1 TB
1 TB
16 TB
2047 GiB*
16 TB
* Some VMs use the MBR partitioning scheme, which only supports up to 2047 GiB boot volumes. If your instance does not boot with a boot volume that is 2 TB or larger,, the VM you are using may be limited to a 2047 GiB boot volume.
See the relevant AWS documentation for more information: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html
It is strongly recommended to perform a Failover Test to ensure that the recovered instance is successfully running on AWS.