CloudEndure allows the replication of any Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine., whether physical, virtual or cloud-based into the AWS cloud for a large variety of operating systems.
Note: It is recommended to install all available Windows Updates on the machine.
Note: Windows Source machines need to have at least 2 GB of free space in order to launch a Target machine successfully.
Note: CloudEndure does not support Windows disks that have GPT partitions and are dynamic as boot disks for BIOS machines. Learn more here.
Note: CloudEndure does not support OS-based disk encryption features such as BitLocker. These should be disabled before using any CloudEndure services.
Note: Ensure that you have Python installed on the machine (version 2.4+, version 3.0+) for Agent installation.
Note: Only machines using the GRUB bootloader are supported.
Note: Kernel versions earlier than 2.6.18-164 are not supported by AWS and CloudEndure. Therefore, machines that run these kernel versions cannot be replicated by CloudEndure.
Note: Secure Boot is not supported in Linux.
Note: Boot disks that span multiple physical disks are not supported.
Note: CloudEndure does not support Paravirtualized Source machines.
Note: CloudEndure does not currently support replicating EC2 instances that utilize the EBS volume multi-attach feature.
Note: CloudEndure only supports x86-based operating systems.
Operating System | AWS Support |
Windows | |
Microsoft Windows Server 2003 32 bit | *See Note 6 below. |
Microsoft Windows Server 2003 64 bit | *See Note 6 below. |
Microsoft Windows Server 2003 R2 32 bit | *See Note 6 below. |
Microsoft Windows Server 2003 R2 64 bit | *See Note 6 below. |
Microsoft Windows Server 2008 32 bit | *See Note 6 below. |
Microsoft Windows Server 2008 64 bit | *See Note 6 below. |
Microsoft Windows Server 2008 R2 64 bit |
*See Note 3 below. *See Note 5 below. |
Microsoft Windows Server 2012 64 bit | *See Note 6 below. |
Microsoft Windows Server 2012 R2 64 bit |
*See Note 3 below. *See Note 5 below. |
Microsoft Windows Server 2016 64 bit | |
Microsoft Windows Server 2019 64 bit |
*See Note 3 below. *See Note 5 below. *See Note 9 below. |
Microsoft Windows XP |
*Only supported when replicating to dedicated hosts and instances. *See Note 8 below. |
Microsoft Windows 7 |
*Only supported when replicating to dedicated hosts and instances. *See Note 8 below. |
Microsoft Windows 8 |
*Only supported when replicating to dedicated hosts and instances. *Only 64-bit is supported. *See Note 8 below. |
Microsoft Windows 10 |
*Only supported when replicating to dedicated hosts and instances. *Only 64-bit is supported. *See Note 8 below. |
Microsoft Windows Vista |
*Only supported when replicating to dedicated hosts and instances. *See Note 8 below. |
Linux | |
SUSE Linux (SLES) 11 and higher. | *SP4 or higher. |
Debian Linux 8 and higher |
*See Note 3 below. |
Kali Linux 2.0 and higher | |
Ubuntu 12.04 and higher | *See Note 2 below. |
Red Hat Enterprise Linux (RHEL) 5.0 and higher |
*See Note 1 below. |
Oracle Linux 6.0 and higher | *Oracle Linux 6.0+ running Unbreakable Enterprise Kernel Release 3 or higher or Red Hat Compatible Kernel only |
CentOS 5.0 and higher |
*See Note 3 below. |
Note 1: According to AWS requirements, machines running Red Hat Enterprise Linux (RHEL) must have Cloud Access (BYOL) licenses to be copied to AWS.
Note 2: Only Kernel 3.x or above are supported for Debian/Ubuntu with AWS.
Note 3: Nitro instances (for example, the C5 and M5 family types) will work with RHEL 7.0+ and CentOS 7.0+ in AWS in a Linux environment and with Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019 in a Windows environment. Certain newer AWS regions only support Nitro instances and therefore only support the previously mentioned operating systems.
Note 4: Kernel versions 2.6.32-71 is not supported in RHEL 6.0 and CentOS 6.0 in AWS.
Note 5: Microsoft Windows Server versions 2008 R2 and above require .Net Framework version 4.5 or above to be installed.
Note 6: Microsoft Windows Server versions 2008 and below require .Net Framework version 3.5 or above to be installed.
Note 7: A pre-requirement for installing the CloudEndure Agent on RHEL8 and CentOS 8 is first running the following:sudo yum install elfutils-libelf-devel
Note 8:When migrating Windows machines into AWS, you can Bring Your Own (BYOL) Windows License by setting a Dedicated Host in the machine Blueprint. When this is done, the licenses from the Source machine will be automatically transferred to the Target machine in AWS.
For MSDN Windows licenses, you can use the Dedicated Instance option in addition to the Dedicated Host option. Selecting the Dedicated Instance option in the machine Blueprint does not allow Windows BYOL by default. To be able to transfer MSDN Windows licenses over to Dedicated Instances, contact Support.
Note that MSDN subscriptions purchased or renewed after 10/1/2019 are not eligible for deployment on AWS (shared or dedicated).
Note 9: When replicating a Windows 2016+ server from AWS to AWS and not using the same VPC cidr range on the destination, you must schedule EC2Launch to run on every boot so that the Target machine will have connectivity. Learn more here.
Note that the json configuration file also needs to be changed to prevent the admin password from changing every time. This is an expected EC2 Launch behavior that does not have anything to do with CloudEndure. This behavior will repeat itself every time a Windows 2016+ machine is coipied to another VPC using AMI.
©2020 COPYRIGHT CloudEndure - Terms of Service - Privacy Policy - AWS Vulnerability Reporting Guidelines - Report a Security Issue