[+]
Updated on 10/31/2016
CloudEndure installation on Windows (AWS)
Before installation
  • CloudEndure was tested on:
    • Microsoft Windows Server 2003 32 and 64 bit
    • Microsoft Windows Server 2008 32 and 64 bit
    • Microsoft Windows Server 2008 R2 32 and 64 bit
    • Microsoft Windows Server 2012 32 and 64 bit
    • Microsoft Windows Server 2012 R2 32 and 64 bit 
  • In order for AWS to run your machine, .Net Framework version 3.5 or above needs to be installed.
  • It is recommended that all available Windows Updates should be installed on the machine. This solves many incompatibilities that Windows distributions used to have with AWS.
  • Note that the time between installation of Windows Updates that require a reboot and the reboot that they require are considered by Microsoft not to be crash-consistent, so please do not create a replica at that state.
  • Make sure that outgoing traffic from the machine to ports 1500 and 443 is enabled at all times. Port 443 is needed to download the agent and for agent upgrades and for communication with the centralized management. Port 1500 is needed for the replication traffic itself.
  • CloudEndure replicates whole volumes. In case you choose to replicate a partition, its entire volume will be replicated.
  • When replicating machine from on-premise, CloudEndure currently only attaches at most one private IP address to the replica instance. Additional IP addresses can be allocated and attached using AWS API, CLI or console. 

  • Make sure that you have an account with CloudEndure, that this account has been activated and you have entered your AWS Access Key Id and Secret Access Key in the AWS credentials tab of the Account page.
  • If you are installing the agent on a non-AWS machine, before installing an agent, make sure that your CloudEndure console Replication Settings tab in the Account page has “Source” set to Generic and “Target” is set to your desired target AWS region.
  • If you are installing the agent on an AWS machine, please make sure you have the latest paravirtualized drivers installed, as described here.
  • Make sure that the AWS account you associated with your CloudEndure account is compliant with the following IAM policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": "ec2:*",
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "elasticloadbalancing:*",
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "cloudwatch:*",
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "autoscaling:*",
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "iam:GetUser",
            "Resource": "*"
        },
        {
            "Effect":"Allow",
            "Action":"iam:PassRole",
            "Resource":"*"
        },
        {
            "Effect":"Allow",
            "Action":"iam:ListInstanceProfiles",
            "Resource":"*"
        },
        {
            "Effect": "Allow",
            "Action": "kms:ListKeys",
            "Resource": "*"
        }
    ]
}