# AWS DRS source servers
Source servers

You must add your source servers to the AWS Elastic Disaster Recovery console in order to replicate them into AWS. Source servers are added by installing the AWS Replication Agent on each individual server. The following documentation provides installation paths for both Linux and Windows servers. Ensure that your servers are supported by AWS Elastic Disaster Recovery by reviewing the [supported Windows operating systems](Supported-Operating-Systems-Windows.md) and [supported Linux operating systems](Supported-Operating-Systems-Linux.md) documentation.

Once your source servers have been added to AWS Elastic Disaster Recovery, you can monitor and interact with them from the **Source Servers** page. The source servers page is the default view in the AWS Elastic Disaster Recovery Console, and is the page that you interact with the most. On the **Source Servers** page you can view all of your source servers, monitor their recovery readiness and data replication state, see the last recovery result, see any pending actions, and sort your servers by column contents. The command menus on the page allow you to perform source server actions such as adding source servers, editing settings, disconnecting, and deleting source servers. 

You can choose the hostname of any individual source server on the source servers page in order to access the server details view. This view allows you to see the details for individual servers. Here you are able to see an in-depth overview of the server's recovery state, view the server's technical details, manage tags, manage disks, and most importantly, configure the individual replications settings and launch settings for the server.

**Topics**
+ [

# Adding source servers to AWS DRS
](adding-servers.md)
+ [

# AWS DRS source servers page
](server-list.md)
+ [

# View server details with AWS DRS
](server-details.md)

# 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
Installation requirements

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 diskspace 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, i the issue exists in your OS: /dev/xvda1 on /tmp type ext4 (rw,noexec)

  \$1To 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-<version number> / linux-headers-<version number>).

  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/<LINK NAME>` 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
Supported Windows operating systems

AWS Elastic Disaster Recovery allows replication of physical, virtual or cloud-based source server 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
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 latest.
+ 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
Installation instructions

 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
Linux

To install the agent on a Linux source server, you should ensure that your source meets all the requirements list 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-<REGION>.s3.<REGION>.amazonaws.com/latest/linux/aws-replication-installer-init` 
**Note**  
Replace `<REGION>` 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-<REGION>.s3.<REGION>.amazonaws.com/latest/linux/aws-replication-installer-init.sha512`   
 Replace `<REGION>` 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-<REGION>.s3.amazonaws.com/latest/linux/aws-replication-installer-init`. Replace `<REGION>` with the AWS Region into which you are replicating.
**Note**  
If you are using a Windows Servers of versions 2016 or older, and are using PowerShell to download the installer, you need to enable TLS 1.2: `[System.Net.ServicePointManager]::SecurityProtocol = 'TLS12'` 

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. 

   ```
   $ 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 prompt 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 replication. Your disks are: /dev/sda,/dev/xvda
   To replication some of the disks, type the path of the disks, separated with a comma (for example, /dev/sda,/dev/sdb).
   To replication 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 replication some of the disks, type the path of the disks, separated with a comma (for example, /dev/sda,/dev/sdb).
   To replication 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 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
Windows

To install the AWS Replication Agent on a Windows source server, you should ensure that your source meets all the requirements list 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.

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-<REGION>.s3.<REGION>.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe`

**Note**  
Replace `<REGION>` with the AWS Region into which you are replicating.

The following is an example URL for downloading the installer file from the us-east-1 region : 

```
https://aws-elastic-disaster-recovery-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe
```

**Note**  
AWS Regions that are not opt-in also support the shorter installer path: `https://aws-elastic-disaster-recovery-<REGION>.s3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe` . Replace `<REGION>` with the AWS Region into which you are replicating.
If you are using a Windows Servers of versions 2016 or older, and are using PowerShell to download the installer, you need to enable TLS 1.2: `[System.Net.ServicePointManager]::SecurityProtocol = 'TLS12'` 
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-<REGION>.s3.amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe` . Replace `<REGION>` 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-<REGION>.s3.amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe` . Replace `<REGION>` 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-<region>.s3.amazonaws.com/latest/windows_legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512` (replace <region> 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-<REGION>.s3.<REGION>.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512`   
 Replace `<REGION>` 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-<REGION>.s3.<REGION>.amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512`   
 Replace `<REGION>` 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-<REGION>.s3.<REGION>.amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512`   
 Replace `<REGION>` 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 | 

1.  Run the agent installer file `AWSReplicationWindowsInstaller.exe` as an Administrator. 

   The installer confirms that the installation of the AWS Replication Agent has started. 

   ```
   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 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 replication. Your disks are: c:
   To replication some of the disks, type the path of the disks, separated with a comma (for example, C:,D:).
   To replication 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 replication. Your disks are: c:
   To replication some of the disks, type the path of the disks, separated with a comma (for example, C:,D:).
   To replication all disks, press Enter:
   Disk to replciate 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 replication. Your disks are: c:
   To replication some of the disks, type the path of the disks, separated with a comma (for example, C:,D:).
   To replication all disks, press Enter:
   Disk to replciate 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 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 re-connected, 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 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 occuring. 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 premise 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 premise 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:<region>:*.*/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.<REGION>.vpce.amazonaws.com

## Create a 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.<REGION>.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 though 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 on 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 very 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 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 to 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 allow 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. 

# AWS DRS source servers page
Source servers page

The **Source servers** page lists all of the source servers that were added to AWS Elastic Disaster Recovery. It allows you to manage your source servers and perform commands for one or more servers, such as controlling replication and launching Initiate recovery job instances. You are likely to interact with AWS Elastic Disaster Recovery predominantly through this page. 

**Topics**
+ [

# Interacting with the Source Servers page
](interracting.md)
+ [

# Source servers page command menus
](command-menus.md)
+ [

# Filtering on the source servers page
](list-filtering.md)

# Interacting with the Source Servers page


The **Source servers** page shows a list of source servers. Each row on the list represents a single server. 

The **Source servers** page provides key information for each source server under each of the columns on the page.

The columns include:
+ **Selector column** – This blank checkbox selector column allows you to select one or more source servers. When you select a server you can interact with it through the **Actions**, **Replication**, and **Initiate recovery job** menus. Selected servers are highlighted. 
+ **Hostname** – This column shows the unique server hostname for each source server. 
+ 
  + **Ready for recovery** – This column shows whether the server is ready for recovery. You can use this column to easily tell whether a server is ready or not and the server's exact status. You can learn more about the server's status by reviewing the **Data replication status** column. 
  + A server that is ready shows the green checkmark and **Ready**. 
  + A server that is ready, but is experiencing a non-critical issue such as lag shows the blue info sign and **Ready** and displays the lag duration to the right. 
  + A server that is still undergoing initial sync shows a gray circle with three dots and **Initial sync**. 
  + A server that is disconnected shows the gray warning sign and **Disconnected**. 
  + A server that is not ready due to a significant error, such as a stall, shows a red **X** and **Not Ready**. Servers that have one or more marketplace licenses assigned to them may not be able to launch if there was an error reading their license information. 
+ **Data replication status** – This column shows the current status of data replication for the server :
  + **Initiating** – The server has just been added to AWS Elastic Disaster Recovery and replication is being initiated. 
  + **Initial sync** – The server is undergoing the initial sync process. The console displays the percentage of the server data that has been synced and the step the server is undergoing in the initial sync process. You can learn more about the exact state of the server in the server info view. 
  + **Rescanning** – The server is undergoing a rescan. The console displays the percentage of the server data that has been rescanned successfully. 
  + **Healthy** – The server is healthy and is ready to initiate a recovery job. 
  + **Lag** – The server is experiencing lag. The console displays the amount of lag time. You can learn more about the exact state of the server in the server info view. 
  + **Stalled** – The server is stalled due to a replication error. You can learn more about the specific cause of the stall in the server info view. 
  + **Disconnected** – The server has been disconnected from AWS Elastic Disaster Recovery. 
+ **Last recovery result** – This column shows the result of the last recovery job launch. The column is empty if no recovery job has ever been launched for the server:
  + **Successful** - Recovery launch job was completed successfully. The console indicates how long ago the job was completed. 
  + **Failed** – Recovery launch job failed. The console indicates how long ago the job failed. You can learn more about why the job failed in the job history. 
  + **Pending** – Recovery launch job is pending. The console indicates how long ago the job was initiated. 
+ **Pending actions** – This column shows any pending actions that need to be performed on the server. This column appears empty unless there is an actionable pending action. Actions include:
  + **Initiate drill** – The source server is healthy, but no drill instances have been launched for the source server. Initiate a drill by launching a drill instance. 
  + **Resolve cause of stall** – The source server is stalled. Resolve the cause of the stall for the server to return to healthy function. 
  + **Reinstall AWS Replication Agent** – The AWS Replication Agent was removed from the source server. Reinstall the agent for replication to resume. 
  +  **Error: Missing permissions to retrieve marketplace licenses from the source account, cannot launch this server** – The marketplace license belongs to a different AWS account, permissions to get information about this marketplace license are missing. [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. 
  +  **Warning: server uses marketplace product, drill recommended** – This source server uses one or multiple marketplace licenses. Doing a drill is strongly recommended as some marketplace incompatibilities can only be identified during launch. [Learn more here.](marketplace-license-requirements.md) 

# Source servers page command menus
Command menus

You can perform a variety of actions, control data replication, and manage your drill and recovery instances for one or more source servers through the command menu buttons. Select one or more servers on the **Source servers** page and choose the **Actions**, **Replication**, or **Initiate recovery job** menu to control your source servers.

**Topics**
+ [

## Actions menu
](#server-actions-main)
+ [

## Initiate recovery job menu
](#server-initiate-recovery-main)
+ [

## Replication menu
](#server-replication-main)

## Actions menu


The **Actions** menu allows you to perform the following actions: 
+ **Add servers** – Choosing this option redirects you to the AWS Replication Agent installation instructions.
+ **Create extended source servers** – Choose this to start a wizard to create extended source servers from source servers replicating into staging accounts, in multi-account setups.
+ **Edit DRS launch settings** – Choose this option to edit a single or multiple selected source servers for their DRS launch settings.
+ **Edit EC2 launch template** – Choose this option to enter edit a single or multiple selected source servers for their EC2 launch template.
+ **Edit post-launch action settings** – Choose this option to activate or deactivate post-launch actions for a single or multiple selected source servers.
+ **View server details** – Choose this option to enter the source server's **Server details view.** 
+ **Disconnect from AWS** – Choose this 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**. 
**Important**  
This uninstalls the AWS Replication Agent from the source server and data replication will stop for the source server. This action does not affect any Drill or Recovery instances that have been launched for this source server, but you are no longer able to identify which source servers your Amazon EC2 instances correspond to. 
+ **Delete server** - Choose the **Delete server** option to permanently delete a source server from AWS Elastic Disaster Recovery. This removes all information related to the server from the AWS Elastic Disaster Recovery service. You can only delete servers that have been disconnected from AWS. You need to reinstall the AWS Replication Agent on a deleted source server to add it back to AWS Elastic Disaster Recovery. 

  When the **Delete X servers** dialog appears, click **Permanently delete**. Then, if the servers have associated recovery instances, you can either:
  + delete them, keeping the EC2 instances intact),
  + terminate them, which deletes the EC2 instances).

## Initiate recovery job menu


 The **Initiate recovery job** menu allows you to start drills and recoveries by launching drill and recovery instances as part of the overall failback process. You can learn more about the entire failback and failover process with AWS Elastic Disaster Recovery in the [Performing a failback and failover with AWS Elastic Disaster Recovery documentation](failback.md). 


+  **Initiate drill** – Choose this option to launch a drill instance for this server or group of servers for the purpose of testing your recovery solution. You should perform periodic drills in order to ensure that you are ready for recovery. [ Learn more about launching Drill instances in AWS Elastic Disaster Recovery](preparing-failover.md#recovery-drill-overview). 
+ **Initiate recovery** – Choose this option to launch a Recovery instances for this server or group of servers for the purpose of recovering the server in the event of a disaster. [Learn more about launching Recovery instances in AWS Elastic Disaster Recovery](failback-preparing-failover.md#failback-launching-instances). 

## Replication menu


 The **Replication** menu allows you to perform the following actions: 
+ **Stop replication** – You can stop replication of a source server at any time. After you stop the replication, you will no longer be charged for the ongoing replication and the staging area infrastructure. Changes will not be reported by the agent to the replication server, and all saved snapshots will be deleted, leaving this instance unprotected. The agent remains installed during this process. If you want to replicate this EC2 instance again, simply click the **Start replication** button. This triggers an initial sync. 
+ **Start replication** – You can start replication of a previously stopped source server. After you start the replication, the agent replicates the selected instances. 

# Filtering on the source servers page
Filtering

You can customize the **Source servers** page through filtering by recovery readiness. 

In the **Filter source servers....** field choose the filtering property from the menu. 

You can filter by a variety of properties, including: 
+ Any recovery readiness – Filter by specific alert (lagging, stalled, launched)
+ Not ready – Filter by a specific hostname or a specific string of characters
+ Ready – Filter by the recovery lifecycle state
+ Initial sync – Filter by the data replication status
+ Ready with lag
+ Disconnected

# View server details with AWS DRS
Server details

To access the server details view, click the **Hostname** of any server on the **Source servers** page. 

![\[Source servers list showing hostname, recovery readiness, and data replication status.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss11-details.png)


You can also access the server details view by checking the box to the left of any single source server on the **Source servers** page and choosing **Actions > View server details**. 

![\[Source servers list with options to view details, edit settings, or initiate recovery job.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss11-details2.png)


The server details view shows information and options for an individual server. Here, you can fully control and monitor the individual server. 

![\[AWS Elastic Disaster Recovery server details showing recovery status and options for a specific server.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details.png)


You can also perform a variety of actions, control replication, and launch Recovery instances for the individual server from the server details view.

The **Overview** box provides a basic overview of the server's status, including the whether the server is ready for recovery, any pending actions, the last recovery result (if any), and a link to the Recovery instance (if one was launched for the server). 

![\[Overview box showing server status: ready for recovery, no pending actions, successful last result.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details-overview.png)


# AWS DRS recovery dashboard
Recovery dashboard

The **Recovery dashboard** tab allows you to monitor the server, its data replication status, and view events and metrics in CloudTrail. 

![\[Recovery dashboard showing last recovery details and data replication status.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details-dashboard.png)


**Topics**
+ [

## Last recovery
](#lifecycle)
+ [

## Data replication status
](#data-replication-stat)
+ [

## Events and metrics
](#events)
+ [

## Server actions and replication control
](#actions)

## Last recovery


The **Last recovery** box provides an overview of the recovery process for the server.

![\[Recovery job details showing start time, job ID, and current status as healthy.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details-recovery.png)


Here, you can see the following:
+ **Job type** – The type of recovery job performed (drill or recovery)
+ **Job ID** – The ID of the last recovery job. Choose the **Job Id** to be redirected to the **Job** page for that specific recovery launch within the **Recovery job history**. 
+ **Job started** – The date and time the last recovery job was started.
+ **Job finished** – The date and time the last recovery job was finished. This field is blank if the job is still ongoing.
+ **Current recovery instance status** – The current status of the latest Recovery instance (if one has been launched).
+ **Status taken at** – The last date and time the** current recovery instance status** was queried.

## Data replication status


The **Data replication status** section provides an overview of the overall source server status, including:
+ **Replication progress** – The percentage of the server's storage that was successfully replicated.
+ **Rescan progress** – In the event of of a rescan, the percentage of the server's storage that was rescanned.
+ **Total replicated storage** – The total amount of storage replicated (in GiB).
+ **Lag** – Whether the server is experiencing any lag. If it is - the lag time is indicated.
+ **Backlog** – Whether there is any backlog on the server (in MiB)
+ **Elapsed replication time** – Time elapsed since replication first began on the server.
+ **Last seen** – The last time the server successfully connected to AWS Elastic Disaster Recovery.
+ **Replication start time** – The date and time replication first began on the server. 

Data replication can be in one of several states, as indicated in the panel title:
+ **Initial sync**: initial copying of data from external servers is not done. Progress bar and **Total replicated storage** fields indicate how far along the process is.
+ **Healthy**: all data has been copied and any changes at source are continuously being replicated (data is flowing).
+ **Rescan**: an event happened that forced the agent on the external server to rescan all blocks on all replicated disks. This is the same as an initial sync but is faster because only changed blocks need to be copied; a rescan progress bar appears.
+ **Stalled**: data is not flowing and user intervention is required (either initial sync never completes, or the state at the source becomes increasingly different from the state at AWS). When the state is stalled, then the replication initiation checklist is also shown, indicating where the error occurred that caused the stalled state.

This panel also shows:
+ **Total replicated storage:** size of all disks being replicated for this source server, and how much has been copied to AWS (once initial sync is complete)

  **Lag**: if you launch a recovery instance now, how far behind it is from the state at the source. Normally this should be none.

  **Backlog**: how much data has been written at source but has not yet been copied to AWS. Normally this should be none.

  **Last seen**: when is the last time the AWS Replication Agent communicated with the AWS DRS service or the replication server.

If everything is working as it should and replication has finished initializing, the Data replication progress section displays a **Healthy** status.

If there are initialization, replication, or connectivity errors, the **Data replication status** section displays the cause of the issue, for example, a stall. If the error occurred during the initialization process, then the exact step during which the error occurred is marked with a red "x" under **Replication initiation steps**.

## Events and metrics


You can review AWS Elastic Disaster Recovery events and metrics in AWS CloudTrail. Choose **View CloudTrail event history** to open AWS CloudTrail in a new tab. Learn more about AWS CloudTrail events in the [AWS CloudTrail user guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html). 

## Server actions and replication control


You can perform a variety of actions, control data replication, and manage your recovery and drill instances for an individual server from the server details view.

**Topics**
+ [

### Actions menu
](#server-actions)
+ [

### Initiate recovery job menu
](#server-initiate-recovery-menu-2)
+ [

### Alerts and errors
](#server-test-alert2)

### Actions menu


The **Actions** menu allows you to perform the following actions: 
+ **Add servers** – Choosing this option redirects you to the AWS Replication Agent installation instructions.
+ **Edit replication settings** – Choose this option to edit the replication settings for the selected server or group of servers through on the **Edit replication settings** tab. 
+ **Edit launch settings** – Choose this option to enter the source server's **Server details view > Launch settings** tab. 
+ **View server details** – Choose this option to enter the source server's **Server details view**. 
+ **Disconnect from AWS** – Choose this option to disconnect the selected server from AWS Elastic Disaster Recovery and AWS. 

  On the **Disconnect X server/s from service** dialog, choose **Disconnect**. 
**Important**  
This uninstalls the AWS Replication Agent from the source server, and data replication stops for the source server. This action does not affect any drill or recovery instances that have been launched for this source server, but you are no longer able to identify which source servers your Amazon EC2 instances correspond to. 
+ **Delete server** – Choose this option to permanently delete a source server from AWS Elastic Disaster Recovery. This removes all information related to the server from the AWS Elastic Disaster Recovery service. You can only delete servers that have been disconnected from AWS. You need to reinstall the AWS Replication Agent on a deleted source server to add it back to AWS Elastic Disaster Recovery. 

  When the **Delete X servers** dialog appears, click **Permanently delete**. 

### Initiate recovery job menu


The Initiate recovery job menu allows you to start drills and recoveries by launching drill and recovery instances as part of the overall failback process. You can learn more about the entire failback and failover process with AWS Elastic Disaster Recovery in the [Performing a failback and failover with AWS Elastic Disaster Recovery documentation](failback.md). 
+ **Initiate drill** – Choose the **Initiate drill** option to launch a drill instance for this server or group of servers for the purpose of testing your recovery solution. You should perform periodic drills in order to ensure that you are ready for recovery. [Learn more about launching drill instances in AWS Elastic Disaster Recovery.](preparing-failover.md#recovery-drill-overview) 
+ **Initiate recovery** – Choose the **Initiate recovery** option to launch a recovery instances for this server or group of servers for the purpose of recovering the server in the event of a disaster. [Learn more about launching recovery instances in AWS Elastic Disaster Recovery.](failback-preparing-failover.md#failback-launching-instances)

### Alerts and errors


You can distinguish between healthy servers and servers that are experiencing issues on the **Recovery dashboard** in several ways. The AWS Elastic Disaster Recovery console is color-coded for ease of use. 
+ Healthy servers with no errors are characterized by the color blue. The **Data replication status** boxes displays steps and information in blue if the server is healthy.
+ Servers that are experiencing temporary issues are characterized by the color yellow. This can include issues such as lag or a rescan. These issues do not break replication, but may delay replication or indicate a bigger problem. 
+ Servers that are experiencing serious issues are characterized by the color red. These issues can include a loss of connection, a stall, or other issues. You have to fix these issues in order for data replication to resume. 

  The **Data replication status** box includes details of the issue. 

  If the stall occurred during initiation, scroll down to **Replication initiation steps**. The step where the issue arose is marked with a red "x". 

# AWS DRS server info
Server info

The **Server info** tab shows general server information, hardware, and network information:
+ **General information**
  + **Last updated**: when was the data in this tab updated.
  + **Date added**: when was this server added to the service.
  + **AWS ID**: the ID of this source server resource.
  + **arn**: the AWS Resource Name for this source server.
+ **Identification hint**s: under most circumstances, the hostname is the best identifier, as it is what is used throughout the console as the name of the source server. If you need to validate which external server this is referring to in your data center, you can use one of the additional fields: Fully qualified domain name, VMware virtual machine identifier (only if source is VMWare), AWS instance ID (only is source is running on AWS).
+ **Hardware and operating system**: the CPUs, RAM, disks, and network interfaces on the external server, as well as the type and full name of the operating system running on that server. The disks shown are all the disk on the source server, and may include disks not being replicated.
+ **Recommended instance type**: this is the EC2 instance type the service is auto-recommending to use for the launched recovery instance. This is based only on the CPUs and RAM at the source (and not on utilization information). This is the instance type that is launched for this server by default. 

Information shown includes:
+ **Last updated**
+ **Date added**
+ **AWS ID** (if relevant)
+ **Hostname**
+ **Fully qualified domain name**
+ **VMware virtual machine identifier** (if relevant)
+ **AWS instance ID**
+ **AWS ID**
+ **CPUs**
+ **RAM**
+ **Disks**
+ **Network interfaces**
+ **Operating system** information
+ **Recommended instance type**

# Managing tags with AWS DRS
Tags

The Tags section shows any tags that have been assigned to the server. A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value. You can use tags to search and filter your resources or track your AWS costs. Learn more about AWS tags in [this Amazon EC2 article](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html). 

**Important**  
**Do not** alter the **Name** tag of resources created by AWS DRS (replication servers, EBS volumes, EBS snapshots, Conversion servers).

Choose **Manage tags** to open **Manage tags** page to add or remove tags. 
+ Choose **Add new tag** to add a new tag. Add a tag **Key** and an optional tag **Value**. Choose **Save** to save your added tags.
+ To remove a tag, choose **Remove** to the right of the tag you want to remove, and then choose **Save**.

# AWS DRS disk settings
Disk settings

The **Disk settings** tab shows a list of all of the disks on the source server and information for each disk:
+ **Disk name**
+ **Staging disk type** – The corresponding Amazon EBS volume disk type that is being used for the disk.
+ **Replicated storage** – The amount of storage that has been replicated from the disk to the Replication Server.
+ **Total storage** – The total storage capacity of the disk.
+  **Status** – shows the status of each disk, values can be either **Normal**, **Normal with marketplace license**, **Error** (with error description). Normal with marketplace license means that the server has at least one marketplace license associated with this volume. Volumes with marketplace licenses pose some limitations on launch: the target region and the selected instance type must support this license. If launching into a different account, the marketplace product must be subscribed to in that account as well or the launch fails. The state is set to Error if there is a problem with the volume, such as not having permissions to read the marketplace license details if the server is owned by a different AWS account. The value can also be empty if the status is not known at this time. 

## Change staging disk type


You can change the EBS volume disk type for each disk or for a group of disks. To change the EBS volume disk type:

1. Select the circle to the left of each disk name and choose **Change staging disk type**.

1. On the **Change staging disk type** dialog, select the type of EBS volume to use for the disk or group of disks.

1. Select the **AUTO** option if your volume's size is greater than 125 GiB and you want AWS Elastic Disaster Recovery to automatically select the most cost-effective EBS volume disk type for each disk based on the disk size and type based on the option you defined in the **Replication settings** (either the default **Lower cost, Throughput Optimized HDD (st1)** option or the **Faster, General Purpose SSD (gp2) or (gp3)** s option).

AWS Elastic Disaster Recovery uses a single Replication Server per 15 source disks. Selecting the **Auto** option ensures that the fewest number of replication servers are used, resulting in increased cost savings.

**Note**  
AWS Elastic Disaster Recovery always uses EBS magnetic volumes for disks that are under 125 GiB in size when you choose the **Auto** option.

If you do not want AWS Elastic Disaster Recovery to automatically select a disk, you can select a disk manually. Select the disk type from the **EBS volume type** menu.

For certain disks, you can configure the amount of IOPS to be allocated per GB of disk space under **IOPS**. You can allocate up to 50 IOPS per GB. 64,000 IOPS are available for Nitro-based instances. Other instances are guaranteed up to 32,000 IOPS. The maximum IOPS per instance is 80,000. 

Choose **Change** to confirm the change.

# AWS DRS replication settings
Replication settings

The **Replication settings** tab allows you to edit the replication settings for an individual source server. After the source server is added to AWS Elastic Disaster Recovery, the replication settings that are defined in the Replication Settings template are automatically applied to the server. You can later edit them for a single source server or multiple source servers through the **Replication settings** tab.

Edit each setting as required and then choose **Save replication settings**.

[Learn more about replication settings.](settings.md) 

# AWS DRS launch settings


The launch settings are a set of instructions that comprise an EC2 launch template and other settings, which determine how a recovery instance is launched for each source server on AWS. 

Launch settings, including the EC2 launch template, are automatically created every time you add a server to AWS Elastic Disaster Recovery. 

The launch settings can be modified at any time, including before the source servers have even completed initial sync.

[Learn more about individual launch settings.](launching-target-servers.md) 

**Important**  
**If the source server’s instance type includes instance store, please consider the following: **   
 It is **not** recommended to change the instance type of an instance to a type that has no ephemeral volumes, or has a different number of ephemeral volumes, as such changes could lead to data inconsistencies and may even cause recovery, drill, or failback to fail. 

# Post-launch settings
Post-launch settings

Post-launch settings allow you to control and automate actions performed after a recovery instance has been launched for the source server in AWS. These settings are created automatically based on the **Default post-launch actions**.

**Activating the post-launch actions for a specific source server**:
+ Navigate to the **Source servers** page and select a source server.
+ Go to the **Post-launch settings** tab. If **Post launch action settings** has **Post launch actions** set to **Active**, click **Edit** for **Post launch action settings**.
+ You will be redirected to the **Edit post-launch settings** screen. Make sure the **Post-launch actions active** option is not checked and click **Save**.

 Alternatively, you can activate and deactivate post-launch actions for multiple servers by navigating to the **Source servers** page, selecting the servers you want to update and clicking **Actions > Edit post-launch action settings**. To activate, make sure the **Post-launch actions active** option is checked, and to deactivate, it should be unchecked. If you made a change, click **Save**. 

**Topics**
+ [

# Adding custom actions with AWS DRS
](post-launch-action-settings-adding-custom-source.md)
+ [

# Activating, deactivating, and editing predefined or custom actions
](post-launch-action-settings-editing-source.md)
+ [

# Deleting custom actions
](post-launch-action-settings-deleting-source.md)
+ [

# Predefined post-launch actions
](predefined-post-launch-actions-source.md)

# Adding custom actions with AWS DRS
Adding custom actions

 AWS Elastic Disaster Recovery (AWS DRS) allows you to run any SSM document that you like – public SSM documents, SSM documents that you created and uploaded to your account or SSM documents that are shared with you. You can configure a custom action to run any SSM document that is available in your account. To be able to create, edit or delete a custom action, make sure the post-launch actions are activated for this source server. Custom actions added to the default settings are automatically added to newly added source servers. 

## Create a custom action


Adding a custom action through source server’s **Post-launch settings**, adds it to this source server. To add a custom action to all newly added source servers, use the **Settings → Default post-launch actions** page. To add a new custom action to the source server, go to **Source server details → Post-launch settings** tab. If the **Post-launch actions** post-launch actions settings is **Active**, you can create new custom actions by clicking on the **Add action** button. 

The **Add action** page includes these parameters:
+ **Action name** – The name of the action in AWS DRS, which should be intuitive, meaningful and unique in this AWS account and region.
+ **Activate this action** – Use this checkbox to activate or deactivate the custom action for this source server. Only active actions run after the launch of a recovery instance.
+ **Mark launch as successful only if this action finishes running successfully** – This checkbox dictates whether or not the launch is marked as successful, based on the successful run of this action. Instance launches progress normally regardless of the success of the action.
+ **System Manager document name** – Select any Systems Manager document that is available to be used in this account.
+ **View in Systems Manager** – Click to open **System Managers** and view additional information about the document.
+ **Description** – Add a description or keep the default.
+ **Document version** – Select which SSM document version to run. AWS DRS can run a default version, the latest version, or a specific version, according to your preferences.
+ **Category** – Select from various available categories including monitoring, validation, security and more.
+ **Order** – Specify the order in which the actions are executed. The lower the number, the earlier the action is executed. Values allowed are between 2 and 10,000. The numbers must be unique but don’t need to be consecutive.
+ **Platform** – Taken from the SSM document and reports which Operating System platform (Windows/Linux) is supported by the action. 
+ **Creator** – Who created the action. For custom actions, the default is always **This account**.

 The **Action parameters** change according to the specific SSM document that is selected. Note that for the instance ID parameter, you can choose to use the launch instance ID, in which case, AWS DRS dynamically populates the value. 

**Note**  
 AWS Elastic Disaster Recovery (AWS DRS) places **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** instance profile on the launch instance if post-launch actions is active for the source server. If you add an SSM command action that requires additional permissions in the launch instance, you must ensure that the instance profile has the right policies or the right permissions. In order to do so, create a role that has the required permissions as per the policies above or has a policy or policies with those permissions attached to it. Go to **Launch settings** > **EC2 launch template** > **Modify** > **Advance** > **IAM instance profile**. Use an existing profile or create a new one using the **Create new IAM profile** link. 

**Note**  
 Only trusted, authorized users should have access to the parameter store. For enhanced security, ensure that users who do not have permissions to execute SSM documents / commands, do not have access to parameter store. [Learn more about restricting access to Systems Manager parameters](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-access.html). Action parameters are stored in the SSM parameter store as regular strings. Changing parameters in the SSM Parameter store may impact the post launch action run on target instances. We recommend to consider security implications, when choosing to use parameters that contain scripts or sensitive information, such as API keys and database passwords. 

# Activating, deactivating, and editing predefined or custom actions


 You can activate, deactivate and edit actions available for this source server. Activating an action ensures it runs after launching a recovery instance. Likewise, deactivating it, prevents it from being run after launching a recovery instance. The default settings are not affected by activating, deactivating or editing an action for a source server. Editing an action for a source server updates it for that source server. These changes are not reflected on the action, if it exists in the default post-launch actions settings. Changes to actions in the default settings, as to apply to newly added source servers, can be done from the **Settings → Default post-launch actions** page. 

To be able to activate, create, deactivate, edit, or delete a custom action and to activate, deactivate or edit predefined actions for a source server, make sure the post-launch actions are activated for that source server.

## Activating, deactivating and editing predefined or custom actions


 To activate, deactivate or edit a post launch action in the default post-launch actions settings, go to **Source server details** page, and visit the **Post-launch settings** tab. If **Post-launch actions settings** shows **Post-launch actions** to be **Active**, you can edit any action defined for the source server. 

Locate the action you want to edit in the **Actions** card view, or use the search field to filter the actions by name.

Choose the action’s card to select it, and then choose the **Edit** button.

 To activate the action, make sure the **Activate this action setting** is checked and click the **Save** button. To deactivate, make sure the **Activate this action** setting is un-checked and click the **Save** button. 

 The edit page allow you to change the value of some of the parameters for both pre-defined actions and custom actions. Some parameters can only be edited if the action is a custom action. See below for specific information. 

The parameters that appear on the edit page:
+ **Action name** – Editable for custom actions. The name of the action in AWS DRS, which should be intuitive, meaningful and unique in this AWS account and region.
+ **Activate this action** – Use this checkbox to activate or deactivate the action for this source server. Only active actions run after the launch of a recovery instance.
+ **Mark launch as successful only if this action finishes running successfully** – This checkbox dictates whether or not the launch is marked as successful, based on the successful run of this action. Instances launches progress normally regardless of the success of the action.
+ **System Manager document name** – Editable for custom actions. Select any Systems Manager document that is available to be used in this account.
+ **View in Systems Manager** – Click to open **System Managers** and view additional information about the document.
+ **Description** – Editable for custom actions. Add a description or keep the default.
+ **Document version** – Editable for custom actions. Select which SSM document version to run. AWS DRS can run a default version, the latest version, or a specific version, according to your preferences.
+ **Category** – Editable for custom actions. Select from various available categories including monitoring, validation, security and more.
+ **Order** – Specify the order in which the actions run. The lower the number, the earlier the action runs. Values allowed are between 2 and 10,000. The numbers must be unique but don’t need to be consecutive.
+ **Platform** – Not editable. Taken from the SSM document and reports which Operating System platform (Windows/Linux) is supported by the action. 
+ **Creator** – Not editable. Who created the action. For custom actions, the default is always **This account**.

 The **Action parameters** change according to the specific SSM document that is selected. Note that for the instance ID parameter, you can choose to use the launch instance ID, in which case, AWS DRS dynamically populates the value. Some predefined actions, where applicable allow to use a dynamically populated value for the volumes. This value is dynamically populated by AWS DRS with the volumes of the instance being launched. 

After making the required changes, click **Save**, to save the changes and **Cancel** to abort them.

# Deleting custom actions


 Custom actions added to a source server from the default settings on creation or created later for that source server can also be deleted. Deleting a custom action for a source server removes it from that source server and means the action is no longer available to that source server. Deleting the action for a source server does not remove it from the default settings if the action was defined there as well. To delete a custom action from the default settings to avoid adding it to newly added source servers, go to the **Settings → Default post-launch actions** page, and delete the action from there. Pre-defined actions cannot be deleted. If a pre-defined action is not required, it can be deactivated. 

 Locate the action you want to delete in the **Actions** card view, or use the search field to filter the actions by name. Select the action, and click the **Delete** button. To confirm, press **Delete**. 

# Predefined post-launch actions


 AWS Elastic Disaster Recovery allows you to run various predefined post-launch actions on your EC2 launched instance. Use these out-of-the-box actions to improve your launch flexibility. 

These actions can be activated, edited or deactivated for a specific source servers.

[List of available pre-defined actions](https://docs.aws.amazon.com/drs/latest/userguide/predefined-post-launch-actions-default.html)