# Adding source servers to AWS DRS
Add source servers to AWS Elastic Disaster Recovery by installing the AWS Replication Agent (the Agent) on them. The Agent can be installed on both Linux and Windows servers.
[Linux installation instructions](linux-agent.md)
[Windows installation instructions](windows-agent.md)
**Topics**
+ [Installation requirements for AWS Replication Agent](installation-requirements.md)
+ [Windows operating systems supported by Elastic Disaster Recovery](Supported-Operating-Systems-Windows.md)
+ [AWS DRS supported Linux operating systems](Supported-Operating-Systems-Linux.md)
+ [Installing the AWS Replication Agent](agent-installation.md)
+ [Adding instances from the Amazon EC2 Console](adding-servers-from-aws-instances.md)
# Installation requirements for AWS Replication Agent
Before installing the AWS Replication Agent on your source servers, ensure that they meet the following requirements:
**Topics**
+ [General requirements](#general-requirements)
+ [Source server requirements](#general-requirements2)
+ [Linux installation requirements](#linux-requirements)
+ [Windows installation requirements](#windows-requirements)
## General requirements
+ Ensure that the source server operating system is supported by AWS.
+ [Supported Windows operating systems.](Supported-Operating-Systems-Windows.md)
+ [Supported Linux operating systems.](Supported-Operating-Systems-Linux.md)
+ Ensure that your setup meets all replication networking requirements. [Learn more about network requirements.](preparing-environments.md)
+ Ensure MAC address stability – ensure that the MAC addresses of the source servers do not change upon a reboot or any other common changes in your network environment. AWS Elastic Disaster Recovery calculates the unique ID of the source server from the MAC address. When a MAC address changes, AWS Elastic Disaster Recovery is no longer able to correctly identify the source server. Consequently, replication stops. If this happens, you need to reinstall the AWS Replication Agent and start replication from the beginning.
**Note**
Elastic Disaster Recovery Agents can only be installed on instances that are in AWS Regions that are supported by Elastic Disaster Recovery. In case of AWS-AWS disaster recovery (in-AWS), Elastic Disaster Recovery should be initialized in both source and target region (done by going through the initialization wizard).
## Source server requirements
+ Verify that your source server has at least 300 MB of free RAM to run the AWS Replication Agent.
+ AWS Elastic Disaster Recovery only supports 64-bit operating systems built for the x86 system architecture.
+ AWS Elastic Disaster Recovery does not support paravirtualized source servers.
+ The AWS Replication Agent installer supports multipath.
## Linux installation requirements
Ensure that your Linux source server meets the following installation requirements prior to installing the AWS Replication Agent:
+ Python 2 (2.4 or above) or Python 3 (3.0 or above) is installed on the server.
+ Verify that you meet these disk space requirements:
+ At least 4 GB of free disk space on the root directory (/) of your source server for the installation. To check the available disk space on the root directory, run the `df -h /` command.
+ At least 500 MB of free disk space on the */tmp* directory for the duration of the installation process. To check the available disk space on the /tmp directory run the `df -h /tmp` command.
+ If `/boot` is a separate partition, ensure that it has a minimum of 50 MB free space needed for the installation. To check the available disk space on the /boot directory run the `df -h /boot` command.
+ The active bootloader software is GRUB 1 or 2.
+ Secure Boot is not supported in Linux.
+ Machines that boot off a disk configured with GPT partitioning must have the package 'grub2-pc-modules' installed
+ When performing a failback for a Linux server, you must boot the Failback Client with BIOS boot mode.
+ Ensure that /tmp is mounted as read\$1write.
+ Boot disks that span multiple physical disks are not supported.
+ Ensure that /tmp is mounted with the exec option. Verify that the /tmp directory is mounted in a way that allows you to run scripts and applications from it.
To verify that the /tmp directory is mounted without the noexec option, run the `sudo mount | grep '/tmp'` command.
If the result is similar to the example, the issue exists in your OS: /dev/xvda1 on /tmp type ext4 (rw,noexec)
To fix and remove the noexec option from the mounted /tmp directory, run the `sudo mount -o remount,exec /tmp` command.
**Example of the troubleshooting procedure:**
![\[Terminal commands showing mount operations and grep searches for "/tmp" directory.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/agent66.png)
+ The AWS Elastic Disaster Recovery user needs to be a user in the sudoers list - a user who can perform sudo.
+ Ensure that the dhclient package is installed. The DHCP client is required because AWS Elastic Disaster Recovery configures recovered instances to use DHCP networking. If the package is not installed, use the appropriate command for your distribution:
+ On RHEL/CentOS/Oracle/Amazon Linux: `sudo yum install dhclient` or `sudo yum install dhcp-client`
+ On Debian/Ubuntu: `sudo apt install isc-dhcp-client`
+ On SUSE: `sudo zypper install dhcp-client`
+ Verify that you have kernel-devel/linux-headers installed that are exactly the same version as the kernel you are running.
The version number of the kernel headers should be identical to the version number of the kernel. Follow these steps:
1. Identify the version of your running kernel by running the `uname -r ` command. The 'uname -r' output version should match the version of one of the installed kernel headers packages (kernel-devel- / linux-headers-).
1. Identify the version of your kernel-devel/linux-headers by running:
+ On RHEL/CENTOS/Oracle/SUSE: `rpm -qa | grep kernel`. This command looks for kernel-devel.
+ On Debian/Ubuntu: `apt-cache search linux-headers`.
1. Verify that the folder that contains the kernel-devel/linux-headers is not a symbolic link. If the content of the kernel-devel/linux-headers, which match the version of the kernel, is actually a symbolic link, you need to remove the link before installing the required package.
To verify that the folder that contains the kernel-devel/linux-headers is not a symbolic link, run the following command:
+ On RHEL/CENTOS/Oracle: `ls -l /usr/src/kernels`
+ On Debian/Ubuntu/SUSE: `ls -l /usr/src`
These results show that the linux-headers are not a symbolic link.
![\[Terminal output showing directory listing with linux-headers files and their details.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/agent5.png)
1. If the content of the kernel-devel/linux-headers, which match the version of the kernel, is a symbolic link, you need to delete the link using the `rm /usr/src/` command.
For example: rm /usr/src/linux-headers-4.4.1
1. Install the correct kernel-devel/linux-headers from the repositories.
If none of the already installed kernel-devel/linux-headers packages match your running kernel version, you need to install the matching package.
**Note**
You can have several kernel headers versions simultaneously on your OS, and you can therefore safely install new kernel headers packages in addition to your existing ones, without uninstalling the other versions of the package. A new kernel headers package does not impact the kernel, and does not overwrite older versions of the kernel headers.
You must install a kernel headers package with the exact same version number of the running kernel. To install the correct kernel-devel/linux-headers, run:
+ On RHEL/CENTOS/Oracle/SUSE: `sudo yum install kernel-devel-`uname -r``
+ On Oracle with Unbreakable Enterprise Kernel: `sudo yum install kernel-uek-devel-`uname -r``
+ On Debian/Ubuntu: `sudo apt-get install linux-headers-`uname -r``
1. If no matching package was found on the repositories configured on your server, you can download it manually from the Internet and then install it.
To download the matching kernel-devel/linux-headers package, navigate to:
+ RHEL, CENTOS, Oracle, and SUSE [package directory](http://rpm.pbone.net/)
+ Debian [package directory](https://packages.debian.org/)
+ Ubuntu [package directory](https://packages.ubuntu.com/)
## Windows installation requirements
+ Install all available Windows updates on the server.
+ A minimum of 4 GB of free disk space is required to launch a drill or recovery instance.
+ When performing a recovery, you must boot the Failback Client with the same boot mode (BIOS or UEFI) as the Windows source server.
+ A graceful reboot from the OS menu or Windows CLI of a Windows source server does not trigger a rescan in AWS DRS once the source server is restarted. Hard reboots, disk changes, and crashes trigger a rescan.
+ Mount points must be assigned a drive letter to be recognized by Elastic Disaster Recovery. A folder path is not recognized.
# Windows operating systems supported by Elastic Disaster Recovery
AWS Elastic Disaster Recovery allows replication of physical, virtual or cloud-based source servers to the AWS Cloud for several versions of Windows.
## General Notes
**Important**
**Windows 2003** is no longer supported.
[Review the AWS Replication Agent installation requirements.](installation-requirements.md)
**These Windows operating systems are supported:**
| Operating system | Supported versions | Prerequisites and Limitations |
| --- | --- | --- |
| Microsoft Windows Server 2022 64-bit | | Requires .Net Framework version 4.5 or above to be installed by the end user. |
| Microsoft Windows Server 2019 64-bit | | Requires .Net Framework version 4.5 or above to be installed by the end user. |
| Microsoft Windows Server 2016 64-bit | | Requires .Net Framework version 4.5 or above to be installed by the end user. |
| Microsoft Windows 10 64-bit | | Ensure that the [auto sleep function in Windows 10](https://answers.microsoft.com/en-us/windows/forum/all/turn-off-auto-sleep-in-windows-10/79f2d86c-3378-495f-8da2-4d78021876d4) is disabled. Data replication may be interrupted if the feature is activated. |
| Microsoft Windows Server 2012 **This version has reached end of life. We recommend that you update to a more recent version.** | 64-bit and R2 64-bit | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Windows.html) |
| Microsoft Windows Server 2008 **This version has reached end of life. We recommend that you update to a more recent version.** | 64-bit and R2 64-bit | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Windows.html) |
| Microsoft Windows 7 64-bit **This version has reached end of life. We recommend that you update to a more recent version.** | | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Windows.html) |
# AWS DRS supported Linux operating systems
## General Notes
+ [Review the AWS Replication Agent installation requirements.](installation-requirements.md)
+ Linux kernel versions up to 6.14 are supported.
+ For source machines configured with LVM, on RHEL/Oracle version less than or equal to 9.4, please make sure to update the lvm package to `lvm2-2.03.23-1.el9` or later.
+ AWS Elastic Disaster Recovery does not support 32 bit versions of Linux.
+ Hard reboots, disk changes, and crashes trigger a rescan. Graceful reboots do not trigger a rescan in the following versions:
+ RHEL/CentOS/Oracle Linux 6\$1 (kernel versions 2.6.32–431 and above)
+ SUSE 12\$1
+ Ubuntu 16\$1 LTS
+ AL 2 and AL 2023
+ Rocky 8\$1
+ Debian 9\$1
**Important**
** Support deprecation notes **
**CentOS versions 6.x**:
Effective August 28, 2026, this operating system will no longer be supported.
**SLES versions 11.x**:
Effective August 28, 2026, this operating system will no longer be supported.
**Oracle versions 6.x**:
Effective August 28, 2026, this operating system will no longer be supported.
**Ubuntu 12.04**:
Effective August 20, 2026, this operating system will no longer be supported.
**Red Hat Enterprise Linux (RHEL) version 5.x and CentOS version 5.x**:
Effective December 30, 2025, this operating system is no longer supported.
**Debian 6.x-9.x**:
Effective April 30, 2026, this operating system will no longer be supported.
**These Linux operating systems are supported:**
| Operating system | Supported versions | Prerequisites and Limitations |
| --- | --- | --- |
| Amazon Linux | 1, 2, 2023 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Linux.html) |
| RHEL | 6.0 to 9.7 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Linux.html) |
| CentOS | 6.0 to 8.0 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Linux.html) |
| Oracle Linux | 6.0 to 7.0, 8.5 to 8.10, and 9.0 to 9.4 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Linux.html) |
| Rocky Linux | 8, 9.7 | For Rocky Linux 8.x, a prerequisite is to run `$ sudo yum install elfutils-libelf-devel` |
| SUSE | 11 SP4 to 15 SP5 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Linux.html) |
| Ubuntu | 12.04 to 24.04 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems-Linux.html) |
| Debian | 10 to 11 | Only Kernel 3.x or above are supported |
# Installing the AWS Replication Agent
You must install the AWS Replication Agent on each source server that you want to add to AWS Elastic Disaster Recovery. Agent installation is composed of the following steps:
**Topics**
+ [Generating the required AWS credentials](credentials.md)
+ [Using an instance profile for agent installation in AWS](agent-installations-in-aws.md)
+ [Installation instructions for the AWS Replication Agent](agent-installation-instructions.md)
+ [Installing the agent on a secured network](installing-agent-blocked.md)
+ [Uninstalling the agent](uninstalling-agent.md)
+ [Reinstalling the agent](reinstalling-agent.md)
+ [Supporting marketplace licenses](marketplace-license-requirements.md)
# Generating the required AWS credentials
In order to install the AWS Replication Agent, you must first generate the required AWS credentials. You can create temporary credentials with AWS STS.
**Important**
Temporary credentials have many advantages. You do not need to rotate them or revoke them when they are no longer needed, and they cannot be reused after they expire. You can specify for how long the credentials are valid, up to a maximum limit. Because they provide enhanced security, using temporary credentials is considered best practice and the recommended option. For more information, see [IAM security best practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-workloads-use-roles).
## Temporary credentials
Before you install the AWS Replication Agent, you need to generate temporary AWS security credentials. The temporary credentials provided by AWS Elastic Disaster Recovery utilize a similar mechanism to the one used by [IAM Roles Anywhere](https://docs.aws.amazon.com/rolesanywhere/latest/userguide/introduction.html).
To create temporary credentials, take the following steps:
1. [Create a new IAM Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) with the **AWSElasticDisasterRecoveryAgentInstallationPolicy** policy.
1. Request temporary security credentials [via AWS STS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html) using the [AssumeRole API](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html).
[Learn more about how temporary credentials work.](Agent-Related-FAQ.md#temporary-credentials-operation)
**Note**
You can also create the default IAM role with the required permissions as an instance profile, as described in [Instance profile role installation](https://docs.aws.amazon.com/drs/latest/userguide/adding-servers-from-aws-instances.html#Instance-Profile-Role-Installation ).
# Using an instance profile for agent installation in AWS
When installing the AWS Replication Agent on an Amazon EC2 instance (when the source and recovery servers are both in AWS Regions), you don't need to generate credentials. Instead, you can use an instance profile with the required IAM policy. For the actual agent installation steps, see [Installing on Linux](linux-agent.md) or [Installing on Windows](windows-agent.md).
+ Go to the EC2 console and select your EC2 instance.
+ From the top right-hand menu, select **Actions > Security > Modify IAM role**.
+ Use a role that contains the [AWSElasticDisasterRecoveryEc2InstancePolicy](security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.md) policy.
If none exists, click **Create new IAM role**, attach the policy and return to the EC2 console window.
+ Select your new role from the drop-down list and click **Update**.
# Installation instructions for the AWS Replication Agent
Once you have generated the required AWS credentials, you can install the AWS Replication Agent on your source servers. There are separate installation instructions for Linux and for Windows. Each operating system has its own installer.
**Topics**
+ [Installing the AWS Replication Agent on Linux](linux-agent.md)
+ [Installing the AWS Replication Agent on Windows](windows-agent.md)
+ [AWS Replication Agent Installer parameters](installer-parameters.md)
# Installing the AWS Replication Agent on Linux
To install the agent on a Linux source server, you should ensure that your source meets all the requirements listed in the [supported Linux operating systems](Supported-Operating-Systems-Linux.md) documentation.
Before installing, please ensure that you are aware of the following:
+ You need root privileges to run the Agent installer file on a Linux server. Alternatively, you can run the Agent Installer file with sudo permissions.
+ The Linux installer creates the **"aws-replication"** group and **"aws-replication"** user within that group. The Agent runs within the context of the newly created user. Agent installation attempts to add the user to **"sudoers"**. Installation fails if the Agent is unable to add the newly created **"aws-replication"** user to **"sudoers"**.
1. Download the agent installer `aws-replication-installer-init` onto your Linux source server.
The Agent installer download location follows this format:
`https://aws-elastic-disaster-recovery-.s3..amazonaws.com/latest/linux/aws-replication-installer-init`
**Note**
Replace `` with the AWS Region into which you are replicating.
The following is an example for downloading the installer file from the us-east-1 region:
------
#### [ wget ]
```
wget -O ./aws-replication-installer-init https://aws-elastic-disaster-recovery-us-east-1.s3.us-east-1.amazonaws.com/latest/linux/aws-replication-installer-init
```
------
#### [ curl ]
```
curl -o aws-replication-installer-init https://aws-elastic-disaster-recovery-us-east-1.s3.us-east-1.amazonaws.com/latest/linux/aws-replication-installer-init
```
------
**Note**
If you are using a legacy Linux OS that does not support TLS 1.2, you need to download the installer on a different server with an OS that supports TLS 1.2 and copy it to the legacy servers you intend to install the agent on.
The command line indicates when the installer has been successfully downloaded.
**Important**
If you need to validate the installer hash, the correct hash is here:
`https://aws-elastic-disaster-recovery-hashes-.s3..amazonaws.com/latest/linux/aws-replication-installer-init.sha512`
Replace `` with the AWS Region into which you are replicating.
For example, when using the **us-east-1** Region:
`https://aws-elastic-disaster-recovery-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/linux/aws-replication-installer-init.sha512`
**Note**
AWS Regions that are not opt-in also support the shorter installer path:
`https://aws-elastic-disaster-recovery-.s3.amazonaws.com/latest/linux/aws-replication-installer-init`. Replace `` with the AWS Region into which you are replicating.
1. Use this command on your source server in order to run the installation script.
```
chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
```
**Note**
To install the agent on a secured network, [learn about the additional required configurations](installing-agent-blocked.md).
If you require additional customization, you can add a variety of parameters to the installer script in order to manipulate the way the Agent is installed on your server. See the [AWS Replication Agent Installer Parameters](installer-parameters.md) for more information.
The installer confirms that the installation of the AWS Replication Agent has started.
```
$ chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
The installation of the AWS Replication Agent has started.
```
1. The installer prompts you to enter your **AWS Region Name**, the **AWS Access Key ID** and **AWS Secret Access Key** that you previously generated. Enter the complete AWS Region name (for example, eu-central-1), the full AWS Access Key ID and the full AWS Secret Access Key. If you are using temporary credentials, you also need to specify the session token.
```
$ chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
The installation of the AWS Replication Agent has started.
AWS Region name: us-east-1
AWS Access Key ID: AKIAI0SF0DNN71EXAMPLE
AWS Secret Access Key: wJalrXUtnFEMI/K71MDENG/bPxRfiCYEXAMPLEKEY
```
**Note**
You can also enter these values as part of the installation script command parameters. If you do not enter these parameters as part of the installation script, you are prompted to enter them one by one as described above. (for example: `chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init --region regionname --aws-access-key-id AKIAIOSFODNN71EXAMPLE --aws-secret-access-key wJalrXUtnFEMI/K71MDENG/bPxRfiCYEXAMPLEKEY`)
1. Once you have entered your credentials, the installer identifies volumes for replication. The installer displays the identified disks and prompts you to choose the disks you want to replicate.
```
$ chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
...
AWS Secret Access Key: wJalrXUtnFEMI/K71MDENG/bPxRfiCYEXAMPLEKEY
Identifying volumes for replication.
Choose the disks you want to replicate. Your disks are: /dev/sda,/dev/xvda
To replicate some of the disks, type the path of the disks, separated with a comma (for example, /dev/sda,/dev/sdb).
To replicate all disks, press Enter:
```
To replicate some of the disks, type the path of the disks, separated by a comma, as illustrated in the installer (such as: /dev/sda, /dev/sdb, etc). To replicate all of the disks, press Enter. The installer identifies the selected disks and prints their size.
```
$ chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
...
To replicate some of the disks, type the path of the disks, separated with a comma (for example, /dev/sda,/dev/sdb).
To replicate all disks, press Enter:
Identified volume for replication: /dev/xvda of size 8 GiB
```
The installer confirms that all disks were successfully identified.
```
$ chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
...
Identified volume for replication: /dev/xvda of size 8 GiB
All volumes for replication were successfully identified.
```
**Note**
When identifying specific disks for replication, do not use apostrophes, brackets, or disk paths that do not exist. Type only existing disk paths. Each disk you selected for replication is displayed with the caption **Disk to replicate identified**. However, the displayed list of identified disks for replication may differ from the data you entered. This difference can be due to several reasons:
The root disk of the source server is always replicated, whether you select it or not. Therefore, it always appears on the list of identified disks for replication.
AWS Elastic Disaster Recovery replicates whole disks. Therefore, if you choose to replicate a partition, its entire disk appears on the list and is later replicated. If several partitions on the same disk are selected, then the disk encompassing all of them appears only once on the list.
Incorrect disks may be chosen by accident. Ensure that the correct disks have been chosen.
**Important**
If disks are disconnected from a server, AWS Elastic Disaster Recovery can no longer replicate them, so they are removed from the list of replicated disks. When they are reconnected, the AWS Replication Agent cannot know that these were the same disks that were disconnected and therefore does not add them automatically. To add the disks after they are reconnected, rerun the AWS Replication Agent installer on the server.
Note that the returned disks need to be replicated from the beginning. Any disk size change is automatically identified, but also causes a resync. Perform a test after installing the Agent to ensure that the correct disks have been added.
1. After all of the disks to be replicated have been successfully identified, the installer downloads and installs the AWS Replication Agent on the source server.
```
$ chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
...
Identified volume for replication: /dev/xvda of size 8 GiB
All volumes for replication were successfully identified.
Downloading the AWS Replication Agent onto the source server... Finished
Installing the AWS Replication Agent onto the source server... Finished
```
1. Once the AWS Replication Agent is installed, the server is added to the AWS Elastic Disaster Recovery console and undergoes the initial sync process. The installer provides the source server's ID.
```
$ chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init
...
Installing the AWS Replication Agent onto the source server... Finished
Syncing the source server with the AWS Elastic Disaster Recovery console... Finished
The following is the source server ID: s-3146f90b19example
The AWS Replication Agent was successfully installed.
$
```
You can review this process in real time on the **Source servers** page.
# Installing the AWS Replication Agent on Windows
To install the AWS Replication Agent on a Windows source server, you should ensure that your source meets all the requirements listed in the [supported Windows operating systems](Supported-Operating-Systems-Windows.md) documentation.
Prior to installing the AWS Replication Agent, please ensure that you are aware of the following:
+ You need to run the agent installer file as an Administrator on each Windows server.
+ We recommend using Windows PowerShell, which supports the 'Ctrl\$1V' shortcut for pasting. Windows Command Prompt (cmd) does not support this functionality.
## Downloading the installer
Before installing the AWS Replication Agent, `AwsReplicationWindowsInstaller.exe`, it needs to be downloaded. Copy or distribute the downloaded agent installer to each Windows source server that you want to add to AWS Elastic Disaster Recovery.
The agent installer follows the following format:
`https://aws-elastic-disaster-recovery-.s3..amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe`
**Note**
Replace `` with the AWS Region into which you are replicating.
The following is an example command for downloading the installer file from the us-east-1 region:
**Note**
If you are using Windows Server 2016 or older, you may need to enable TLS 1.2 in PowerShell before downloading: `[System.Net.ServicePointManager]::SecurityProtocol = 'TLS12'`
```
Invoke-WebRequest "https://aws-elastic-disaster-recovery-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe" -OutFile .\AwsReplicationWindowsInstaller.exe
```
The command line indicates when the installer has been successfully downloaded.
**Note**
AWS Regions that are not opt-in also support the shorter installer path: `https://aws-elastic-disaster-recovery-.s3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe` . Replace `` with the AWS Region into which you are replicating.
Microsoft Windows Server versions 2008 and 2008 R2 use a version of the AWS Replication Agent that is only valid for those versions - `AwsReplicationWindowsLegacyInstaller.exe`. DO NOT use this installer file to install the agent on any other OS types. You can download it from `https://aws-elastic-disaster-recovery-.s3.amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe` . Replace `` with the AWS Region into which you are replicating.
Microsoft Windows Server 2012 uses a version of the AWS Replication Agent that is only valid for that version AwsReplicationWindows2012LegacyInstaller.exe. DO NOT use this installer file to install the agent on any other OS types. You can download it from `https://aws-elastic-disaster-recovery-.s3.amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe` . Replace `` with the AWS Region into which you are replicating.
If you need to validate the installer hash, the correct hash is here: `https://aws-elastic-disaster-recovery-hashes-.s3..amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512` (replace with the AWS Region into which you are replicating.)
### AWS Replication Agent download URL for Windows for each supported AWS Region
****
| Region name | Region identity | Download Link |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | https://aws-elastic-disaster-recovery-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| US East (Ohio) | us-east-2 | https://aws-elastic-disaster-recovery-us-east-2.s3.us-east-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| US West (N. California) | us-west-1 | https://aws-elastic-disaster-recovery-us-west-1.s3.us-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| US West (Oregon) | us-west-2 | https://aws-elastic-disaster-recovery-us-west-2.s3.us-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Hong Kong) | ap-east-1 | https://aws-elastic-disaster-recovery-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Tokyo) | ap-northeast-1 | https://aws-elastic-disaster-recovery-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Seoul) | ap-northeast-2 | https://aws-elastic-disaster-recovery-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Osaka) | ap-northeast-3 | https://aws-elastic-disaster-recovery-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Singapore) | ap-southeast-1 | https://aws-elastic-disaster-recovery-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Sydney) | ap-southeast-2 | https://aws-elastic-disaster-recovery-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Jakarta) | ap-southeast-3 | https://aws-elastic-disaster-recovery-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Melbourne) | ap-southeast-4 | https://aws-elastic-disaster-recovery-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Mumbai) | ap-south-1 | https://aws-elastic-disaster-recovery-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Asia Pacific (Hyderabad) | ap-south-2 | https://aws-elastic-disaster-recovery-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (Frankfurt) | eu-central-1 | https://aws-elastic-disaster-recovery-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (Zurich) | eu-central-2 | https://aws-elastic-disaster-recovery-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (Stockholm) | eu-north-1 | https://aws-elastic-disaster-recovery-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (Milan) | eu-south-1 | https://aws-elastic-disaster-recovery-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (Spain) | eu-south-2 | https://aws-elastic-disaster-recovery-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (Ireland) | eu-west-1 | https://aws-elastic-disaster-recovery-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (London) | eu-west-2 | https://aws-elastic-disaster-recovery-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Europe (Paris) | eu-west-3 | https://aws-elastic-disaster-recovery-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Canada (Central) | ca-central-1 | https://aws-elastic-disaster-recovery-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Middle East (UAE) | me-central-1 | https://aws-elastic-disaster-recovery-me-central-1.s3.me-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Middle East (Bahrain) | me-south-1 | https://aws-elastic-disaster-recovery-me-south-1.s3.me-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Israel (Tel Aviv) | il-central-1 | https://aws-elastic-disaster-recovery-il-central-1.s3.il-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| South America (São Paulo) | sa-east-1 | https://aws-elastic-disaster-recovery-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
| Africa (Cape Town) | af-south-1 | https://aws-elastic-disaster-recovery-af-south-1.s3.af-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe |
### Validating the downloaded AWS Replication Agent installer for Windows.
**Important**
If you need to validate the installer hash, the correct hash is here:
`https://aws-elastic-disaster-recovery-hashes-.s3..amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512`
Replace `` with the AWS Region into which you are replicating, for example: us-east-1:
`https://aws-elastic-disaster-recovery-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 `
****
| Region name | Region identity | SHA512 Hash Download Link |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | https://aws-elastic-disaster-recovery-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| US East (Ohio) | us-east-2 | https://aws-elastic-disaster-recovery-hashes-us-east-2.s3.us-east-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| US West (N. California) | us-west-1 | https://aws-elastic-disaster-recovery-hashes-us-west-1.s3.us-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| US West (Oregon) | us-west-2 | https://aws-elastic-disaster-recovery-hashes-us-west-2.s3.us-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Hong Kong) | ap-east-1 | https://aws-elastic-disaster-recovery-hashes-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Tokyo) | ap-northeast-1 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Seoul) | ap-northeast-2 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Osaka) | ap-northeast-3 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Singapore) | ap-southeast-1 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Sydney) | ap-southeast-2 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Jakarta) | ap-southeast-3 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Melbourne) | ap-southeast-4 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Mumbai) | ap-south-1 | https://aws-elastic-disaster-recovery-hashes-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Asia Pacific (Hyderabad) | ap-south-2 | https://aws-elastic-disaster-recovery-hashes-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (Frankfurt) | eu-central-1 | https://aws-elastic-disaster-recovery-hashes-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (Zurich) | eu-central-2 | https://aws-elastic-disaster-recovery-hashes-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (Stockholm) | eu-north-1 | https://aws-elastic-disaster-recovery-hashes-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (Milan) | eu-south-1 | https://aws-elastic-disaster-recovery-hashes-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (Spain) | eu-south-2 | https://aws-elastic-disaster-recovery-hashes-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (Ireland) | eu-west-1 | https://aws-elastic-disaster-recovery-hashes-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (London) | eu-west-2 | https://aws-elastic-disaster-recovery-hashes-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Europe (Paris) | eu-west-3 | https://aws-elastic-disaster-recovery-hashes-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Canada (Central) | ca-central-1 | https://aws-elastic-disaster-recovery-hashes-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Middle East (UAE) | me-central-1 | https://aws-elastic-disaster-recovery-hashes-me-central-1.s3.me-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Middle East (Bahrain) | me-south-1 | https://aws-elastic-disaster-recovery-hashes-me-south-1.s3.me-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| South America (São Paulo) | sa-east-1 | https://aws-elastic-disaster-recovery-hashes-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
| Africa (Cape Town) | af-south-1 | https://aws-elastic-disaster-recovery-hashes-af-south-1.s3.af-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 |
### AWS Replication Agent download URL for Windows versions 2008 and 2008 R2 for each supported AWS Region
| Region name | Region identity | Download Link |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | https://aws-elastic-disaster-recovery-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| US East (Ohio) | us-east-2 | https://aws-elastic-disaster-recovery-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| US West (N. California) | us-west-1 | https://aws-elastic-disaster-recovery-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| US West (Oregon) | us-west-2 | https://aws-elastic-disaster-recovery-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Hong Kong) | ap-east-1 | https://aws-elastic-disaster-recovery-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Tokyo) | ap-northeast-1 | https://aws-elastic-disaster-recovery-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Seoul) | ap-northeast-2 | https://aws-elastic-disaster-recovery-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Osaka) | ap-northeast-3 | https://aws-elastic-disaster-recovery-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Singapore) | ap-southeast-1 | https://aws-elastic-disaster-recovery-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Sydney) | ap-southeast-2 | https://aws-elastic-disaster-recovery-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Jakarta) | ap-southeast-3 | https://aws-elastic-disaster-recovery-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Melbourne) | ap-southeast-4 | https://aws-elastic-disaster-recovery-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Mumbai) | ap-south-1 | https://aws-elastic-disaster-recovery-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Asia Pacific (Hyderabad) | ap-south-2 | https://aws-elastic-disaster-recovery-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (Frankfurt) | eu-central-1 | https://aws-elastic-disaster-recovery-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (Zurich) | eu-central-2 | https://aws-elastic-disaster-recovery-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (Stockholm) | eu-north-1 | https://aws-elastic-disaster-recovery-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (Milan) | eu-south-1 | https://aws-elastic-disaster-recovery-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (Spain) | eu-south-2 | https://aws-elastic-disaster-recovery-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (Ireland) | eu-west-1 | https://aws-elastic-disaster-recovery-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (London) | eu-west-2 | https://aws-elastic-disaster-recovery-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Europe (Paris) | eu-west-3 | https://aws-elastic-disaster-recovery-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Canada (Central) | ca-central-1 | https://aws-elastic-disaster-recovery-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Middle East (UAE) | me-central-1 | https://aws-elastic-disaster-recovery-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Middle East (Bahrain) | me-south-1 | https://aws-elastic-disaster-recovery-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| South America (São Paulo) | sa-east-1 | https://aws-elastic-disaster-recovery-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
| Africa (Cape Town) | af-south-1 | https://aws-elastic-disaster-recovery-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe |
### Validating the downloaded AWS Replication Agent installer for Windows versions 2008 and 2008 R2.
**Important**
If you need to validate the installer hash, the correct hash is here:
`https://aws-elastic-disaster-recovery-hashes-.s3..amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512`
Replace `` with the AWS Region into which you are replicating, for example: us-east-1:
`https://aws-elastic-disaster-recovery-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 `
| Region name | Region identity | SHA512 Hash Download Link |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | https://aws-elastic-disaster-recovery-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| US East (Ohio) | us-east-2 | https://aws-elastic-disaster-recovery-hashes-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| US West (N. California) | us-west-1 | https://aws-elastic-disaster-recovery-hashes-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| US West (Oregon) | us-west-2 | https://aws-elastic-disaster-recovery-hashes-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Hong Kong) | ap-east-1 | https://aws-elastic-disaster-recovery-hashes-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Tokyo) | ap-northeast-1 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Seoul) | ap-northeast-2 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Osaka) | ap-northeast-3 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Singapore) | ap-southeast-1 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Sydney) | ap-southeast-2 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Jakarta) | ap-southeast-3 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Melbourne) | ap-southeast-4 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Mumbai) | ap-south-1 | https://aws-elastic-disaster-recovery-hashes-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Asia Pacific (Hyderabad) | ap-south-2 | https://aws-elastic-disaster-recovery-hashes-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (Frankfurt) | eu-central-1 | https://aws-elastic-disaster-recovery-hashes-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (Zurich) | eu-central-2 | https://aws-elastic-disaster-recovery-hashes-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (Stockholm) | eu-north-1 | https://aws-elastic-disaster-recovery-hashes-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (Milan) | eu-south-1 | https://aws-elastic-disaster-recovery-hashes-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (Spain) | eu-south-2 | https://aws-elastic-disaster-recovery-hashes-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (Ireland) | eu-west-1 | https://aws-elastic-disaster-recovery-hashes-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (London) | eu-west-2 | https://aws-elastic-disaster-recovery-hashes-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Europe (Paris) | eu-west-3 | https://aws-elastic-disaster-recovery-hashes-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Canada (Central) | ca-central-1 | https://aws-elastic-disaster-recovery-hashes-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Middle East (UAE) | me-central-1 | https://aws-elastic-disaster-recovery-hashes-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Middle East (Bahrain) | me-south-1 | https://aws-elastic-disaster-recovery-hashes-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| South America (São Paulo) | sa-east-1 | https://aws-elastic-disaster-recovery-hashes-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
| Africa (Cape Town) | af-south-1 | https://aws-elastic-disaster-recovery-hashes-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 |
### AWS Replication Agent download URL for Windows 2012 for each supported AWS Region
| Region name | Region identity | Download Link |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | https://aws-elastic-disaster-recovery-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| US East (Ohio) | us-east-2 | https://aws-elastic-disaster-recovery-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| US West (N. California) | us-west-1 | https://aws-elastic-disaster-recovery-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| US West (Oregon) | us-west-2 | https://aws-elastic-disaster-recovery-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Hong Kong) | ap-east-1 | https://aws-elastic-disaster-recovery-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Tokyo) | ap-northeast-1 | https://aws-elastic-disaster-recovery-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Seoul) | ap-northeast-2 | https://aws-elastic-disaster-recovery-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Osaka) | ap-northeast-3 | https://aws-elastic-disaster-recovery-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Singapore) | ap-southeast-1 | https://aws-elastic-disaster-recovery-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Sydney) | ap-southeast-2 | https://aws-elastic-disaster-recovery-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Jakarta) | ap-southeast-3 | https://aws-elastic-disaster-recovery-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Melbourne) | ap-southeast-4 | https://aws-elastic-disaster-recovery-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Mumbai) | ap-south-1 | https://aws-elastic-disaster-recovery-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Asia Pacific (Hyderabad) | ap-south-2 | https://aws-elastic-disaster-recovery-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (Frankfurt) | eu-central-1 | https://aws-elastic-disaster-recovery-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (Zurich) | eu-central-2 | https://aws-elastic-disaster-recovery-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (Stockholm) | eu-north-1 | https://aws-elastic-disaster-recovery-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (Milan) | eu-south-1 | https://aws-elastic-disaster-recovery-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (Spain) | eu-south-2 | https://aws-elastic-disaster-recovery-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (Ireland) | eu-west-1 | https://aws-elastic-disaster-recovery-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (London) | eu-west-2 | https://aws-elastic-disaster-recovery-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Europe (Paris) | eu-west-3 | https://aws-elastic-disaster-recovery-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Canada (Central) | ca-central-1 | https://aws-elastic-disaster-recovery-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Middle East (UAE) | me-central-1 | https://aws-elastic-disaster-recovery-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Middle East (Bahrain) | me-south-1 | https://aws-elastic-disaster-recovery-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| South America (São Paulo) | sa-east-1 | https://aws-elastic-disaster-recovery-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
| Africa (Cape Town) | af-south-1 | https://aws-elastic-disaster-recovery-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe |
### Validating the downloaded AWS Replication Agent installer for Windows 2012.
**Important**
If you need to validate the installer hash, the correct hash is here:
`https://aws-elastic-disaster-recovery-hashes-.s3..amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512`
Replace `` with the AWS Region into which you are replicating, for example: us-east-1:
`https://aws-elastic-disaster-recovery-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 `
| Region name | Region identity | SHA512 Hash Download Link |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | https://aws-elastic-disaster-recovery-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| US East (Ohio) | us-east-2 | https://aws-elastic-disaster-recovery-hashes-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| US West (N. California) | us-west-1 | https://aws-elastic-disaster-recovery-hashes-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| US West (Oregon) | us-west-2 | https://aws-elastic-disaster-recovery-hashes-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Hong Kong) | ap-east-1 | https://aws-elastic-disaster-recovery-hashes-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Tokyo) | ap-northeast-1 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Seoul) | ap-northeast-2 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Osaka) | ap-northeast-3 | https://aws-elastic-disaster-recovery-hashes-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Singapore) | ap-southeast-1 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Sydney) | ap-southeast-2 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Jakarta) | ap-southeast-3 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Melbourne) | ap-southeast-4 | https://aws-elastic-disaster-recovery-hashes-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Mumbai) | ap-south-1 | https://aws-elastic-disaster-recovery-hashes-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Asia Pacific (Hyderabad) | ap-south-2 | https://aws-elastic-disaster-recovery-hashes-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (Frankfurt) | eu-central-1 | https://aws-elastic-disaster-recovery-hashes-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (Zurich) | eu-central-2 | https://aws-elastic-disaster-recovery-hashes-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (Stockholm) | eu-north-1 | https://aws-elastic-disaster-recovery-hashes-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (Milan) | eu-south-1 | https://aws-elastic-disaster-recovery-hashes-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (Spain) | eu-south-2 | https://aws-elastic-disaster-recovery-hashes-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (Ireland) | eu-west-1 | https://aws-elastic-disaster-recovery-hashes-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (London) | eu-west-2 | https://aws-elastic-disaster-recovery-hashes-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Europe (Paris) | eu-west-3 | https://aws-elastic-disaster-recovery-hashes-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Canada (Central) | ca-central-1 | https://aws-elastic-disaster-recovery-hashes-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Middle East (UAE) | me-central-1 | https://aws-elastic-disaster-recovery-hashes-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Middle East (Bahrain) | me-south-1 | https://aws-elastic-disaster-recovery-hashes-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| South America (São Paulo) | sa-east-1 | https://aws-elastic-disaster-recovery-hashes-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
| Africa (Cape Town) | af-south-1 | https://aws-elastic-disaster-recovery-hashes-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 |
## Installing the agent
1. Run the agent installer file `AwsReplicationWindowsInstaller.exe` as an Administrator.
```
.\AwsReplicationWindowsInstaller.exe
```
The installer confirms that the installation of the AWS Replication Agent has started.
```
The installation of the AWS Replication Agent has started.
```
**Note**
To install the agent on a secured network, [learn about the additional required configurations](installing-agent-blocked.md).
1. The installer prompts you to enter your **AWS Region Name**, the **AWS Access Key ID** and the **AWS Secret Access Key** that you previously generated. Enter the complete AWS Region name (for example: eu-central-1), and the full AWS Access Key ID and AWS Secret Access Key. If you are using temporary credentials, you also need to specify the session token.
```
The installation of the AWS Replication Agent has started.
AWS Region name: us-east-1
AWS Access Key ID: AKIAI0SF0DNN71EXAMPLE
AWS Secret Access Key: wJalrXUtnFEMI/K71MDENG/bPxRfiCYEXAMPLEKEY
```
**Note**
You can also enter these values as part of the installation script command parameters. If you do not enter these parameters as part of the installation script, you are prompted to enter them one by one as described above. (for example: `.\AwsReplicationWindowsInstaller.exe --region regionname --aws-access-key-id AKIAIOSFODNN7EXAMPLE --aws-secret-access-key wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`)
If you require additional customization, you can add a variety of parameters to the installation script in order to manipulate the way the Agent is installed on your server. See the [Installer Parameters](installer-parameters.md) for more information.
1. Once you have entered your credentials, the installer verifies that the source server has enough free disk space for Agent installation and identify volumes for replication. The installer displays the identified disks and prompts you to choose the disks you want to replicate.
```
...
AWS Secret Access Key: wJalrXUtnFEMI/K71MDENG/bPxRfiCYEXAMPLEKEY
Verifying that the source server has enough free disk space to install the AWS Replication Agent.
(a minimum of 2GB of free disk space is required)
Identifying volumes for replication.
Choose the disks you want to replicate. Your disks are: c:
To replicate some of the disks, type the path of the disks, separated with a comma (for example, C:,D:).
To replicate all disks, press Enter:
```
To replicate some of the disks, type the path of the disks, separated by a comma, as illustrated in the installer (for example: C:, D:, etc). To replicate all of the disks, press **Enter**. The installer identifies the selected disks and prints their size.
```
...
Identifying volumes for replication.
Choose the disks you want to replicate. Your disks are: c:
To replicate some of the disks, type the path of the disks, separated with a comma (for example, C:,D:).
To replicate all disks, press Enter:
Disk to replicate identified: c:0 of size 30GiB
```
The installer confirms that all of the disks were successfully identified.
```
...
Identifying volumes for replication.
Choose the disks you want to replicate. Your disks are: c:
To replicate some of the disks, type the path of the disks, separated with a comma (for example, C:,D:).
To replicate all disks, press Enter:
Disk to replicate identified: c:0 of size 30GiB
All volumes for replication were successfully identified
```
**Note**
When identifying specific disks for replication, do not use apostrophes, brackets, or disk paths that do not exist. Type only existing disk paths. Each disk that you selected for replication is displayed with the caption **Disk to replicate identified**. However, the displayed list of identified disks for replication may differ from the data you entered. This difference can be due to several reasons:
The root disk of the source server is always replicated, whether you select it or not. Therefore, it always appears on the list of identified disks for replication.
AWS Elastic Disaster Recovery replicates whole disks. Therefore, if you choose to replicate a partition, its entire disk appears on the list and is later replicated. If several partitions on the same disk are selected, then the disk encompassing all of them appears only once on the list.
Incorrect disks may be chosen by accident. Ensure that the correct disks have been chosen.
**Important**
If disks are disconnected from a server, AWS Elastic Disaster Recovery can no longer replicate them, so they are removed from the list of replicated disks. When they are reconnected, the AWS Replication Agent cannot know that these were the same disks that were disconnected and therefore does not add them automatically. To add the disks after they are reconnected, rerun the AWS Replication Agent installer on the server.
Note that the returned disks need to be replicated from the beginning. Any disk size changes are automatically identified, but also cause a resync. Perform a test after installing the Agent to ensure that the correct disks have been added.
1. After all of the disks to be replicated have been successfully identified, the installer downloads and installs the AWS Replication Agent on the source server.
```
...
All volumes for replication were successfully identified
Downloading the AWS Replication Agent onto the source server... Finished
Installing the AWS Replication Agent onto the source server... Finished
```
1. Once the AWS Replication Agent is installed, the server is added to the AWS Elastic Disaster Recovery console and undergoes the initial sync process. The installer provides the source server's ID.
```
...
All volumes for replication were successfully identified
Downloading the AWS Replication Agent onto the source server... Finished
Installing the AWS Replication Agent onto the source server... Finished
Syncing the source server with the Elastic Disaster Recovery Console... Finished
The following is the source server ID: s-3146f90b19example
The AWS Replication Agent was successfully installed.
Press Enter to close...
```
You can review this process in real time on the **Source servers** page.
# AWS Replication Agent Installer parameters
The AWS Replication Agent Installer supports the following command line parameters.
**--region**
The region into which the installer registers the source server.
**--aws-access-key-id**
The AWS IAM Access Key used for authenticating the installing user. If this parameter is not provided, the installer prompts for it.
**--aws-secret-access-key**
The AWS IAM Secret Access Key tied to the AWS IAM Access Key used for authenticating the installing user. If this parameter is not provided, the installer prompts for it.
**--aws-session-token**
The session token is generated when using [temporary credentials](credentials.md#credentials-agent-temporary) generated using AWS STS.
**--account-id**
Use this parameter to install the DRS agent on an EC2 instance to replicate to another AWS account without any additional access key or temporary credentials. Specify the 12 digit ID of the account into which you want to replicate your source server. This action requires an EC2 instance profile with the [AWSElasticDisasterRecoveryEc2InstancePolicy ](security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.md) policy, to define the account to replicate into as a [Trusted Account](trusted-accounts.md#trusted-accounts-page) and select the roles in **Failback and in-AWS right-sizing roles**.
**--no-prompt**
Run the installation without prompting the user.
**--devices**
Specify exactly which disks to replicate.
**--force-volumes**
This parameter must be used with the *--no-prompt* parameter. This parameter cancels the automatic detection of physical disks to replicate. You need to specify the exact disks to replicate using the *--devices* parameter (including the root disk, failure to specify the root disk causes replication to fail). This parameter should only be used as a troubleshooting tool if the *--devices* parameter fails to identify the disks correctly.
**--tags**
Use this parameter to add resource tags to the source server. Use a space to separate each tag.
```
--tags {"Key1"="Value1" "Key2"="Value2"}
```
This flag may only be used when adding new source servers to AWS DRS. You cannot use the --tags flag to modify tags of source servers that have already been added to AWS DRS.
**--s3-endpoint**
Use this parameter to specify a VPC endpoint you created for S3 if you do not wish to open your firewall ports to access the default S3 endpoint. [Learn more about installing the Agent on a blocked network.](installing-agent-blocked.md)
**--endpoint**
Use this parameter to specify the Private Link endpoint you created for Elastic Disaster Recovery if you do not wish to open your firewall ports to access the default AWS Elastic Disaster Recovery endpoint. [Learn more about installing the agent on a blocked network.](installing-agent-blocked.md)
We do not recommend using this flag when installing the AWS Elastic Disaster Recovery Agent on an EC2 Instance, as it can prevent successful failback from occurring. We recommend ensuring DNS automatically resolves the `{region}.drs.amazonaws.com` entry to the Private Link endpoint rather than leveraging this parameter.
**--install-as-recovery-instance**
Use this parameter to add an existing AWS instance to AWS Elastic Disaster Recovery as a recovery instance. You may opt to add recovery instances if you have added additional EC2 instances to AWS and now want to recover them into source servers. You are asked to pair the newly added recovery instance with a source server during AWS Replication Agent installation.
**--proxy-address**
*Linux Installer only.*
Use this parameter to configure the agent to use a specific proxy server: `--proxy-address https://PROXY:PORT/`. Ensure the proxy configuration has the trailing forward slash (/).
**--exclude-instance-store-volumes**
Use this parameter to exclude instance store volumes from replication.
**--dualstack**
Use this parameter to configure the agent to use Elastic Disaster Recovery dual-stack API endpoints. When you specify this parameter, the agent communicates with Elastic Disaster Recovery through `drs.{region}.api.aws` instead of `drs.{region}.amazonaws.com`, and with Amazon S3 through `s3.dualstack.{region}.amazonaws.com` instead of `s3.{region}.amazonaws.com`.
This parameter enables IPv6 support for API communication between the agent and AWS services, with IPv4 as a fallback. This parameter does not set the **IP version** in the replication configuration settings, which determines the Internet Protocol version used for data replication. For more information about the **IP version** setting, see [IP version](data-routing.md#ip-version).
# Installing the agent on a secured network
The AWS DRS AWS Replication Agent installer needs network access to AWS Elastic Disaster Recovery and S3 endpoints. If your on-premises network is not open to Elastic Disaster Recovery and S3 endpoints, then you can install the Agent with the aid of PrivateLink.
You can connect your on-premises network to the subnet in your staging area VPC using AWS VPN or DirectConnect. To use the AWS VPN or DirectConnect, you must activate private IP in the replication settings.
These topics describe the connectivity prerequisites that enable you to install the agent. All of the settings apply to the target account (or the staging account in a multi-account scenario) and Region where you want to handle the recovery.
## Create a VPC Endpoint for AWS Elastic Disaster Recovery
To allow the AWS Replication Agent installer to communicate with AWS Elastic Disaster Recovery, create an interface VPC endpoint for AWS Elastic Disaster Recovery in your staging area subnet. This VPC endpoint is used exclusively for management traffic; replication data is transmitted directly between the source and replication servers. For more information, see [Creating an Interface Endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#create-interface-endpoint.html) in the Amazon VPC User Guide.
If the AWS replication agents are installed with a principal using [ AWSElasticDisasterRecoveryAgentInstallationPolicy ](security-iam-awsmanpol-AWSElasticDisasterRecoveryAgentInstallationPolicy.md) and a VPCE policy is used (to scope down access), add the following statement to your policy:
```
{
"Effect": "Allow",
"Principal": "*",
"Action": "execute-api:Invoke",
"Resource": "arn:aws:execute-api::*.*/POST/CreateSessionForDrs"
}
```
## Use the created VPC Endpoint for AWS Elastic Disaster Recovery
Once you have created the VPC Endpoint, the AWS Replication Agent can connect to Elastic Disaster Recovery via VPN/DirectConnect by using the --endpoint installation parameter. Learn more about [Private DNS for interface endpoints](https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-interface.html#vpce-private-dns) in the *Amazon VPC User Guide*.
Run the AWS Replication Agent installer with the --endpoint parameter. Enter your endpoint-specific DNS hostname within the parameter. The installer is then able to connect to AWS Elastic Disaster Recovery via the endpoint over your VPN/DirectConnect connection.
Example of an interface endpoint DNS name: vpce-0123456789-abcdef.drs..vpce.amazonaws.com
## Create an S3 Endpoint for AWS Elastic Disaster Recovery
To allow the AWS Replication Agent installer to communicate with S3, create an interface S3 endpoint for AWS Elastic Disaster Recovery in your staging area subnet. For more information, see [Endpoints for Amazon S3](https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-s3.html) in the *Amazon VPC User Guide*. The endpoint requires a security group that allows connection from the agent, enabling it to download components it needs for the installation.
## Use the created S3 Endpoint for AWS Elastic Disaster Recovery
Once you have created the interface VPC Endpoint, the AWS Replication Agent can connect to S3 via VPN/DirectConnect by using the --s3-endpoint installation parameter. Learn more about [Private DNS for interface endpoints](https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-interface.html#vpce-private-dns) in the *Amazon VPC User Guide*.
Run the AWS Replication Agent installer with the --s3-endpoint parameter. Enter your endpoint-specific DNS hostname. The installer is then able to connect to Elastic Disaster Recovery via the endpoint over your VPN/DirectConnect connection.
Example of an interface endpoint DNS name: vpce-0123456789-abcdef.s3..vpce.amazonaws.com
## Preparing the AWS VPC
To prepare the staging area subnet in a private subnet, two more endpoints have to be created to ensure the successful creation of the replication servers.
+ EC2 Interface Endpoint: used to establish connectivity to EC2 endpoint from the staging area subnet
+ S3 Gateway Endpoint: used by the replication servers to download the replication software from S3
For more information about setting up AWS Elastic Disaster Recovery with a site-to-site VPN connection, [visit this blog post](https://aws.amazon.com/blogs/storage/cross-region-aws-elastic-disaster-recovery-agent-installation-in-a-secured-network).
# Uninstalling the agent
Uninstalling the AWS Replication Agent from a source server stops the replication of that server. Uninstalling the AWS Replication Agent removes the source server from the Elastic Disaster Recovery Console.
## Uninstalling the Agent through the AWS Elastic Disaster Recovery console
To uninstall the AWS Replication Agent through the AWS Elastic Disaster Recovery console.
Navigate to the **Source servers** page.
Check the box to the left of each server that you want to disconnect from Elastic Disaster Recovery (by uninstalling the AWS Replication Agent). Open the **Actions** menu, and choose the **Disconnect from AWS** option to disconnect the selected server from AWS Elastic Disaster Recovery and AWS.
When the **Disconnect X server/s from service** dialog appears, click **Disconnect**.
The AWS Replication Agent is uninstalled from all of the selected source servers.
## Uninstalling the Agent manually through the source server
To uninstall the AWS Replication Agent manually through the source server:
**Windows**
Copy the following folder to a new location:`C:\Program Files (x86)\AWS Replication Agent\dist`
From the new location, run in CMD as an administrator:
`install_agent_windows.exe --remove`
**Linux**
As root, cd to `/var/lib/aws-replication-agent`.
Run the following commands from that folder:
`./stopAgent.sh`
`./uninstall_agent_linux.sh`
# Reinstalling the agent
To reinstall the AWS Replication Agent, download the latest version of the agent and follow the installation instructions. You do not need to remove any previous versions prior to reinstalling the agent.
+ [Linux](linux-agent.md)
+ [Windows](windows-agent.md)
**Note**
You must reinstall the agent to benefit from new features.
## Reinstalling the agent on a recovery instance
If you are reinstalling an agent on a recovery instance:
1. Select your recovery instance and choose **Disconnect from AWS** from the **Actions** drop-down menu.
1. When reinstalling the agent, include the **--install-as-recovery-instance** parameter.
Example:
```
chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init --install-as-recovery-instance s-abcd01234567890
```
**Note**
In order to reinstall the agent on a recovery instance, you need to provide the temporary credentials for a role that has the [AWSElasticDisasterRecoveryAgentInstallationPolicy](security-iam-awsmanpol-AWSElasticDisasterRecoveryAgentInstallationPolicy.md) policy.
# Supporting marketplace licenses
Installing the AWS replication agent on an EC2 instance on AWS that has one or more active subscriptions to a marketplace license requires taking the following points into consideration:
+ Some marketplace products do not function with certain instance types or in certain regions. DRS does not verify if the marketplace license applies to the instance type and region defined. To see if the marketplace product applies to the current settings, visit the marketplace product page. It is also highly recommended to do periodic drills as some of these incompatibilities are only identified upon launch.
+ If an agent is to be installed on an EC2 instance existing on one account (source account) which is a different AWS account than the AWS account where DRS is operated (the target account), it is mandatory to provide permissions that allow getting the marketplace license information from the source account. [Create a Failback and in-AWS right-sizing role for trusted account](adding-trusted-account.md#trusted-accounts-failback-role) using the target account AWS account ID. This role must be created in the source account, or the agent installation fails. If this role is removed or modified, launch operations might fail if new marketplace licenses are added.
+ If an agent was installed on an EC2 instance existing on one account (source account), and DRS is operated on a different account (target account), and a new volume, that has a marketplace license associated with it, is connected to the instance with the **Automatically replicate new disks** setting active, the volume might fail to be added if permissions to allow getting the marketplace license information were removed or do not exist. [Create a Failback and in-AWS right-sizing role for trusted account](adding-trusted-account.md#trusted-accounts-failback-role) using the target account AWS account ID, and re-install the agent if a volume fails to be added due to this reason.
+ In case of EC2 instances from one account that replicate to a staging account (see [multi-account](multi-account.md)) and launch in one or more target accounts, only the staging account must have a [Failback and in-AWS right-sizing role created](adding-trusted-account.md#trusted-accounts-failback-role) for.
# Adding instances from the Amazon EC2 Console
You can now add EC2 instances as source servers in DRS, starting from the EC2 console. New or existing instances can be added by selecting the appropriate action on the EC2 console, sending you to the AWS focused page allowing you to install the AWS replication agent used by DRS on the selected instances.
## Add instances
You can protect your EC2 instances using AWS Elastic Disaster Recovery (DRS) in the chosen AWS Region, by adding them to AWS DRS as source servers. Utilize AWS Systems Manager (SSM) if present on your instance to install the AWS replication agent, a step needed to start replicating data from your instance to AWS. Only instances managed by AWS Systems Manager would be able to have the AWS replication agent installed on them.
**Note**
You need an instance profile with the policies listed below in order to have your instances managed by SSM and for installing the AWS replication agent:
[AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html)
[AWSElasticDisasterRecoveryEC2InstancePolicy](https://docs.aws.amazon.com/drs/latest/userguide/security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.html)
Successfully installing the AWS replication agent adds the instance to AWS DRS (as a **source server**) in the chosen target region.
## Supported EC2 instances
**Note**
Any additional EBS volumes added during the EC2 Instance creation that are offline, unmounted, or unformatted are not replicated. Any volume that is later placed online or mounted with a valid file system is automatically replicated if [Automatically replicate new disks](https://docs.aws.amazon.com/drs/latest/userguide/volumes-drs.html#auto-replicate) is enabled.
This section lists all the instances that were selected to be protected by AWS DRS. The list shows which instances are currently managed by SSM and which instances are currently not managed. Only instances managed by SSM can have the AWS replication agent installed on them using this page. You can also install the agent using the installer as defined in [Installing the AWS Replication Agent](https://docs.aws.amazon.com/drs/latest/userguide/agent-installation.html), without requiring the SSM agent to be present and active on the server to be protected.
To have an instance managed by SSM, requires the SSM agent to be installed on a compatible operating system ([or preinstalled in the AMI](https://docs.aws.amazon.com/systems-manager/latest/userguide/ami-preinstalled-agent.html)), and the instance to have the correct permissions (as defined in the [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html) and the [AWSElasticDisasterRecoveryEC2InstancePolicy](https://docs.aws.amazon.com/drs/latest/userguide/security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.html) policies). To update the instance profiles, the **Instance profile role installation** section allows you to create the default instance profile (with the two policies mentioned above) if needed. The **Instance profiles** section allows you to assign instance profiles to instances, and automatically assigns the default instance profile to all instances that do not have any instance profile attached to them. Use the **Attach profiles to all instances** button to attach the assigned instance profiles to the instances in case the default profile was created and automatically assigned to them or if you changed the assigned instance profile.
## Target disaster recovery region
On this section, you can define the target disaster recovery region. This can be the same region where the instances are present in, or it can be a different region, for cross-region protection. AWS DRS must be initialized in the target region in order to protect the instances onto that region. The indicator next to the region’s name shows if AWS DRS is already initialized in the target region, or not. If the region is not initialized, a button labelled Initialize and configure AWS Elastic Disaster Recovery is visible and active. Choosing this button opens the AWS DRS initialization wizard for AWS DRS in the target region on another browser tab.
## Instance profile role installation - optional
This section provides you with the option to create the default IAM role with the required permissions as an instance profile. The role **AWSElasticDisasterRecoveryAutomatedAgentInstallRole** includes the permissions defined in the policies [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html) and [AWSElasticDisasterRecoveryEC2InstancePolicy](https://docs.aws.amazon.com/drs/latest/userguide/security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.html). These permissions are required to allow the SSM agent to operate and to install the AWS replication agent, respectively. Clicking the **Install default IAM role** installs this role. This needs to be done only once per account. If the role was already installed in the account, this button is inactive. The default instance profile role is automatically assigned to instances without an instance profile in the **Instance profiles** section. If you click the **Attach profiles to all instances** button, this role is attached to all instances it was assigned to in the **Instance profiles** section. If this default IAM role is not installed, you need to make sure you have an instance profile with the [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html) and [AWSElasticDisasterRecoveryEC2InstancePolicy](https://docs.aws.amazon.com/drs/latest/userguide/security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.html) policies (or the combined set of permissions within both of these policies).
## Instance profiles
This section lists all the instances that were selected to be protected by adding them as source servers to AWS DRS and their current instance profiles. Instances without any instance profile have the **AWSElasticDisasterRecoveryAutomatedAgentInstallRole** instance profile and IAM role assigned to them if it exists on this account. Using the default profile is not mandatory, as any instance profile in the account can be assigned to any instance, but care must be taken to verify each instance has an instance profile with the permissions defined in the [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html) and [AWSElasticDisasterRecoveryEC2InstancePolicy](https://docs.aws.amazon.com/drs/latest/userguide/security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.html) policies.
**Note**
AWS DRS does not validate the instance profile has the required permissions to support working with the SSM agent or installing the AWS replication agent for DRS.
**Note**
Attaching an instance profile with the needed permissions is a mandatory step if you want to install AWS DRS on instances that have the SSM agent installed on them (manually, or preinstalled on AMI) but are not managed on SSM due to missing an instance profile with the [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html) policy.
Click the button labelled **Attach profiles to all instances** to attach the assigned instance profiles to their instances.
After attaching such a profile, allow AWS DRS a few minutes to identify the instance as managed by SSM. If SSM is present on the instance, and an instance profile with the needed permissions was attached to the instance, then within a few minutes, the marker near the instance ID changes to show that the instance is currently managed by SSM.
## Attach profiles to all instances
Clicking this button attaches the instance profiles assigned in the **Instance profiles** section to their instances. After attaching appropriate instance profiles to instances, allow a few minutes for DRS to detect if these instances are managed by SSM.
## Add instances
Click this button to install the AWS replication agent on all instances that are currently managed by SSM. If there are such instances, AWS DRS lists those instances and the progress of installing the AWS replication agent on them. Successfully installing the AWS replication agent on these instances adds them as source servers to AWS DRS. If there are no instances that are currently managed by SSM, try installing the SSM agent on these instances, then attach an appropriate instance profile to them.
## Add instances result page
On this page you can view the result of adding instances to AWS DRS by installing the AWS replication agent on them. The page shows the progress of this process if currently running, or the summary of the last run. In addition, for each instance that is currently managed by SSM, there is a table listing the following:
**Instance ID** - The ID of the instance. This also links to the instance on the EC2 console page (opens in a different browser tab).
**Status** - The current status of the installation, possible values include **Success**, **In Progress**, **Pending** and **Error**.
**Details** - holds a link to the source servers page on the target region for successful installations, or a link to the run log on the SSM console (opens in a new browser tab) for runs that have failed, are pending or are in progress.