NEW - You can now accelerate your migration and modernization with AWS Transform. Read [Getting Started](https://docs.aws.amazon.com/transform/latest/userguide/getting-started.html) in the *AWS Transform User Guide*. # Source Servers in AWS Application Migration Service Source servers You must add your source servers to the AWS Application Migration Service console in order to migrate them into AWS. Source servers are added by installing the AWS Replication Agent on each individual server. This documentation provides installation paths for both Linux and Windows servers. Ensure that your servers are supported by AWS Application Migration Service by reviewing the [Supported operating systems](Supported-Operating-Systems.md) In addition, AWS Application Migration Service allows you to perform [agentless snapshot replication](agentless-mgn.md) from your vCenter source environment into AWS. This is achieved by installing the Application Migration Service vCenter Client in your vCenter environment. Agentless snapshot replication has its own unique credentials, installation, and replication mechanisms. AWS Application Migration Service recommends using agent-based replication when possible, as it supports CDP (Continuous Data Protection) and provides the shortest cutover window. Agentless replication should be used when your company's policies or technical issues prevent you from installing the AWS Replication Agent on each individual server. Once your source servers have been added to AWS Application Migration Service, you can monitor and interact with them from the Source servers page. The Source servers page is the default view in the AWS Application Migration Service 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 migration lifecycle and data replication state, see the next step in the migration process for each server, and sort your servers by a variety of categories. You can also perform a variety of commands from the Source servers page through the command menus. These menus allow you to full control your servers by managing data replication, launching test and cutover instances, and disconnecting servers from AWS Application Migration Service. You can click on 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 view of the server's migration lifecycle, browse an overview of the server's technical details, manage tags, manage disks, and most importantly, configure the individual replication settings and launch settings for the server. **Topics** + [ # Adding source servers ](adding-servers.md) + [ # Installing the AWS Application Migration Service vCenter Client for Agentless Replication on vCenter source environments ](agentless-mgn.md) + [ # Manage source servers ](server-list.md) + [ # Access details on a source server ](server-details.md) # Adding source servers Add source servers to AWS Application Migration Service by installing the AWS Replication Agent (also referred to as "the Agent") on them. The Agent can be installed on both Linux and Windows servers. You can add source servers from vCenter without installing an agent through the agentless replication feature. Quick links: + [Linux installation instructions](linux-agent.md) + [Windows installation instructions](windows-agent.md) + [Agentless replication instructions](agentless-mgn.md) **Note** While the use of AWS Application Migration Service is free for 90 days, you will incur charges for any AWS infrastructure that is provisioned during migration and after cutover, such as compute (Amazon EC2) and storage (Amazon EBS) resources. These are billed to your account separately, at your regular rates. **Topics** + [ # Installation requirements ](installation-requirements.md) + [ # Operating systems supported by Application Migration Service ](Supported-Operating-Systems.md) + [ # Installing the AWS Replication Agent ](agent-installation.md) # Installation requirements Before installing the AWS Replication Agent on your source servers, ensure that they meet these requirements: ## General requirements + Ensure that the source server operating system is supported by AWS. + [Supported Windows operating systems.](/mgn/latest/ug/Supported-Operating-Systems.html#Supported-Operating-Systems-Windows) + [Supported Linux operating systems.](/mgn/latest/ug/Supported-Operating-Systems.html#Supported-Operating-Systems-Linux) + Ensure that your setup meets all 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 Application Migration Service calculates the unique ID of the source server from the MAC address. When a MAC address changes, Application Migration Service 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. + AWS Application Migration Service does not support fully paravirtualized source servers. Source servers with partial paravirtualization, such as VMWare's paravirtualization of I/O devices, is supported. + The AWS Replication Agent installer supports multipath. ### Source server requirements These are universal requirements for both Linux and Windows source servers: + Root directory – Verify that your source server has at least 2 GB of free disk space on the root directory (/) . + Verify that your source server has at least 300 MB of free RAM to run the AWS Replication Agent. + Application Migration Service only supports operating systems built for the x86 system architecture. ## Linux installation requirements Ensure that your Linux source server meets these installation requirements prior to installing the AWS Replication Agent: + Python is installed on the server – Python 2 (2.4 or above) or Python 3 (3.0 or above). + These tools are required for agent installation only. The installer attempts to install them if they are not present already: ``` make gcc perl tar gawk rpm ``` + Verify that you meet these disk space requirements: + At least 2 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. After you have entered the commands for checking the available disk space, the results are displayed as: ![\[Terminal output showing disk space usage for root and tmp directories on Ubuntu Linux system.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agent1.png) + Ensure that you have Python installed on the source server (version 2.4\$1, version 3.0\$1) for Agent installation. + Only servers using the GRUB bootloader (GRUB 1 or 2) are supported. + Machines that boot off a disk configured with GPT partitioning must have the package 'grub2-pc-modules' installed + Secure Boot is not supported in Linux. + Boot disks that span multiple physical disks are not supported. + Ensure that */tmp* is mounted as read\$1write. + 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 this command: `sudo mount | grep '/tmp'` If the result is similar to this example, it means that the issue exists in your OS: ``` $ sudo mount | grep '/tmp' /dev/xvda1 on /tmp type ext4 (rw,noexec) ``` To fix and remove the *noexec* option from the mounted */tmp* directory, run this command: `sudo mount -o remount,exec /tmp` This example illustrates the troubleshooting procedure: ![\[Terminal commands showing mount operations and grep searches for /tmp directory.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agent66.png) + The AWS Application Migration Service user needs to be either a root user or a user in the sudoers list. + Ensure that the dhclient package is installed. If not, please install the package using: For Redhat/CentOS/Fedora/AmazonLinux: ``` sudo yum install dhclient ``` OR ``` sudo yum install dhcp-client ``` For Ubuntu/Debian: ``` sudo apt install isc-dhcp-client ``` For SUSE, check the [link](https://software.opensuse.org/download/package?package=dhcp-client&project=network%3Adhcp) for the instructions to install "`dhcp-client`" package + 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 completely identical to the version number of the kernel. To handle this issue, follow these steps: 1. Identify the version of your running kernel. `uname -r` ![\[Terminal output showing Linux kernel version 4.14.177-107.254.amzn2.x86_64.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agent2.jpg) The *uname -r* output version should match the version of one of the installed kernel headers packages (kernel-devel- / linux-headers-). 1. Identify the version of your *kernel-devel/linux-headers*. To identify the version of your running kernel, run this command: On RHEL/CENTOS/Oracle/SUSE: `rpm -qa | grep kernel` ![\[Terminal output showing installed kernel packages on a Linux system.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agent3.jpg) **Note** This command looks for kernel related packages. The kernel-devel package is the specific package to look for. On Debian/Ubuntu: `apt-cache search linux-headers` ![\[Terminal output showing search results for Linux kernel headers packages.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agent4.png) 1. Verify that the folder that contains the *kernel-devel/linux-headers* is not a symbolic link. Sometimes, the content of the *kernel-devel/linux-headers*, which match the version of the kernel, is actually a symbolic link. In this case, 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 this command: On RHEL/CENTOS/Oracle: ``` ls -l /usr/src/kernels ``` On Debian/Ubuntu/SUSE: ``` ls -l /usr/src ``` ![\[Terminal output showing Linux directory listing with kernel-related files and timestamps.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agent5.png) In the above example, the results show that the actual **linux-headers-\$1** folders are not symbolic links. 1. [If a symbolic link exists] Delete the symbolic link. If you found that 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. Run this command: `rm /usr/src/` 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. **Note** For everything to work, you need to install a kernel headers package with the exact same version number of the running kernel. To install the correct *kernel-devel/linux-headers*, run this command: On RHEL/CENTOS/Oracle: `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`` On SUSE: `sudo zypper install kernel-default-devel-`uname -r`` 1. [If no matching package was found] Download the matching *kernel-devel/linux-headers* package. 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 these sites: + [RHELand Centos](https://access.redhat.com/) + [Oracle](https://access.redhat.com/) + [SUSE](https://scc.suse.com/packages?name=SUSE) + [Debian](https://www.debian.org/distrib/packages/) + [Ubuntu](https://packages.ubuntu.com/) If the kernel-devel/linux-headers packages are not available for the current running kernel version, consider upgrading the kernel to a version that has corresponding kernel-devel packages available. System administrators should validate that the appropriate kernel-devel packages are available before upgrading the kernel. ## Windows installation requirements Ensure that your source server operating system is supported. See [Supported Windows operating systems.](/mgn/latest/ug/Supported-Operating-Systems.html#Supported-Operating-Systems-Windows). Ensure that your source server meets the agent installation hardware requirements, including: + At least 2 GB of free disk space on the disk containing the "Program Files(x86)" directory + Install all available Windows updates on the server. + A graceful reboot from the OS menu or Windows CLI of a Windows source server does not triggers a rescan in Application Migration Service 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 AWS Application Migration Service. A folder path is not recognized. # Operating systems supported by Application Migration Service Supported operating systems AWS Application Migration Service supports replication of physical, virtual or cloud-based source servers for multiple versions of Window and Linux operating systems. ## Supported Windows operating systems Supported Windows operating systems AWS Application Migration Service allows replication of physical, virtual or cloud-based source servers to the AWS Cloud for multiple versions of Windows. ### General Notes **Important** ** Support deprecation notes** **Windows 2003**: Effective February 15, 2026, this operating system is no longer supported. **Windows 2008**: Effective December 30, 2026, this operating system is no longer supported. **Windows 7**: Effective December 30, 2026, this operating system is no longer supported. + [Review the AWS Replication Agent installation requirements.](installation-requirements.md) + Windows source servers require a minimum of 2 GB of free disk space to launch a test or cutover instance. + The WMI service must be activated to install the AWS Replication Agent. **These Windows operating systems are supported:** | Operating system | Supported versions | Prerequisites and Limitations | | --- | --- | --- | | Microsoft Windows Server 2025 64-bit | | Requires .Net Framework version 4.5 or above to be installed by the end user. | | 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 | Requires .Net Framework version 4.5 or above to be installed by the end user. | | 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/mgn/latest/ug/Supported-Operating-Systems.html) | | Microsoft Windows Server 2003 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/mgn/latest/ug/Supported-Operating-Systems.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/mgn/latest/ug/Supported-Operating-Systems.html) | ## Supported Linux operating systems Supported Linux operating systems ### General Notes **Important** ** Support deprecation notes ** **Red Hat Enterprise Linux (RHEL) version 5.x and CentOS version 5.x**: Effective December 30, 2025, these operating systems are no longer supported. **Debian 6.x- 9.x**: Effective April 30, 2026, these operating systems are no longer supported. **Ubuntu 12.04**: Effective August 20, 2026, this operating system is no longer supported. **Oracle versions 6.x**: Effective August 28, 2026, these operating systems are no longer supported. **CentOS versions 6.x**: Effective August 28, 2026, these operating systems are no longer supported. **SLES versions 11.x**: Effective August 28, 2026, these operating systems are no longer supported. **CentOS 7-7.9**: Effective November 20, 2026, these operating systems are no longer supported. **Amazon Linux 1 (AL1)**: Effective November 20, 2026, this operating system is no longer supported. **Ubuntu 14.04**: Effective December 20, 2026, this operating system is no longer supported. **Debian 10**: Effective December 30, 2026, this operating system is no longer supported. **Red Hat Enterprise Linux (RHEL) versions 6.x**: Effective December 30, 2026, these operating systems are no longer supported. **CentOS versions 8.x**: Effective December 30, 2026, these operating systems are no longer supported. + [Review the AWS Replication Agent installation requirements.](installation-requirements.md) + Application Migration Service does not support 32 bit versions of Linux. + 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. + Kernel version 4.9.256 is not supported. Agent installation fails on servers that run this kernel version. + Kernel versions earlier than 2.6.18-164 are not supported by AWS Application Migration Service. Therefore, servers that run these kernel versions cannot be replicated by AWS Application Migration Service. **These Linux operating systems are supported:** | Operating system | Supported versions | Prerequisites and Limitations | | --- | --- | --- | | Amazon Linux | 1, 2, 2023 | Amazon Linux 1 is only supported for AWS to AWS recovery. | | RHEL | 6.0 to 9.7, 10, 10.1 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mgn/latest/ug/Supported-Operating-Systems.html) | | CentOS | 6.0 to 8.0 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mgn/latest/ug/Supported-Operating-Systems.html) | | Oracle Linux | 6.0 to 7.0, 8.5 to 8.9, and 9.0 to 9.4 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mgn/latest/ug/Supported-Operating-Systems.html) | | Rocky Linux | 8 to 9.7, 10, 10.1 | For Rocky Linux 8.x, a prerequisite is to run `$ sudo yum install elfutils-libelf-devel` | | SUSE Linux Enterprise Server | 11 SP4 to 15 SP7 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mgn/latest/ug/Supported-Operating-Systems.html) | | Ubuntu | 12.04 to 24.04 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mgn/latest/ug/Supported-Operating-Systems.html) | | Debian | 10 to 11 | Only Kernel 3.x or above are supported | | AlmaLinux | 9.6, 9.7, 10, 10.1 | For AlmaLinux, a prerequisite is to run `$ sudo yum install elfutils-libelf-devel` | # Installing the AWS Replication Agent You must install the AWS Replication Agent on each source server that you want to add to AWS Application Migration Service. You need to reinstall the AWS Replication Agent after any major upgrade to the source server (see [Agent Related FAQ](Agent-Related-FAQ.md#When-Reinstall-Agent) for more info). **Topics** + [ # Generating the required AWS credentials ](credentials.md) + [ # Installing the AWS Replication Agent on Linux servers ](linux-agent.md) + [ # Installing the AWS Replication Agent on Windows servers ](windows-agent.md) + [ # Installing the Agent on a secured network ](installing-agent-blocked.md) + [ # Uninstalling the Agent ](uninstalling-agent.md) + [ # Reinstalling the Agent ](reinstalling-agent.md) # Generating the required AWS credentials In order to install the AWS Replication Agent, you must first generate the required AWS credentials. **Important** Temporary credentials have many advantages. You don't need to rotate them or revoke them when they're 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. ## Temporary credentials The temporary credentials provided by AWS Application Migration Service 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, you need to: 1. [Create a new IAM Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) with the **AWSApplicationMigrationAgentInstallationPolicy** policy. 1. Request temporary security credentials [through AWS STS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html) through the [AssumeRole API](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html). An example of generating temporary credentials via AWS CLI can be found [here](https://docs.aws.amazon.com/cli/latest/reference/sts/assume-role.html#examples). [Learn more about how temporary credentials work.](Agent-Related-FAQ.md#temporary-credentials-operation) ## Permanent credentials Where possible, we recommend using temporary credentials instead of creating users who have long-term credentials such as passwords and access keys. However, there are specific use cases that require long-term credentials (for example, agentless snapshot based replications). In general, you should be able to use the same policy as recommended above in *Temporary Credentials*. ## Installing the AWS Replication Agent on an Amazon EC2 instance When installing an AWS Replication Agent on an Amazon EC2 instance (when the source server is in AWS Regions), you don't need to generate credentials. Instead, you can use an instance profile with the required IAM policy: + Go to the Amazon EC2 console and select your Amazon EC2 instance. + From the top right-hand menu, select **Actions > Security > Modify IAM role**. + Use a role that contains the [AWSApplicationMigrationServiceEc2InstancePolicy](security-iam-awsmanpol-AWSApplicationMigrationServiceEc2InstancePolicy.md) policy. If none exists, click **Create new IAM role**, attach the policy and return to the Amazon EC2 console window. + Select your new role from the drop-down list and click **Update**. # Installing the AWS Replication Agent on Linux servers Installing the agent on Linux servers Complete these steps to install the AWS Replication Agent on Linux source servers. 1. Ensure that the necessary service roles have been created by clicking on the Reinitialize service permissions button on the AWS Application Migration Service console's replication settings page. You must have the permissions necessary to create IAM roles in order for this operation to succeed. 1. Download the agent installer with the wget command your Linux source server. This wget command downloads the Agent installer file - aws-replication-installer-init onto your server. The Agent installer follows this format: `https://aws-application-migration-service-.s3..amazonaws.com/latest/linux/aws-replication-installer-init` . Replace `` with the AWS Region into which you are replicating. This is an example of the full wget command for us-east-1: `wget -O ./aws-replication-installer-init https://aws-application-migration-service-us-east-1.s3.us-east-1.amazonaws.com/latest/linux/aws-replication-installer-init ` The command line indicates when the installer has been successfully downloaded. **Important** 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. If you need to validate the installer hash, the correct hash can be found here: `https://aws-application-migration-service-hashes-.s3..amazonaws.com/latest/linux/aws-replication-installer-init.sha512` (replace with the AWS Region into which you are replicating. For example, us-east-1: https://aws-application-migration-service-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/linux/aws-replication-installer-init.sha512 Replicating Amazon EC2 instances that were launched with marketplace product codes, is not supported. **Note** 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`". AWS Regions that are not opt-in also support the shorter installer path: `https://aws-application-migration-service-.s3.amazonaws.com/latest/linux/aws-replication-installer-init` . Replace `` with the AWS Region into which you are replicating. You can generate a custom installation command through the **Add servers** prompt. [Learn more about the Add servers prompt](add-server-server-page.md#server-actions-main). This table contains the installer download link by supported AWS Region: **** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mgn/latest/ug/linux-agent.html) 1. [Generate the temporary credentials](credentials.md) that are required to install the AWS Replication Agent. **Important** When using [temporary credentials](credentials.md) (created using an IAM role instead of a user), you need to enter these parameters to the command prompt: AWS access key AWS secret access key AWS session token The request to enter an AWS session token only appears if the system identifies that you are using temporary credentials. AWS access key for temporary credentials begins with the letters ASIA. 1. Once the agent installer has successfully downloaded, copy and input the installer command into the command line on your source server in order to run the installation script. `sudo chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init` You can choose to add the Region and required credential as parameters in the installation scripts: + **--region** – The AWS Region in 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) that are generated using AWS STS. If you use temporary credentials and do not provide this parameter, the installer prompts for it. 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. Add the parameters to the end of the installation script. Available parameters include: + --no-prompt This parameter runs a silent installation. + --devices This parameter specifies which specific disks to replicate. The devices should be mentioned with comma separated, example `--devices="/dev/sda,/dev/sdb,/dev/sdc,/dev/sdd"` + --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 (for example: --tags KEY=VALUE [KEY=VALUE ...]) **Note** This flag may only be used when adding new source servers to Application Migration Service. You cannot use the --tags flag to modify tags of source servers that have already been added to Application Migration Service. + --s3-endpoint Use this parameter to specify a VPC endpoint you created for Amazon S3 if you do not wish to open your firewall ports to access the default Amazon S3 endpoint. [Learn more about installing the Agent on a blocked network.](installing-agent-blocked.md) + --user-provided-id This parameter allows you to provide a name to the source server that you are about to add, or identify a source server that needs to be updated. This identification is used by Application Migration Service to consistently recognize the server replication, and avoid duplication when [importing inventory](https://docs.aws.amazon.com/mgn/latest/ug/import-main.html) from a CSV file. Once provided for a server this parameter cannot be modified. + --endpoint Use this parameter: + To specify the private link endpoint you created for AWS Application Migration Service if you do not wish to open your firewall ports to access the default Application Migration Service endpoint. [Learn more about installing the Agent on a blocked network.](installing-agent-blocked.md) + When using dual-stack, to specify a Application Migration Service dual-stack endpoint. You must also specify the `--dualstack` flag. + --no-replication By default after agent installation, the replication begins automatically. This attribute allows you to install the agent without immediately starting the replication. The 90-day free replication period excludes hours where the replication was stopped. To start the replication post installation of replication agent using `--no-replication` attribute you can start replication by using the "Start Replication" option from Replication menu for the source server in the AWS MGN Dashboard or by using AWS CLI [start-replication](https://docs.aws.amazon.com/mgn/latest/APIReference/API_StartReplication.html) + --dualstack This parameter enables the agent to run in a dual-stack Application Migration Service configuration. When using this flag, you must also use the `--endpoint` flag to specify a Application Migration Service dual-stack endpoint. The installer confirms that the installation of the AWS Replication Agent has started. ![\[Terminal output showing successful start of AWS Replication Agent installation.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/sourceservers-linuxagent1.png) 1. The installer prompts you to enter your **AWS Region Name**, the **AWS Access Key ID**, the **AWS Secret Access Key**, and the **AWS Session Token** that you previously generated. Enter the complete AWS Region name (for example, eu-central-1) and the full credentials. ![\[Terminal window showing AWS Replication Agent installation with region and credential inputs.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/sourceservers-linuxagent2.png) **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: `sudo chmod +x aws-replication-installer-init; sudo ./aws-replication-installer-init --region regionname --aws-access-key-id AKIAIOSFODNN7EXAMPLE --aws-secret-access-key wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`). The AWS Access Key ID and AWS Secret Access Key values are hidden when entered into the installer. 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. ![\[Terminal window showing AWS Replication Agent installation and volume identification process.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/sourceservers-linuxagent3.png) 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, and more). To replicate all of the disks, click **Enter**. The installer identifies the selected disks and print their size. ![\[Terminal output showing AWS Replication Agent installation and volume identification process.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/sourceservers-linuxagent4.png) The installer confirms that all disks were successfully identified. ![\[Terminal output showing AWS Replication Agent installation and volume identification process.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/sourceservers-linuxagent5.png) **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 Application Migration Service 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 that disk 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 Application Migration Service 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 be replicated from the beginning. Any disk size changes are automatically identified, but this 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 that are to be replicated have been successfully identified, the installer downloads and installs the AWS Replication Agent on the source server. ![\[Terminal output showing AWS Replication Agent installation and volume identification process.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/sourceservers-linuxagent6.png) 1. Once the AWS Replication Agent is installed, the server is added to the AWS Application Migration Service console and undergoes the initial sync process. The installer provides you with the source server's ID. ![\[Terminal output showing AWS Replication Agent installation and volume identification process.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/sourceservers-linuxagent7.png) You can review this process in real time on the **Source servers** page. [Learn more about the initial sync process](migration-dashboard.md#initiation). # Installing the AWS Replication Agent on Windows servers Installing the agent on Windows servers Complete these steps to install the AWS Replication Agent on Windows source servers. Ensure that the necessary service roles have been created by clicking on the **Reinitialize service permissions** button on the AWS Application Migration Service console replication settings page. You must have the permissions necessary to create IAM roles in order for this operation to succeed. Download the agent installer (AWSReplicationWindowsInstaller.exe)**.** Copy or distribute the downloaded agent installer to each Windows source server that you want to add to AWS Application Migration Service. The agent installer follows this format: `https://aws-application-migration-service-.s3..amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe` . Replace `` with the AWS Region into which you are replicating. This is an example of the installer link for us-east-1: `https://aws-application-migration-service-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe` **Important** You need to run the agent installer file as an Administrator on each Windows server. If you need to validate the installer hash, the correct hash can be found here: `https://aws-application-migration-service-hashes-.s3..amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512` (replace with the AWS Region into which you are replicating, for example, us-east-1: https://aws-application-migration-service-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 We recommend using Windows PowerShell, which support ctrl\$1v pasting, and not Windows Command Prompt (cmd), which does not. Replicating Amazon EC2 instances that were launched with marketplace product codes, is not supported. **Note** AWS Regions that are not opt-in also support the shorter installer path: `https://aws-application-migration-service-.s3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe`. Replace `` with the AWS Region into which you are replicating. You can generate a custom installation command through the **Add servers** prompt. [Learn more about the Add servers prompt](add-server-server-page.md#server-actions-main). Microsoft Windows Server versions 2003, 2003 R2, 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 generate an installer by following the steps outlined in the [Add servers actions prompt documentation](add-server-server-page.md#server-actions-main) or directly download it from `https://aws-application-migration-service-.s3.amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe` . Replace `` with the AWS Region into which you are replicating. If you need to validate the installer hash, the correct hash can be found here: `https://aws-application-migration-service-hashes-.s3.amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512` (replace with the AWS Region into which you are replicating. Microsoft Windows Server 2012 uses a version of the AWS Replication Agent that is only valid for that version AwsReplicationWindows2012LegacyInstaller.exe. DO NOT use this installer file to install the agent on any other OS types. You can download it from `https://aws-application-migration-service-.s3.amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe` . Replace `` with the AWS Region into which you are replicating. If you need to validate the installer hash, the correct hash can be found here: `https://aws-application-migration-service-hashes-.s3.amazonaws.com/latest/windows_legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512` (replace with the AWS Region into which you are replicating. ## AWS Replication Agent download URL for Windows for each supported AWS Region **** | Region name | Region identity | Download Link | | --- | --- | --- | | US East (Ohio) | us-east-2 | **IPv4 - **https://aws-application-migration-service-us-east-2.s3.us-east-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-east-2.s3.dualstack.us-east-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | US East (N. Virginia) | us-east-1 | **IPv4 - **https://aws-application-migration-service-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-east-1.s3.dualstack.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | US West (N. California) | us-west-1 | **IPv4 - **https://aws-application-migration-service-us-west-1.s3.us-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-west-1.s3.dualstack.us-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | US West (Oregon) | us-west-2 | **IPv4 - **https://aws-application-migration-service-us-west-2.s3.us-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-west-2.s3.dualstack.us-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Africa (Cape Town) | af-south-1 | **IPv4 - **https://aws-application-migration-service-af-south-1.s3.af-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-af-south-1.s3.dualstack.af-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Hong Kong) | ap-east-1 | **IPv4 - **https://aws-application-migration-service-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-east-1.s3.dualstack.ap-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Jakarta) | ap-southeast-3 | **IPv4 - **https://aws-application-migration-service-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-3.s3.dualstack.ap-southeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Mumbai) | ap-south-1 | **IPv4 - **https://aws-application-migration-service-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-south-1.s3.dualstack.ap-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Osaka) | ap-northeast-3 | **IPv4 - **https://aws-application-migration-service-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-3.s3.dualstack.ap-northeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Seoul) | ap-northeast-2 | **IPv4 - **https://aws-application-migration-service-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-2.s3.dualstack.ap-northeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Singapore) | ap-southeast-1 | **IPv4 - **https://aws-application-migration-service-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-1.s3.dualstack.ap-southeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Sydney) | ap-southeast-2 | **IPv4 - **https://aws-application-migration-service-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-2.s3.dualstack.ap-southeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Malaysia) | ap-southeast-5 | **IPv4 - **https://aws-application-migration-service-ap-southeast-5.s3.ap-southeast-5.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-5.s3.dualstack.ap-southeast-5.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Thailand) | ap-southeast-7 | **IPv4 - **https://aws-application-migration-service-ap-southeast-7.s3.ap-southeast-7.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-7.s3.dualstack.ap-southeast-7.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Tokyo) | ap-northeast-1 | **IPv4 - **https://aws-application-migration-service-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-1.s3.dualstack.ap-northeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Canada (Central) | ca-central-1 | **IPv4 - **https://aws-application-migration-service-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ca-central-1.s3.dualstack.ca-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (Frankfurt) | eu-central-1 | **IPv4 - **https://aws-application-migration-service-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-central-1.s3.dualstack.eu-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (Ireland) | eu-west-1 | **IPv4 - **https://aws-application-migration-service-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-1.s3.dualstack.eu-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (London) | eu-west-2 | **IPv4 - **https://aws-application-migration-service-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-2.s3.dualstack.eu-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (Milan) | eu-south-1 | **IPv4 - **https://aws-application-migration-service-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-south-1.s3.dualstack.eu-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (Paris) | eu-west-3 | **IPv4 - **https://aws-application-migration-service-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-3.s3.dualstack.eu-west-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (Stockholm) | eu-north-1 | **IPv4 - **https://aws-application-migration-service-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-north-1.s3.dualstack.eu-north-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Middle East (Bahrain) | me-south-1 | **IPv4 - **https://aws-application-migration-service-me-south-1.s3.me-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-me-south-1.s3.dualstack.me-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | South America (São Paulo) | sa-east-1 | **IPv4 - **https://aws-application-migration-service-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-sa-east-1.s3.dualstack.sa-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Middle East (UAE) | me-central-1 | **IPv4 - **https://aws-application-migration-service-me-central-1.s3.me-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-me-central-1.s3.dualstack.me-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Melbourne) | ap-southeast-4 | **IPv4 - **https://aws-application-migration-service-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-4.s3.dualstack.ap-southeast-4.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Asia Pacific (Hyderabad) | ap-south-2 | **IPv4 - **https://aws-application-migration-service-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-south-2.s3.dualstack.ap-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (Zurich) | eu-central-2 | **IPv4 - **https://aws-application-migration-service-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-central-2.s3.dualstack.eu-central-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Europe (Spain) | eu-south-2 | **IPv4 - **https://aws-application-migration-service-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-south-2.s3.dualstack.eu-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | Tel Aviv | il-central-1 | **IPv4 - **https://aws-application-migration-service-il-central-1.s3.il-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-il-central-1.s3.dualstack.il-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | AWS GovCloud (US-East) | us-gov-east-1 | **IPv4 - **https://aws-application-migration-service-us-gov-east-1.s3.us-gov-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-gov-east-1.s3.dualstack.us-gov-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe | | AWS GovCloud (US-West) | us-gov-west-1 | **IPv4 - **https://aws-application-migration-service-us-gov-west-1.s3.us-gov-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-gov-west-1.s3.dualstack.us-gov-west-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-application-migration-service-hashes-.s3..amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512` Replace `` with the AWS Region into which you are replicating, for example: us-east-1: `https://aws-application-migration-service-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 | **IPv4 - **https://aws-application-migration-service-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-east-1.s3.dualstack.us-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | US East (Ohio) | us-east-2 | **IPv4 - **https://aws-application-migration-service-hashes-us-east-2.s3.us-east-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-east-2.s3.dualstack.us-east-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | US West (N. California) | us-west-1 | **IPv4 - **https://aws-application-migration-service-hashes-us-west-1.s3.us-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-west-1.s3.dualstack.us-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | US West (Oregon) | us-west-2 | **IPv4 - **https://aws-application-migration-service-hashes-us-west-2.s3.us-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-west-2.s3.dualstack.us-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Hong Kong) | ap-east-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-east-1.s3.dualstack.ap-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Tokyo) | ap-northeast-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-1.s3.dualstack.ap-northeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Seoul) | ap-northeast-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-2.s3.dualstack.ap-northeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Osaka) | ap-northeast-3 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-3.s3.dualstack.ap-northeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Singapore) | ap-southeast-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-1.s3.dualstack.ap-southeast-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Sydney) | ap-southeast-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-2.s3.dualstack.ap-southeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Jakarta) | ap-southeast-3 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-3.s3.dualstack.ap-southeast-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Melbourne) | ap-southeast-4 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-4.s3.dualstack.ap-southeast-4.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Malaysia) | ap-southeast-5 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-5.s3.ap-southeast-5.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-5.s3.dualstack.ap-southeast-5.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Thailand) | ap-southeast-7 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-7.s3.ap-southeast-7.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-7.s3.dualstack.ap-southeast-7.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Mumbai) | ap-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-south-1.s3.dualstack.ap-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Asia Pacific (Hyderabad) | ap-south-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-south-2.s3.dualstack.ap-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (Frankfurt) | eu-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-central-1.s3.dualstack.eu-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (Zurich) | eu-central-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-central-2.s3.dualstack.eu-central-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (Stockholm) | eu-north-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-north-1.s3.dualstack.eu-north-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (Milan) | eu-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-south-1.s3.dualstack.eu-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (Spain) | eu-south-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-south-2.s3.dualstack.eu-south-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (Ireland) | eu-west-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-1.s3.dualstack.eu-west-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (London) | eu-west-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-2.s3.dualstack.eu-west-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Europe (Paris) | eu-west-3 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-3.s3.dualstack.eu-west-3.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Canada (Central) | ca-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ca-central-1.s3.dualstack.ca-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Middle East (UAE) | me-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-me-central-1.s3.me-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-me-central-1.s3.dualstack.me-central-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Middle East (Bahrain) | me-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-me-south-1.s3.me-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-me-south-1.s3.dualstack.me-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | South America (São Paulo) | sa-east-1 | **IPv4 - **https://aws-application-migration-service-hashes-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-sa-east-1.s3.dualstack.sa-east-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | | Africa (Cape Town) | af-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-af-south-1.s3.af-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-af-south-1.s3.dualstack.af-south-1.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe.sha512 | ## AWS Replication Agent download URL for Windows versions 2003, 2003 R2, 2008, and 2008 R2 for each supported AWS Region | Region name | Region identity | Download Link | | --- | --- | --- | | US East (N. Virginia) | us-east-1 | **IPv4 - **https://aws-application-migration-service-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-east-1.s3.dualstack.us-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | US East (Ohio) | us-east-2 | **IPv4 - **https://aws-application-migration-service-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-east-2.s3.dualstack.us-east-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | US West (N. California) | us-west-1 | **IPv4 - **https://aws-application-migration-service-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-west-1.s3.dualstack.us-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | US West (Oregon) | us-west-2 | **IPv4 - **https://aws-application-migration-service-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-west-2.s3.dualstack.us-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Hong Kong) | ap-east-1 | **IPv4 - **https://aws-application-migration-service-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-east-1.s3.dualstack.ap-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Tokyo) | ap-northeast-1 | **IPv4 - **https://aws-application-migration-service-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-1.s3.dualstack.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Seoul) | ap-northeast-2 | **IPv4 - **https://aws-application-migration-service-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-2.s3.dualstack.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Osaka) | ap-northeast-3 | **IPv4 - **https://aws-application-migration-service-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-3.s3.dualstack.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Singapore) | ap-southeast-1 | **IPv4 - **https://aws-application-migration-service-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-1.s3.dualstack.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Sydney) | ap-southeast-2 | **IPv4 - **https://aws-application-migration-service-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-2.s3.dualstack.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Jakarta) | ap-southeast-3 | **IPv4 - **https://aws-application-migration-service-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-3.s3.dualstack.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Melbourne) | ap-southeast-4 | **IPv4 - **https://aws-application-migration-service-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-4.s3.dualstack.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Malaysia) | ap-southeast-5 | **IPv4 - **https://aws-application-migration-service-ap-southeast-5.s3.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-5.s3.dualstack.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Thailand) | ap-southeast-7 | **IPv4 - **https://aws-application-migration-service-ap-southeast-7.s3.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-7.s3.dualstack.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Mumbai) | ap-south-1 | **IPv4 - **https://aws-application-migration-service-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-south-1.s3.dualstack.ap-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Asia Pacific (Hyderabad) | ap-south-2 | **IPv4 - **https://aws-application-migration-service-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-south-2.s3.dualstack.ap-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (Frankfurt) | eu-central-1 | **IPv4 - **https://aws-application-migration-service-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-central-1.s3.dualstack.eu-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (Zurich) | eu-central-2 | **IPv4 - **https://aws-application-migration-service-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-central-2.s3.dualstack.eu-central-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (Stockholm) | eu-north-1 | **IPv4 - **https://aws-application-migration-service-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-north-1.s3.dualstack.eu-north-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (Milan) | eu-south-1 | **IPv4 - **https://aws-application-migration-service-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-south-1.s3.dualstack.eu-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (Spain) | eu-south-2 | **IPv4 - **https://aws-application-migration-service-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-south-2.s3.dualstack.eu-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (Ireland) | eu-west-1 | **IPv4 - **https://aws-application-migration-service-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-1.s3.dualstack.eu-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (London) | eu-west-2 | **IPv4 - **https://aws-application-migration-service-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-2.s3.dualstack.eu-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Europe (Paris) | eu-west-3 | **IPv4 - **https://aws-application-migration-service-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-3.s3.dualstack.eu-west-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Canada (Central) | ca-central-1 | **IPv4 - **https://aws-application-migration-service-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ca-central-1.s3.dualstack.ca-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Middle East (UAE) | me-central-1 | **IPv4 - **https://aws-application-migration-service-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-me-central-1.s3.dualstack.me-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Middle East (Bahrain) | me-south-1 | **IPv4 - **https://aws-application-migration-service-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-me-south-1.s3.dualstack.me-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | South America (São Paulo) | sa-east-1 | **IPv4 - **https://aws-application-migration-service-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-sa-east-1.s3.dualstack.sa-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | | Africa (Cape Town) | af-south-1 | **IPv4 - **https://aws-application-migration-service-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-af-south-1.s3.dualstack.af-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe | ## Validating the downloaded AWS Replication Agent installer for Windows versions 2003, 2003 R2, 2008, and 2008 R2. **Important** If you need to validate the installer hash, the correct hash is here: `https://aws-application-migration-service-hashes-.s3..amazonaws.com/latest/windows_legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512` Replace `` with the AWS Region into which you are replicating, for example: us-east-1: `https://aws-application-migration-service-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 | **IPv4 - **https://aws-application-migration-service-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-east-1.s3.dualstack.us-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | US East (Ohio) | us-east-2 | **IPv4 - **https://aws-application-migration-service-hashes-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-east-2.s3.dualstack.us-east-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | US West (N. California) | us-west-1 | **IPv4 - **https://aws-application-migration-service-hashes-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-west-1.s3.dualstack.us-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | US West (Oregon) | us-west-2 | **IPv4 - **https://aws-application-migration-service-hashes-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-west-2.s3.dualstack.us-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Hong Kong) | ap-east-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-east-1.s3.dualstack.ap-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Tokyo) | ap-northeast-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-1.s3.dualstack.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Seoul) | ap-northeast-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-2.s3.dualstack.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Osaka) | ap-northeast-3 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-3.s3.dualstack.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Singapore) | ap-southeast-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-1.s3.dualstack.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Sydney) | ap-southeast-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-2.s3.dualstack.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Jakarta) | ap-southeast-3 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-3.s3.dualstack.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Melbourne) | ap-southeast-4 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-4.s3.dualstack.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Malaysia) | ap-southeast-5 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-5.s3.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-5.s3.dualstack.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Thailand) | ap-southeast-7 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-7.s3.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-7.s3.dualstack.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Mumbai) | ap-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-south-1.s3.dualstack.ap-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Asia Pacific (Hyderabad) | ap-south-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-south-2.s3.dualstack.ap-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (Frankfurt) | eu-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-central-1.s3.dualstack.eu-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (Zurich) | eu-central-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-central-2.s3.dualstack.eu-central-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (Stockholm) | eu-north-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-north-1.s3.dualstack.eu-north-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (Milan) | eu-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-south-1.s3.dualstack.eu-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (Spain) | eu-south-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-south-2.s3.dualstack.eu-south-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (Ireland) | eu-west-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-1.s3.dualstack.eu-west-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (London) | eu-west-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-2.s3.dualstack.eu-west-2.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Europe (Paris) | eu-west-3 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-3.s3.dualstack.eu-west-3.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Canada (Central) | ca-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ca-central-1.s3.dualstack.ca-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Middle East (UAE) | me-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-me-central-1.s3.dualstack.me-central-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Middle East (Bahrain) | me-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-me-south-1.s3.dualstack.me-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | South America (São Paulo) | sa-east-1 | **IPv4 - **https://aws-application-migration-service-hashes-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-sa-east-1.s3.dualstack.sa-east-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 | | Africa (Cape Town) | af-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/AwsReplicationWindowsLegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-af-south-1.s3.dualstack.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 | **IPv4 - **https://aws-application-migration-service-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-east-1.s3.dualstack.us-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | US East (Ohio) | us-east-2 | **IPv4 - **https://aws-application-migration-service-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-east-2.s3.dualstack.us-east-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | US West (N. California) | us-west-1 | **IPv4 - **https://aws-application-migration-service-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-west-1.s3.dualstack.us-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | US West (Oregon) | us-west-2 | **IPv4 - **https://aws-application-migration-service-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-us-west-2.s3.dualstack.us-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Hong Kong) | ap-east-1 | **IPv4 - **https://aws-application-migration-service-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-east-1.s3.dualstack.ap-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Tokyo) | ap-northeast-1 | **IPv4 - **https://aws-application-migration-service-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-1.s3.dualstack.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Seoul) | ap-northeast-2 | **IPv4 - **https://aws-application-migration-service-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-2.s3.dualstack.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Osaka) | ap-northeast-3 | **IPv4 - **https://aws-application-migration-service-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-northeast-3.s3.dualstack.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Singapore) | ap-southeast-1 | **IPv4 - **https://aws-application-migration-service-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-1.s3.dualstack.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Sydney) | ap-southeast-2 | **IPv4 - **https://aws-application-migration-service-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-2.s3.dualstack.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Jakarta) | ap-southeast-3 | **IPv4 - **https://aws-application-migration-service-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-3.s3.dualstack.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Melbourne) | ap-southeast-4 | **IPv4 - **https://aws-application-migration-service-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-4.s3.dualstack.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Malaysia) | ap-southeast-5 | **IPv4 - **https://aws-application-migration-service-ap-southeast-5.s3.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-5.s3.dualstack.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Thailand) | ap-southeast-7 | **IPv4 - **https://aws-application-migration-service-ap-southeast-7.s3.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-southeast-7.s3.dualstack.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Mumbai) | ap-south-1 | **IPv4 - **https://aws-application-migration-service-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-south-1.s3.dualstack.ap-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Asia Pacific (Hyderabad) | ap-south-2 | **IPv4 - **https://aws-application-migration-service-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ap-south-2.s3.dualstack.ap-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (Frankfurt) | eu-central-1 | **IPv4 - **https://aws-application-migration-service-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-central-1.s3.dualstack.eu-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (Zurich) | eu-central-2 | **IPv4 - **https://aws-application-migration-service-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-central-2.s3.dualstack.eu-central-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (Stockholm) | eu-north-1 | **IPv4 - **https://aws-application-migration-service-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-north-1.s3.dualstack.eu-north-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (Milan) | eu-south-1 | **IPv4 - **https://aws-application-migration-service-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-south-1.s3.dualstack.eu-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (Spain) | eu-south-2 | **IPv4 - **https://aws-application-migration-service-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-south-2.s3.dualstack.eu-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (Ireland) | eu-west-1 | **IPv4 - **https://aws-application-migration-service-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-1.s3.dualstack.eu-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (London) | eu-west-2 | **IPv4 - **https://aws-application-migration-service-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-2.s3.dualstack.eu-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Europe (Paris) | eu-west-3 | **IPv4 - **https://aws-application-migration-service-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-eu-west-3.s3.dualstack.eu-west-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Canada (Central) | ca-central-1 | **IPv4 - **https://aws-application-migration-service-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-ca-central-1.s3.dualstack.ca-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Middle East (UAE) | me-central-1 | **IPv4 - **https://aws-application-migration-service-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-me-central-1.s3.dualstack.me-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Middle East (Bahrain) | me-south-1 | **IPv4 - **https://aws-application-migration-service-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-me-south-1.s3.dualstack.me-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | South America (São Paulo) | sa-east-1 | **IPv4 - **https://aws-application-migration-service-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-sa-east-1.s3.dualstack.sa-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe | | Africa (Cape Town) | af-south-1 | **IPv4 - **https://aws-application-migration-service-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe **Dual-stack - **https://aws-application-migration-service-af-south-1.s3.dualstack.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-application-migration-service-hashes-.s3..amazonaws.com/latest/windows_legacy/windows_2012_legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512` Replace `` with the AWS Region into which you are replicating, for example: us-east-1: `https://aws-application-migration-service-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 | **IPv4 - **https://aws-application-migration-service-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-east-1.s3.dualstack.us-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | US East (Ohio) | us-east-2 | **IPv4 - **https://aws-application-migration-service-hashes-us-east-2.s3.us-east-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-east-2.s3.dualstack.us-east-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | US West (N. California) | us-west-1 | **IPv4 - **https://aws-application-migration-service-hashes-us-west-1.s3.us-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-west-1.s3.dualstack.us-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | US West (Oregon) | us-west-2 | **IPv4 - **https://aws-application-migration-service-hashes-us-west-2.s3.us-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-us-west-2.s3.dualstack.us-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Hong Kong) | ap-east-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-east-1.s3.ap-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-east-1.s3.dualstack.ap-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Tokyo) | ap-northeast-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-1.s3.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-1.s3.dualstack.ap-northeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Seoul) | ap-northeast-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-2.s3.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-2.s3.dualstack.ap-northeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Osaka) | ap-northeast-3 | **IPv4 - **https://aws-application-migration-service-hashes-ap-northeast-3.s3.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-northeast-3.s3.dualstack.ap-northeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Singapore) | ap-southeast-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-1.s3.dualstack.ap-southeast-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Sydney) | ap-southeast-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-2.s3.dualstack.ap-southeast-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Jakarta) | ap-southeast-3 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-3.s3.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-3.s3.dualstack.ap-southeast-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Melbourne) | ap-southeast-4 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-4.s3.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-4.s3.dualstack.ap-southeast-4.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Malaysia) | ap-southeast-5 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-5.s3.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-5.s3.dualstack.ap-southeast-5.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Thailand) | ap-southeast-7 | **IPv4 - **https://aws-application-migration-service-hashes-ap-southeast-7.s3.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-southeast-7.s3.dualstack.ap-southeast-7.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Mumbai) | ap-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-ap-south-1.s3.ap-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-south-1.s3.dualstack.ap-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Asia Pacific (Hyderabad) | ap-south-2 | **IPv4 - **https://aws-application-migration-service-hashes-ap-south-2.s3.ap-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ap-south-2.s3.dualstack.ap-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (Frankfurt) | eu-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-central-1.s3.eu-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-central-1.s3.dualstack.eu-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (Zurich) | eu-central-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-central-2.s3.eu-central-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-central-2.s3.dualstack.eu-central-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (Stockholm) | eu-north-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-north-1.s3.eu-north-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-north-1.s3.dualstack.eu-north-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (Milan) | eu-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-south-1.s3.eu-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-south-1.s3.dualstack.eu-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (Spain) | eu-south-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-south-2.s3.eu-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-south-2.s3.dualstack.eu-south-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (Ireland) | eu-west-1 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-1.s3.eu-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-1.s3.dualstack.eu-west-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (London) | eu-west-2 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-2.s3.eu-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-2.s3.dualstack.eu-west-2.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Europe (Paris) | eu-west-3 | **IPv4 - **https://aws-application-migration-service-hashes-eu-west-3.s3.eu-west-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-eu-west-3.s3.dualstack.eu-west-3.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Canada (Central) | ca-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-ca-central-1.s3.ca-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-ca-central-1.s3.dualstack.ca-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Middle East (UAE) | me-central-1 | **IPv4 - **https://aws-application-migration-service-hashes-me-central-1.s3.me-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-me-central-1.s3.dualstack.me-central-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Middle East (Bahrain) | me-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-me-south-1.s3.me-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-me-south-1.s3.dualstack.me-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | South America (São Paulo) | sa-east-1 | **IPv4 - **https://aws-application-migration-service-hashes-sa-east-1.s3.sa-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-sa-east-1.s3.dualstack.sa-east-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | | Africa (Cape Town) | af-south-1 | **IPv4 - **https://aws-application-migration-service-hashes-af-south-1.s3.af-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 **Dual-stack - **https://aws-application-migration-service-hashes-af-south-1.s3.dualstack.af-south-1.amazonaws.com/latest/windows\$1legacy/windows\$12012\$1legacy/AwsReplicationWindows2012LegacyInstaller.exe.sha512 | ## Installation steps Installation steps Complete these steps to install the AWS Replication Agent on Windows source servers. 1. [Generate the temporary credentials](credentials.md) that are required to install the AWS Replication Agent. **Important** When using [temporary credentials](credentials.md) (created using an IAM role instead of a user), you need to enter these parameters to the command prompt: AWS access key AWS secret access key AWS session token The request to enter an AWS session token only appears if the system identifies that you are using temporary credentials. AWS access key for temporary credentials begins with the letters ASIA. 1. Run the agent installer file – AWSReplicationWindowsInstaller.exe – as an Administrator. The CMD opens. To run the installer with the default settings, enter your **AWS Region Name**, the **AWS Access Key ID** and the **AWS Secret Access Key**, and the **AWS Session Token** as described in the next step. 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. Add the parameters to the end of the installation script. + --no-prompt This parameter runs a silent installation. + --devices This parameter specifies which specific 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 (for example: --tags KEY=VALUE [KEY=VALUE ...]) **Note** This flag may only be used when adding new source servers to Application Migration Service. You cannot use the --tags flag to modify tags of source servers that have already been added to Application Migration Service. + --s3-endpoint Use this parameter to specify a VPC endpoint you created for Amazon S3 if you do not wish to open your firewall ports to access the default Amazon S3 endpoint. [Learn more about installing the Agent on a blocked network.](installing-agent-blocked.md) + --user-provided-id This parameter allows you to provide a name to the source server that you are about to add, or identify a source server that needs to be updated. This identification is used by Application Migration Service to consistently recognize the server replication, and avoid duplication when [importing inventory](https://docs.aws.amazon.com/mgn/latest/ug/import-main.html) from a CSV file. Once provided for a server this parameter cannot be modified. + --endpoint Use this parameter to specify the Private Link endpoint you created for AWS Application Migration Service if you do not wish to open your firewall ports to access the default Application Migration Service endpoint. [Learn more about installing the agent on a blocked network.](installing-agent-blocked.md) + --no-replication By default after agent installation, the replication begins automatically. This attribute allows you to install the agent without immediately starting the replication. The 90-day free replication period excludes hours where the replication was stopped. + --dualstack This parameter enables the agent to run in a dual-stack Application Migration Service configuration. The installer confirms that the installation of the AWS Replication Agent has started. ![\[Command prompt window showing the start of AWS Replication Agent installation.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/new-soureservers-windows1.png) 1. The installer prompts you to enter your **AWS Region Name**, the **AWS Access Key ID**, the **AWS Secret Access Key** (and the **AWS Session Token** if appropriate) 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. ![\[AWS Replication Agent installation window prompting for AWS Region Name and access keys.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/new-soureservers-windows2.png) **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)` 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 prompt you to choose the disks you want to replicate. ![\[AWS Replication Agent installation window showing region, access key, and disk space verification.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/new-soureservers-windows3.png) To replicate some of the disks, type the path of the disks, separated by a comma, as illustrated in the installer (for example: C: or D:). To replicate all of the disks, press **Enter**. The installer identifies the selected disks and print their size. ![\[AWS Replication Agent installer showing region, access key, and disk selection options.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/new-soureservers-windows4.png) The installer confirms that all of the disks were successfully identified. ![\[AWS Replication Agent installation progress showing disk selection and successful identification.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/new-soureservers-windows5.png) **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 Application Migration Service 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 only appears 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 Application Migration Service 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 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. ![\[AWS Replication Agent installation progress showing region, disk selection, and completion status.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/new-soureservers-windows6.png) 1. Once the AWS Replication Agent is installed, the server is added to the AWS Application Migration Service console and undergoes the initial sync process. The installer provides the source server's ID. ![\[Command prompt showing successful installation of AWS Replication Agent with disk replication details.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/new-soureservers-windows7.png) You can review this process in real time on the **Source servers** page. [Learn more about the initial sync process](migration-dashboard.md#initiation). # Installing the Agent on a secured network The AWS Application Migration Service AWS Replication Agent installer needs network access to Application Migration Service and Amazon S3 endpoints. If your on premises network is not open to Application Migration Service and Amazon S3 endpoints, then you can install the Agent with the aid of PrivateLink. You can connect your on premises network to the subnet in your staging area VPC using AWS Virtual Private Network or AWS Direct Connect. To use the Site-to-Site VPN or Direct Connect, you must [use private IP in the replication settings](replication-server-settings.md#use-private-ip) (not supported for IPv6). ## Create a VPC endpoint for AWS Application Migration Service To allow the AWS Replication Agent installer to communicate with Application Migration Service, create an interface VPC endpoint for Application Migration Service in your staging area subnet. 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 [ AWSApplicationMigrationAgentInstallationPolicy ](security-iam-awsmanpol-AWSApplicationMigrationAgentInstallationPolicy.md#security-iam-awsmanpol-AWSApplicationMigrationAgentInstallationPolicy.title) and a VPCE policy is used (to scope down access), add this statement to your policy: ``` { "Effect": "Allow", "Principal": "*", "Action": "execute-api:Invoke", "Resource": "arn:aws:execute-api::*:*/POST/CreateSessionForMgn" } ``` ## Use the created VPC Endpoint for AWS Application Migration Service Once you have created the VPC Endpoint, the AWS Replication Agent can connect to Application Migration Service via Site-to-Site VPN/Direct Connect 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 Application Migration Service via the endpoint over your Site-to-Site VPN/Direct Connect connection. ## Create an Amazon S3 endpoint for AWS Application Migration Service To allow the AWS Replication Agent installer to communicate with Amazon S3, create an interface Amazon S3 endpoint for Application Migration Service 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*. ## Use the created Amazon S3 Endpoint for AWS Application Migration Service Once you have created the Amazon VPC Endpoint, the AWS Replication Agent can connect to Amazon S3 via Site-to-Site VPN/Direct Connect 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 Application Migration Service via the endpoint over your Site-to-Site VPN/Direct Connect connection. ## Prescriptive guidance A detailed guide for rehosting servers using Application Migration Service over private networks is available here: [Migrating on-premises servers to AWS over private networks by using Application Migration Service.](https://docs.aws.amazon.com/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/welcome.html) # 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 AWS Application Migration Service console. **Note** The source server must be able to communicate with the Application Migration Service service in order for the Agent to be uninstalled successfully. If the Agent is uninstalled directly from a source server without disconnecting the server from Application Migration Service or finalizing the cutover within the Application Migration Service console, the replication metering period continues and once 2160 hours have elapsed, billing for replication begins. ## Uninstalling the Agent through the AWS Application Migration Service console To uninstall the AWS Replication Agent though the AWS Application Migration Service console. Navigate to the **Source servers** page. Check the box to the left of each server that you want to disconnect from Application Migration Service (by uninstalling the AWS Replication Agent). Open the **Actions** menu, and choose the **Disconnect from service** option to disconnect the selected server from Application Migration Service and AWS. On the **Disconnect X server/s from service** dialog, click **Disconnect**. The AWS Replication Agent is uninstalled from all of the selected source servers. You can then archive these servers. [Learn more about archiving.](add-server-server-page.md#server-actions-main) ## Uninstalling the Agent manually through the source server To uninstall the AWS Replication Agent manually through the source server: **Windows** Copy this 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** Run as root or with sudo these commands: `/var/lib/aws-replication-agent/uninstall-agent.sh` # Reinstalling the Agent To reinstall the AWS Replication Agent, download the latest version of the agent and follow the installation instructions. The AWS Replication Agent can be installed over an existing agent installation. You do not need to remove any previous versions prior to install. + [Installing the AWS Replication Agent on Linux servers](linux-agent.md) + [Installing the AWS Replication Agent on Windows serversInstallation steps](windows-agent.md) # Installing the AWS Application Migration Service vCenter Client for Agentless Replication on vCenter source environments Installing the vCenter Client AWS Application Migration Service allows you to perform agentless snapshot replication from your vCenter source environment into AWS. This is achieved by installing the Application Migration Service vCenter Client in your vCenter environment. Application Migration Service recommends using agent-based replication when possible, as it supports CDP (Continuous Data Protection) and provides the shortest cutover window. Agentless replication should be used when your company’s policies prevent you from installing the AWS Replication Agent on each individual server. **Topics** + [ # Agentless replication overview ](installing-vcenter-overview-mgn.md) + [ ## Prerequisites ](#installing-vcenter-prereques-mgn) + [ # VMware limitations ](installing-vcenter-reques-mgn.md) + [ # Generating vCenter Client IAM credentials ](vcenter-credentials-mgn.md) + [ # Installing the Application Migration Service vCenter Client ](installing-vcenter-appliance-mgn.md) + [ # Replicating servers from vCenter to AWS ](replicating-vcenter-aws-mgn.md) + [ # Updating the vCenter or AWS Credentials ](updating-vcenter-or-aws-credentials.md) + [ # Differentiating agentless and agent-based servers ](differences-vcenter-aws.md) # Agentless replication overview Agentless snapshot-based replication allows you to replicate source servers on your vCenter environment into AWS without installing the AWS Replication Agent. In order to use agentless replication, you must dedicate at least one VM in your vCenter environment to host the Application Migration Service vCenter Client. The Application Migration Service vCenter Client is a software bundle distributed by Application Migration Service and is available for installation as a binary installer. The installation process installs services on the client VM which allow Application Migration Service to remotely discover your VMs that are suitable for agentless replication, and to perform data replication between your vCenter environment and AWS through the use of periodic snapshot shipping. Agentless snapshot based replication is divided into two main operations: discovery and replication: The discovery process involves periodically scanning your vCenter environment to detect source server VMs that are suitable for agentless replication, and adding these VMs to the Application Migration Service console. Once a source server has been added, you may choose to initiate agentless replication on the source VM using the Application Migration Service API or console. The discovery process also collects all of the necessary information from vCenter in order to perform an agentless conversion process once a migration job is launched. The replication process involves continuously starting and monitoring the “snapshot shipping processes” on the source server VM being replicated. A “snapshot shipping process” is a long running logical operation which consists of taking a VMware snapshot on the replicated VM, and launching an ephemeral replication agent process which uses VMware’s Changed Block Tracking (CBT) feature to identify changed volume data location, using Virtual Disk Development Kit (VDDK) to read the modified data, and sending the data from the source environment to the customer’s target AWS account. The first snapshot shipping process performs an “initial sync” which sends the entire disk contents of the replicating VM into AWS. Following snapshot shipping processes leverage CBT only to sync disk changes to the customer’s target AWS account. Each successful snapshot shipping process completes the replication operation by creating a group of consistent Amazon EBS snapshots in the customer’s AWS account, which can then be used by the customer to launch test and cutover instances through the regular Application Migration Service mechanisms. These are the main system components of agentless replication: + Application Migration Service vCenter Client – A software bundle that is installed on a dedicated VM in your vCenter environment in order to facilitate agentless replication. + vCenter Replication Agent – A java agent that is based on the AWS Replication Agent, which replicates a single VM using VDDK and CBT as the data source instead of the Application Migration Service driver (that is used by the AWS Replication Agent) + Application Migration Service Service + Application Migration Service console **Note** Agentless replication does not work in IPv6-only source environments. This diagram illustrates the high level interaction between the different agentless replication system components: ![\[Diagram showing agentless replication from corporate data center to AWS Cloud with staging and migration steps.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agentless-architecture.png) ## Prerequisites 1. Ensure that you have initialized AWS Application Migration Service. # VMware limitations Application Migration Service supports VMC on AWS for agentless replication. + Application Migration Service partially supports vMotion, Storage vMotion, and other features based on virtual machine migration (such as DRS and Storage DRS) subject to these limitations: + Migrating a virtual machine to a new ESXi host or datastore after one replication run ends, and before the next replication run begins, is supported as long as the vCenter account has sufficient permissions on the destination ESXi host, datastores, and datacenter, and on the virtual machine itself at the new location. + Migrating a virtual machine to a new ESXi host, datastore, and/or datacenter while a replication run is active – that is, while a virtual machine upload is in progress – is not supported. Cross vCenter vMotion is not supported for use with Application Migration Service. + AWS does not provide support for migrating VMware Virtual Volumes. # Generating vCenter Client IAM credentials In order to use the Application Migration Service vCenter Client, you must first generate the correct IAM credentials. You need to create at least one AWS Identity and Access Management (IAM) user, and assign the proper permission policies to this user. Obtain an Access key ID and Secret access key, which you need to enter into the Agent installation prompt in order to begin the installation. We recommend that you use **IAM access last used information** to rotate and remove access keys safely. For more information, see [Rotating access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_RotateAccessKey). 1. Open the **AWS Management Console** and look for **IAM** under **Find Services**. 1. From the **IAM** main page, choose **Users** from the left-hand navigation menu. 1. You can either select an existing user or add a new user. To add a new user, click **Add user**. 1. Give the user a **User name** and select the **Programmatic access** access type. Click **Next: Permissions**. 1. Choose the **Attach existing policies directly** option. Search for **AWSApplicationMigrationVCenterClientPolicy** and **AWSApplicationMigrationAgentPolicy**. Select the policies and click **Next: Tags.** 1. Add tags if you wish to use them and then click **Next: Review.** 1. Review the information. Ensure that the **Programmatic access** type is selected and that the correct policy is attached to the user. Choose **Create user**. 1. A confirmation message appears and you can see the **Access key ID** and **Secret access key** that you need in order to install the AWS Replication Agent on your source servers. To save this information as .csv file, click **Download .csv**. You can also access this information and re-generate your security credentials by navigating to **IM > Users > Your user**. Open the **Security credentials** tab and scroll down to **Access keys**. Here you can manage your access keys (create, delete, and more). # Installing the Application Migration Service vCenter Client The first step to deploying the agentless solution is installing the Application Migration Service vCenter Client on your vCenter environment. **Note** If you have multiple vCenter environments, you need to install multiple clients. You may not have more than one Application Migration Service vCenter Client installed per AWS account. If you have multiple vCenter environments, you can either use a different AWS account for each environment or you can migrate your VMs serially, environment by environment, into the same AWS account. After the Application Migration Service vCenter Client has been installed, it discovers all of the VMs in your vCenter environment and add them to Application Migration Service. ## Application Migration Service vCenter Client requirements Ensure that you review the notes below prior to installing the Application Migration Service vCenter Client. Once you have read the notes, proceed to [install the client](client-installation-instructions-mgn.md). ### vCenter Client requirements + You must install the Application Migration Service vCenter Client on a VM that has outbound network connectivity to the AWS Application Migration Service API endpoints and outbound network connectivity to the vCenter endpoint. Customers who want to use PrivateLink can use VPN or AWS Direct Connect to connect to AWS. + The Application Migration Service vCenter Client currently only supports VirtualDiskFlatVer2BackingInfo VMDK on CBT. + You must log in to your Broadcomm account and download VDDK 7.0.3.3 to the VM on which the Application Migration Service vCenter Client is installed. VDDK 7.0.3.3 must be used, regardless of the vCenter version used. + The Application Migration Service vCenter Client requires these vCenter user permissions for agentless deployment. It is a best practice to create a dedicated role with these permissions and a dedicated user group with which the role is associated. Every new user created for the Application Migration Service vCenter Client needs to be a member of that group in order to obtain the required permissions. The vCenter predefined role: “ Consolidated Backup user (sample) ” provides most of these permissions. If that role is used, the **Toggle disk change tracking** permission must be provided.. + Change configuration + Acquire disk lease + Toggle disk change tracking + Provisioning + Allow read-only disk access + Allow virtual machine download + Snapshot management + Create snapshot + Remove snapshot + The VM on which the Application Migration Service vCenter Client is installed should meet these RAM, CPU, and memory requirements: + Minimal requirements (these requirements allow the replication of up to 5 servers in parallel) – 2 GiB RAM, 1 core, 10 GiB of free disk space + Optional performance requirements (these requirements allow the replication of the maximum number of 50 servers in parallel) – 16 GiB RAM, 8 cores, 10 GiB of free disk space + VMs that are being replicated into AWS should have at least 2 GiB of free disk space. + The VM on which the Application Migration Service vCenter Client is installed should not allow any incoming (ingress) traffic. + The VM on which the Application Migration Service vCenter Client is installed should only allow outgoing traffic as following: + Egress TCP on the port on which the vCenter API is ran. + Egress TCP on port 443 for communication with the Application Migration Service API. + Egress TCP on port 1500 – for the replication server. + Patching of guest OS running AWS vCenter client should be handled by the customer as part of shared responsibility. + IAM credentials used by the vCenter Client should be rotated on a regular schedule. Learn more about how to rotate access keys for IAM users in [this IAM blog post](https://aws.amazon.com/blogs/security/how-to-rotate-access-keys-for-iam-users/). IAM credentials can be regenerated by reinstalling the AWS Replication Agent. + The VM that hosts the Application Migration Service vCenter Client should only be used for client hosting and should not be used for any other purposes. + Only a trusted administrator should have access to the VM on which the Application Migration Service vCenter Client is installed. + The Application Migration Service vCenter Client should be located in an isolated and dedicated network and considered a sensitive segment. + You can deactivate the vCenter Client auto-update mechanism by running this command: `touch /var/lib/aws-vcenter-client/.disable_auto_updates` Once auto-updates are deactivated, you need to reinstall the client to perform a manual update. If you deactivate the auto-update mechanism, you are responsible for ensuring that all security updates are performed on the client. After a manual update, you should validate the new hash against the [installer hash](client-installation-instructions-mgn.md). ### vCenter Client installer notes + The Application Migration Service vCenter Client installer only supports vCenter 6.7, 7.0 and 8.0. + The Application Migration Service vCenter Client can be installed on these 64 bit Linux versions: + Ubuntu 18.x\$1 (64 bit) - 22.04 + Amazon Linux 2 + RHEL 8.x + If you are using a RHEL 8.x environment, ensure that you run the `sudo yum install python3` command to install python prior to launching the client installer. + These flags are used by the installer: + usage: aws-vcenter-client-installer-init.py [-h] + [--aws-access-key-id AWS\$1ACCESS\$1KEY\$1ID] + [--aws-access-key-id AWS\$1ACCESS\$1KEY\$1ID] + [--aws-secret-access-key AWS\$1SECRET\$1ACCESS\$1KEY] + [--region REGION] + [--endpoint ENDPOINT] + [--s3-endpoint S3\$1ENDPOINT] + [--vcenter-host VCENTER\$1HOST] + [--vcenter-port VCENTER\$1PORT] + [--vcenter-user VCENTER\$1USER] + [--vcenter-password VCENTER\$1PASSWORD] + [--vcenter-ca-path VCENTER\$1CA\$1PATH] + [--vddk-path VDDK\$1PATH] + [--vcenter-client-tags KEY=VALUE [KEY=VALUE ...]] + [--source-server-tags KEY=VALUE [KEY=VALUE ...]] + [--disable-ssl-cert-validation] + [--no-prompt] + Use this flag for an unattended installation. If you are using this flag, you must also use the --force-delete-existing client flag. [--force-delete-existing-client] + Use this flag to delete an existing version of the vCenter Client from your VM. You must use this flag if you've previously installed the vCenter Client on the VM. If you use the --no-prompt flag, you must also use this flag. [--version] Optional arguments: -h, --help show this help message and exit ### vCenter environment requirements + AWS Application Migration Service supports VM hardware version 7 and higher with CBT activated. Ensure that you upgrade any VMs you have to hardware version 7 or higher. Ensure that CBT support is activated in your vSphere deployment. Application Migration Service activates CBT on replicating VMs. You can deactivate CBT after cutover. + The VM being replicated into Application Migration Service must not contain any existing VMware snapshots. + Once added to Application Migration Service, snapshot-based replication creates snapshots on the replicated VM, which may result in slower disk performance. + VMs with independent disks, Raw Device Mappings (RDM), or direct-attach disks (iSCSI, NBD) are not supported for replication into Application Migration Service. + The VM being replicated into Application Migration Service can be either stopped or running. Changing the VM state during data replication does not affect data replication and causes no data corruption. # Application Migration Service vCenter Client installation instructions To install the Application Migration Service vCenter Client, follow these steps: 1. Download the Application Migration Service vCenter Client installer onto a VM within your vCenter environment. You can download the client from this URL: `https://aws-application-migration-service-(region).s3.(region).amazonaws.com/latest/vcenter-client/linux/aws-vcenter-client-installer-init.py` Replace `(region)` with the AWS Region into which you are replicating. This is an example of the installer link for us-east-1: `https://aws-application-migration-service-us-east-1.s3.us-east-1.amazonaws.com/latest/vcenter-client/linux/aws-vcenter-client-installer-init.py` If you need to validate the installer hash, the correct hash can be found here: `https://aws-application-migration-service-hashes-(region).s3.(region).amazonaws.com/latest/vcenter-client/linux/aws-vcenter-client-installer-init.py.sha512 ` This is an example of the installer hash link for us-east-1: `https://aws-application-migration-service-hashes-us-east-1.s3.us-east-1.amazonaws.com/latest/vcenter-client/linux/aws-vcenter-client-installer-init.py.sha512` 1. In command prompt, navigate to the directory where you downloaded the Application Migration Service vCenter Client installer and run the installer with this command: `sudo python3 aws-vcenter-client-installer-init.py` ![\[Command prompt showing execution of Python script for AWS vCenter Client installer.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agentless3.png) 1. The installer prompts you for your credentials, enter the required info in each field and then press **Enter**: ![\[Terminal window displaying AWS access key details and endpoint information.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agentless4.png) + AWS Access Key ID – Enter the AWS Access Key ID you generated in the previous section. + AWS Secret Access Key – Enter the AWS Secret Access Key you generated in the previous section. + AWS Region name – The AWS Region of your account (for example, eu-west-1). + The Private Link endpoint for AWS Application Migration Service (optional, leave blank if not using Private Link). + The VPC endpoint for Amazon S3 (optional, leave blank if not using a VPC endpoint). 1. The installer then prompts you to enter your vCenter information, enter the required info in each field and then press **Enter**: ![\[Command line interface prompting for vCenter connection details including IP, port, and credentials.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agentless5.png) + vCenter IP or hostname + vCenter port (press Enter to use the default TCP Port 443) + vCenter username + vCenter password + Path to vCenter root CA certificate (optional) - To use SSL certificate validation, download the certificates from `https:///certs/download.zip` ( example: `wget https:///certs/download.zip --no-check-certificate`) then enter the path of the certificate (example: `/usr/local/src/lin/f7f2bd6e.0)`). Otherwise, press **Enter** to deactivate SSL certificate validation. **Note** The certificate must be located in a file that's readable to the vCenter client user, such as a shared directory. If the certificate is not located in a shared directory, you see a permission error in the logs (Error 13). To use a certificate in your vCenter environment, you must setup a connection using a hostname. Using an IP does not work with a certificate. It's a security best practice to use certificates. Customers that do not use certificated authentication are responsible for any security issues that may arise. + Path to VDDK tarball - Provide the path to the VDDK tarball that you previously downloaded onto the VM. (example: `path/to/VMware-vix-disklib-7.0.3-21933544.x86_64.tar.gz`). You can download VDDK tarball from your Broadcomm account. + Resource tags for the AWS vCenter client (optional) - Use this format for tagging: KEY=VALUE [KEY=VALUE ...] add resource tags to the AWS vCenter client; use a space to separate each tag (e.g., --vcenter-client-tags tag1=val1 tag2=val2 tag3=val3) + Resource tags for source servers to be discovered by the AWS vCenter client (optional) - Use this format for tagging: KEY=VALUE [KEY=VALUE ...] add resource tags to the source servers added by discovery; use a space to separate each tag (e.g., --vcenter-client-tags tag1=val1 tag2=val2 tag3=val3) 1. The installer downloads and installs the AWS vCenter client and registers it with AWS Application Migration Service. ![\[Terminal output showing successful download and installation of AWS vCenter client.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/agentless6.png) 1. Once the AWS vCenter client has been installed, all of the VMs in your vCenter are added to AWS Application Migration Service. The VMs are added in the DISCOVERED state. **Note** If you have a significant number of VMs in your vCenter environment, it may take some time for all of the VMs to become visible in the Application Migration Service console. The Application Migration Service vCenter Appliance is excluded from the discovered servers list. You can configure transparent proxy either by using an environment variable prior to the installation (Linux and Windows), or by using the --proxy-address flag in the Linux installer: + Using the installer: ./aws-vcenter-client-installer-init.py --proxy-address http://PROXY:PORT/ + Using environment variable: export https\$1proxy=http://PROXY:PORT/; ./aws-vcenter-client-installer-init.py Make sure the proxy has a trailing forward slash. # Replicating servers from vCenter to AWS Once you have successfully installed the AWS vCenter client, all of your vCenter VMs are added to Application Migration Service in the DISCOVERED state. The DISCOVERED state means that the VM has not been replicated to AWS. **Note** VMware only sends data for up to 50 servers in parallel. Replicating more than 50 servers at once causes the rest to be queued and results in a longer wait. By default, the Application Migration Service console only shows active servers. You can tell which servers are being shown by looking at the filtering box under the main **Source servers** title. To see your discovered non-replicating servers that have been added from vCenter, open the filtering menu and choose **Discovered source servers**. You now see all of your non-replicating DISCOVERED VMs. To replicate one or more VMs into AWS, select the box to the left of each VM name, choose the **Replication** menu, and then choose **Start data replication**. Choose **Start** on the **Start data replication for x servers** dialog. The Application Migration Service console indicates that data replication has started. To view the data replication progress, open the filtering menu and return to the default **Active source servers** view. You now only see your replicating source servers. You can follow the launch process on the main **Source servers** view. Once the VM has reached the **Ready for testing** state under **Migration lifecycle**, you can continue to [launch test and cutover instances](launching-test-servers.md) and perform all other regular Application Migration Service operations on the server. # Updating the vCenter or AWS Credentials Users who want to change the vCenter or AWS credentials used by the Application Migration Service appliance should follow these steps. This change requires root privileges on the appliance: 1. In the command prompt, navigate to the aws-vcenter-client directory: `cd /var/lib/aws-vcenter-client/1.1.8/` 1. Run the vCenter configuration update tool with this command: `sudo ./vcenter_configuration_update` 1. When running the vCenter configuration update tool, you are prompted to provide the necessary credentials. Follow these steps to update the credentials. Provide the required info in each field and then press Enter: + New vCenter username (--new-vcenter-username) + New vCenter password (--new-vcenter-password) + New AWS Secret Key ID (--new-aws-access-key-id) + New AWS Secret Access Key (--new-aws-secret-access-key) + New path to the CA (optional) (--new-ca-path) 1. If you do not provide the `--new-ca-path` flag, the tool first asks if you want to update the CA path. If you answer yes, it prompts you for the new CA path. If you answer no, the tool uses the CA path from the previous configuration. The tool verifies the new vCenter and AWS credentials by attempting to connect to vCenter and Application Migration Service using them. 1. Upon successful connection to vCenter and Application Migration Service, the tool saves the new credentials and restart the necessary services. 1. In case of failure to connect to vCenter or Application Migration Service, the new credentials are not stored, and the previous configuration is retained. This error message is displayed: `Failed to connect to the vCenter endpoint or MGN using the new connection details. The configuration changes will not be applied.` # Differentiating agentless and agent-based servers You can differentiate an agentless vCenter VM that's replicating through snapshot shipping and an agent-based server (from any source infrastructure) through several ways: 1. On the **Source servers** page, under the **Replication type** column, the Application Migration Service console identifies the replication type, whether it is through **Snapshot shipping** (agentless) or **Agent based**. 1. In the server details view, under the **Migration dashboard**, agentless servers that are replicated through snapshot shipping have an additional **Lifecycle** step – **Not started.** 1. Similarly, in the server details view, under the **Migration dashboard**, the **Data replication status** box shows the **Replication type** as **Snapshot shipping**. # Manage source servers The **Source servers** page lists all of the source servers that have been added to AWS Application Migration Service (AWS MGN). The **Source servers** page allows you to manage your source servers and perform a variety of commands for one or more servers (such as controlling replication and launching test and cutover instances). The **Source servers** page is the main page of AWS MGN console and you will most likely interact with AWS Application Migration Service predominantly through this page. ## 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 table displays **Active source servers** by default. You can use the dropdown menu above the first row to choose to display: + **Agentless discovered servers** - servers discovered by the agentless replication process, which are not yet replicating. + **Imported servers** - servers whose information was imported into MGN, but an agent is not yet installed on them. + **Archived source servers** - servers whose migration has completed, and the users archived their data. 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 a server is selected, you can interact with the server through the **Actions**, **Replication**, and **Test and cutover** menus. Selected servers are highlighted. + **Source server name** – This column shows the unique server name for each source server. + **Alerts** – This column shows whether any alerts exist for the server. + **No indication** – a healthy server for which a test or cutover instance has not been launched. + **Launched** – a healthy server for which a test of cutover instance has been launched. + **A clock icon with a warning message** – a server that is experiencing a temporary issue such as lag or backlog + **A red x and message** – a server that is experiencing significant issues, such as a stall. + **Replication type** – This column identifies whether the server is being replicated through the default **Agent based** replication or through **Snapshot shipping**. [Learn more about agentless based snapshot shipping replication for vCenter.](agentless-mgn.md) + **Migration lifecycle** – This column shows the migration lifecycle state for each source server. This way you can easily know which lifecycle step the server is undergoing. Migration lifecycle steps include these: [[Learn more about Migration lifecycle steps](migration-dashboard.md#lifecycle)](migration-dashboard.md#initiation). + **Not ready** + **Ready for testing** + **Test in progress** + **Ready for cutover** + **Cutover in progress** + **Cutover complete** + **Disconnected** + **Data replication status** – This column shows the current status of data replication for the server. The information presented in this column changes based on the server's Migration lifecycle state and whether the server is experiencing any issues. This column shows a variety of information, including: + **Not Started** – Data replication has not started. + **Paused** – Data replication has been paused. + **Healthy** – The server is healthy and ready for Test or Cutover instance launch. + **Done** – The server has been successfully cutover and data replication has been stopped as a result. + **Percentage complete** – The percentage of the server's storage that was successfully replicated if the server is undergoing initial sync or a rescan. + **Lag** – Whether server is experiencing any lag. If it is; the lag time is indicated. + **Backlog** – Whether there is any backlog on the server (in MiB). + **Last snapshot** – This column shows the time the last consistent snapshot was taken of the source server. Servers that are still in the initial sync process and those that have been disconnected do not show any info in this field. Healthy servers shows a recent snapshot. Unhealthy servers' last snapshot indicates the last time they were healthy. + **Next step** – This column shows the next step that needs to be undertaken in order to successfully complete a cutover for the server. The information presented in this column changes based on the server's Migration lifecycle state and whether the server is experiencing any issues. This column shows a variety of next steps, including: + **Wait for initial sync to complete** – Data replication is initiating for the server. Wait for the initial sync process to complete. + **Start data replication** – Data replication has not been started or is paused. + **Launch test instance** – The server is ready to launch a test instance. + **Complete testing and mark as 'ready for cutover'** – The server has launched a Test instance that needs to be reverted or finalized. + **Launch cutover instance** – The server had a Test instance launched and finalized and now is ready to launch a cutover instance. + **Finalize cutover** – The server has launched a cutover instance that needs to be finalized. + **Terminate launched instance, Launch cutover instance** – The server is ready for cutover. Terminate the launched Test instance and launch a cutover instance. + **Resolve cause of stalled data replication** – The server is experiencing significant issues such as a stall that need to be addressed. + **Wait for lag to disappear, then X.** – The server is experiencing a temporary lag. Wait for the lag to disappear and then perform the indicated action. + **Mark as archived** – The server has been successfully cut over and can now be archived. **Topics** + [ ## Interacting with the source servers page ](#interracting) + [ # Add a source server ](add-server-server-page.md) + [ # Manage data replication ](server-replication-main.md) + [ # Manage test and cutover instances ](server-test-cutover-main.md) + [ # Source server migration metrics ](source-server-migration-metrics.md) + [ # Filtering the source servers list ](list-filtering.md) # Add a source server To add a server, simply click **Add server**. To run a variety of commands on your source servers, select one or more servers and choose the **Actions**, **Replication**, or **Test and cutover** menu. The **Add servers** prompt opens, allowing you to create a custom installation command by taking these steps: + 1. Select your operating system. The installation command is different for Windows and Linux **Note** If you want to install the AWS Replication Agent on a legacy Windows OS (Windows Server 2003, Windows Server 2008 or Windows Server 2008 R2), you must choose the **Legacy OS: Windows Server 2003 or Windows Server 2008** box. This downloads a unique version of the AWS Replication Agent installer that is only valid for legacy Windows OSs (`AwsReplicationWindowsLegacyInstaller.exe`). **Do not** use this installer file to install the agent on any other OS types. 1. Select your replication preferences for the source server. The selected preferences are added as installation prompts to the custom installation command that is generated by this form. Choose the **Replicate all disks** option to replicate all of the disks of the source server. This is the default option. This option adds the `--no-prompt` prompt to the installation command. Select the **Choose which disks to replicate** option to choose which specific disks you want to replicate. You are prompted to select which disks to replicate during agent installation. 1. Enter the credentials [you previously generated for AWS Replication Agent installation](credentials.md). The form does not send the secret, but does add it to the installation command. 1. If you are adding a Windows source server to AWS MGN, download the installer onto the source server. The installer is downloaded from the AWS Region of your account. If you're adding a Linux source server, skip this step. 1. Copy the generated custom installation command and either input it into the command line on your source server. Proceed with [AWS Replication Agent installation as instructed in the documentation](agent-installation.md). To run a variety of commands on your source servers, select one or more servers and choose the **Actions**, **Replication**, or **Test and cutover** menu. ## Actions menu The **Actions** menu allows you to perform these actions: + **View server details** – Choose this option to see the server details view for the selected server. This option is only available when a single server is selected. + **Add server to application** – Choose this option to easily add servers to an application. + **Disconnect from service** – Choose this option to disconnect the selected server from Application Migration Service and AWS. This option should be used when data replication is complete. 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. If you need to restart data replication for this server, you need to reinstall the agent. This action does not affect any test or cutover instances that have been launched for this source server, but you can no longer identify which source servers your Amazon EC2 instances correspond to. + **Mark as archived** – Choose this option in order to archive the server. You should only archive servers for which you have already performed a cutover. Archived servers are removed from the main **Source servers** page, but can still be accessed through filtering options. On the **Archive X servers** dialog, select **Archive**. To see your archived servers, open the **Preferences** menu by choosing the gear button. Select the **Show only archived servers** option and click **Confirm**. You are now able to see all of your archived servers. Unselect this option to see your non-archived servers. # Manage data replication You can manage data replication for the source server through these actions on the **Replication** drop-down menu: + **Start data replication** – Restarts data replication for a source server on which data replication has been stopped. If you are using agent-based replication you don't necessarily have to reinstall the agent. + **Stop data replication** – Stops data replication for a source server. Stopping the replication stops billing, deletes existing snapshots and EBS volumes, and terminates replication servers. Configuration is retained, and if you are using agent-based replication the agent is not uninstalled. + **Pause data replication** – Pauses data replication for a source server. Pausing the replication does not stop billing or delete existing snapshots or EBS volumes. Replication servers are not terminated and if you are using agent-based replication the agent is not uninstalled from the source server. + **Resume data replication** – Resume data replication for a paused source server. This syncs any changes since the last synchronization and completes the data replication flow. Choose **Edit** in the **Replication settings **section to access the ** Edit Replication Settings** page, where you can edit the settings for the selected source server. [Learn more about editing replication settings.](replication-settings-template.md) # Manage test and cutover instances The **Test and cutover** menu allows you to manage your test and cutover instances. For a more in-depth step-by-step guide to launching test and cutover instances, see the [Launching test and cutover instances documentation](launching-test-servers.md). + **Launch test instances** – Choose this option to launch a test instance for this server. When the **Launch test instances for X** servers dialog appears, cick **Launch** to begin the test. The AWS Application Migration Service console indicates **1 launch job complete** after the test has been completed successfully. + **Mark as "Ready for cutover"** – Use this option to finalize testing for this server after you have completed all of the necessary tests in preparation for cutover. When the **Mark X servers as "Ready for cutover"** dialog appears, select whether you want to terminate the launched instances used for testing. We recommend that you terminate these instances, as you will be charged for them even though you no longer need them. Check the **Yes, terminate launched instances (recommended)** box and choose **Continue**. The AWS Application Migration Service console indicates that testing has been finalized. The selected source servers' **Migration lifecycle** column shows the **Ready for cutover** status and the launched Test instances are deleted if that option was selected. + **Revert to "ready for testing"** – Choose this option to revert a finalized test for this server if you want to run further tests prior to initiating a cutover. The **Revert testing for X servers** dialog appears. Select whether you want to terminate the launched instances used for testing. We recommend that you terminate these instances, as you will be charged for them even though you no longer need them. Check the **Yes, terminate launched instances (recommended)** box and choose **Revert**. The AWS Application Migration Service console indicates that testing has been reverted. The selected source servers' **Migration lifecycle** column shows the **Ready for testing** status and the launched Test instances are deleted if that option was selected. + **Launch cutover instances** – Choose this option to launch a cutover instance for this server after you have finalized all of your testing and are ready to initiate a cutover. The **Launch cutover instances for X** **servers** dialog appears. Choose **Launch** to begin the cutover. The AWS Application Migration Service console indicates **1 launch job complete** after the cutover has been completed successfully. This changes your source servers' **Migration lifecycle** status to **Cutover in progress**, indicating that the cutover is in progress but has not yet been finalized. + **Finalize cutover** – Choose this option to finalize the cutover for this server after you have successfully performed a cutover. This changes your source servers' **Migration lifecycle** status to **Cutover complete**, indicating that the cutover is complete and that the migration has been performed successfully. In addition, this stops data replication and cause all replicated data to be discarded. All AWS resources used for data replication are terminated. The **Finalize cutover for X servers** dialog appears. Choose **Finalize**. The AWS Application Migration Service console indicates **X servers cutover. Data replication has been stopped for servers** once the cutover has been completed successfully. The AWS Application Migration Service console automatically stops data replication for the cutover source servers to save resource costs. The selected source servers' **Migration lifecycle** column shows the **Cutover** status, the **Data replication** column shows **Disconnected** and the **Next step** column states **Mark as archived**. The source servers have now been successfully migrated into AWS and can be archived. **Note** This action does not uninstall the AWS Replication Agent from the source server. Use the **Disconnect from service** option under the **Actions** menu when you have completed the migration and want to uninstall the agent from your source server. + **Revert to "ready for cutover"** – Choose this option to revert a finalized cutover for this server if you encounter any issues or want to reverse the cutover for any reason. This revert syour source servers' **Migration lifecycle** to the **Ready for cutover** status, indicating that these servers have not undergone cutover. The **Revert cutover for X servers** dialog appears. Click **Revert**. + **Edit launch settings** – Use this option to edit the launch settings for this server. You are redirected to the **Edit launch settings** page. [Learn more about launch settings.](launching-target-servers.md) + **Edit post-launch settings** – Use this option to edit the post-launch settings for the selected source server or group of source servers. [Learn more about post-launch settings.](source-post-launch-settings.md) + **Terminate launched instance** – Choose this option if you want to delete your test or cutover instance for any reason at any time. It can only be selected for a server that has a launched test or cutover instance. When the **Terminate launched instance** dialog appears, click **Terminate**. # Source server migration metrics The source server migration metrics present an aggregated overview of your source servers, focused on three topics: **Alerts**, **Data replication status**, and **Migration status**. ## Understand source server alerts The source server **Alerts** migration metric presents an aggregated overview of the application associated servers alerts. You can look up an individual source server's **Alerts** in the **Source servers** table at the bottom of the page. + A healthy server for which a test or cutover instance has not been launched displays a **Healthy** status. + A healthy server for which a test of cutover instance has been launched displays a **Healthy** status. + A server that is experiencing a temporary issue such as lag or backlog displays a **Lagging** status. + A server that is experiencing significant issues, such as a stall, displays a **Stalled** status. ## Understand data replication status The source server **Data replication status** migration metric presents an aggregated overview of the your source servers' data replication status. You can look up an individual source server's **Data replication status** status in the **Source servers** table at the bottom of the page. Source server **Data replication status** can have one of these values: + **Transferring snapshot** + **Initial sync** + **Finalizing sync** + **Lagging** + **Healthy** + **Stalled** + **Rescanning** + **Not started** + **Initiating** + **Creating snapshot** + **Paused** + **Disconnected** ## Understand the migration lifecycle metric The source server **Migration lifecycle** metric shows an aggregated overview of your source servers' migration lifecycle. You can look up an individual source server's **Migration lifecycle** status in the **Source servers** table at the bottom of the page. Source server **Migration lifecycle** can have one of these values: + **Stopped** + **Not ready** + **Ready for testing** + **Test in progress** + **Ready for cutover** + **Cutover in progress** + **Cutover complete** + **Disconnected** + **Discovered** # Filtering the source servers list You can customize the **Source servers** page through filtering. Filtering allows you to easily filter your servers by one or multiple properties. Click within the **Filter servers** field and choose the filtering property from the **Properties** menu. You can filter by a variety of properties, including: + Alerts – Filter by specific alert (lagging, stalled, launched). + Hostname – Filter by a specific hostname or a specific string of characters. + Migration lifecycle – Filter by the migration lifecycle state. + Data replication status – Filter by the data replication status. + Next step – Filter by next step. + SourceServerID – Filter by specific source server ID or string. + Tags – Filter by tags. Relevant specific tag values appear under the **Tags** category. Choose the value to filter by. You can filter by multiple properties at once in order to narrow down your results. Choose **Clear filters** to clear the current filtering properties selected. # Access details on a source server Server details You can access the server details view by clicking on the **Source server name** of any server on the **Source servers** page. 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**. The server details view shows information and options for an individual server. Here, you can fully control and monitor the individual server. You can also perform a variety of actions, control replication, and launch test and cutover instances for the individual server from the server details view. The **Next actions** box serves as a helpful guide to the state of the server and the next steps you need to take in order to complete the migration process for the server. The server details view is divided into several tabs, including: + Migration dashboard + Server info + Tags + Disk settings + Replication settings + Launch settings **Topics** + [ # Monitor the server in the migration lifecycle ](migration-dashboard.md) + [ # Review source server information ](source-server-info.md) + [ # Add or remove tags assigned to source servers ](Cirrus_tags.md) + [ # Review disk settings for source servers ](disk-settings.md) + [ # Change staging disk type ](staging-disk.md) + [ # Edit replication settings for a source server ](replication-settings.md) + [ # Review launch settings for a source server ](launch-settings-source.md) + [ # Review post-launch settings ](source-post-launch-settings.md) + [ # Editing the post-launch settings ](source-post-launch-settings-editing.md) + [ # Activating and deactivating post-launch actions ](source-post-launch-settings-actions.md) + [ # Deploying post-launch actions ](source-post-launch-settings-deployment.md) # Monitor the server in the migration lifecycle Migration dashboard The **Migration dashboard** tab allows you to monitor the server in relation to the migration lifecycle. Here, you can see the lifecycle state the source server is currently on, a detailed view of the data replication status, and any events that the source server has undergone (in AWS CloudTrail). You can use the Migration dashboard to monitor the status of your source server and to troubleshoot migration and data replication issues. ## Understand lifecycle states The **Lifecycle** view shows the current state of each server within the migration lifecycle. Lifecycle states include: + **Not ready** – The server is undergoing the Initial Sync process and is not yet ready for testing. Data replication can only commence once all of the Initial Sync steps have been completed. + **Ready for testing** – The server has been successfully added to AWS Application Migration Service and data replication has started. Test or cutover instances can now be launched for this server. + **Test in progress** – A test instance is currently being launched for this server. + **Ready for cutover** – This server has been tested and is now ready for a cutover instance to be launched. + **Cutover in progress** – A cutover instance is currently being launched for this server. + **Cutover complete** – This server has been cutover. All of the data on this server has been migrated to the cutover instance. The lifecycle always displays the **Launch status**, **Last test**, and **Cutover status** for each server that has undergone these stages. **Topics** + [ ### Not ready ](#not-ready) + [ ### Ready for testing ](#ready-for-testing-1) + [ ### Test in progress ](#test-in-progress) + [ ### Ready for cutover ](#ready-for-cutover1) + [ ### Cutover in progress ](#cutover-in-progress) + [ ### Cutover complete ](#cutover-stage) ### Not ready The **Not ready** lifecycle state represents several possible scenarios: **Topics** + [ #### Server undergoing initial sync ](#initiation) + [ #### Unable to complete initiation ](#unable-to-initiate) #### Server undergoing initial sync A source server that has been added to AWS Application Migration Service automatically begins the initial sync process after AWS Replication Agent installation. Data replication can only commence after all of the initial sync steps have been completed. The server is in the **Not ready** lifecycle state until initial sync has been successfully completed. Initial sync steps include: + Initiation + Creating firewall rules + Creating replication server + Booting replication server + Resolving Service Manager address + Authenticating with the Service Manager + Downloading replication software + Creating staging disks + Pairing replication server with agent + Establishing communication between AWS Replication Agent and replication server + Sync (0% to 100%) + Flush backlog (if any) + Create first launchable snapshot You can review the overall progress of the Initial Sync process under the** Data replication status** view. It provides the percentage of completion, the time left until initial sync is finished, and whether there are any issues (such as a stall). You can tell that a server has successfully completed the initial sync process through several indicators on the main **Source servers** page as well as on the **Migration dashboard** tab for an individual server. On the main **Source servers** page, a newly added server that has completed initial sync for the first time shows **Ready for testing** under the **Migration lifecycle** column and **Healthy** under the **Data replication status** column. On the individual server view, under the **Migration dashboard** tab, the **Lifecycle** section shows the **Ready for testing** status. The **Data replication status** section shows the **Healthy** status. **Note** Servers automatically undergo initial sync every time there is a network disconnect. #### Unable to complete initiation The server is in the **Not ready** Lifecycle state until Initial Sync has been successfully completed. If the Initial Sync process is stalled for any reason, the **Data replication status** section indicates that replication has stalled. Scroll down to the Replication initiation steps to see the step on which the error occurred. The step on which initial sync failed is marked with a red "x". You must fix the indicated issue before the initial sync process can continue. You are not able to migrate your server and the server remains in the **Not ready** state until the issue is resolved. Each step has troubleshooting methods. ### Ready for testing Once the server has successfully completed the Initial Sync process, it enters the **Ready for testing** lifecycle state. The **Data replication status** box shows a **Healthy** state, indicating that the server is healthy. You can now launch a test instance for this server. The server stays in the **Ready for testing** lifecycle state until you launch a Test instance for the server. ### Test in progress Once you have launched a Test instance for your server, the migration dashboard shows the **Test in progress** lifecycle state. Within the **Lifecycle** box, you can review the **Launch status** and **Last test** information fields for the test instance. + The **Launch status** field shows the time of the test instance launch. While the Testing instance is being launched, the **Launch status** field shows **Waiting**. + Once the test instance has been launched, the Launch status shows **Launched**. Wait for the instance to boot and then choose **View in EC2 console** link to open the EC2 console in a new tab, in order to view and monitor your launched test instance. + The AWS EC2 console opens in a new tab and automatically searches for and displays your test instance. + The **Last test** field shows the date of the last test. To review the test launch details, click **Job ID**, which opens the job within the **Launch History** page in a new tab. + On the main **Source servers** page, the **Migration lifecycle** column shows **Ready for testing** and the **Next step** column shows **Launch test instance**. + The server stays in the **Test in progress** Lifecycle state until you finalize your testing and mark the server as **Ready for cutover**. You can use these indicators to verify that your test instance was successfully launched:: + On the **Server Details > Lifecycle** pane, the Launch status states **Launched**. + On the main **Source servers** page, the **Alerts** column shows the **Launched** status. ### Ready for cutover After you have finalized your testing, the Migration dashboard shows the **Ready for cutover** lifecycle state. + The **Launch status** field shows the time of the last test instance launch. Click on the **View in EC2 console** link to open the EC2 console in a new tab in order to view and monitor your launched Test instance. + The **Last test** field shows the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This opens the relevant Job. + The **Cutover** field shows the date of the last cutover instance launch, if applicable. You can review the cutover launch details by clicking on the **Job ID**. This opens the relevant Job. + On the **Source servers** page, the **Migration lifecycle** column shows **Ready for cutover** and the** Next step** column shows **Terminate test instance; Launch cutover instance**. The server stays in the **Ready for cutover** Lifecycle state until you launch a cutover instance. ### Cutover in progress Once you have launched a cutover instance for your server, the Migration dashboard shows the **Cutover in progress** Lifecycle state. + The **Launch status** field shows the last time of cutover launch. Click on the **View in EC2 console** link to open the EC2 console in a new tab in order to view and monitor your launched cutover instance. + The **Last test** field shows the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This opens the Job. + The **Cutover** field shows the date of the last cutover instance launch. You can review the cutover launch details by clicking on the **Job ID**. This opens the Job. + On the **Source servers** page, the **Migration lifecycle** column shows **Cutover in progress** and the **Next step** column shows **Complete the cutover**. The server stays in the **Cutover in progress** Lifecycle state until you complete the cutover. ### Cutover complete Once you have completed your cutover instance launch for your server, the Migration dashboard shows the **Cutover complete** lifecycle state. This is the final state in the migration lifecycle. This state indicates that you have successfully migrated your source server to AWS. + The **Launch status** field shows **Launched**. Click on the **View in EC2 console** link to open the EC2 console in a new tab in order to view and monitor your launched cutover instance. + The **Last test** field shows the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This opens the Job. + The **Cutover** field shows the date you finalized your Cutover instance launch. You can review the cutover launch details by clicking on the **Job ID**. This opens the Job. + The AWS Application Migration Service console automatically stops data replication for the source servers that were cutover in order to save resource costs. + On the **Source servers** page, the selected source servers' **Migration lifecycle** column shows the **Cutover complete** status, the **Data replication status** column shows **Disconnected** and the **Next step** column shows **Mark as archived**. The lifecycle also shows the status of any post-launch actions for the server. [Learn more about post-launch actions.](source-post-launch-settings.md) ## Understand data replication states 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** – The percentage of the server's storage that was rescanned (in the event of a rescan) + **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 Application Migration Service. + **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 the source are continuously being replicated (data is flowing). + **Rescan**: an event happened that forced the agent on the external server to rescan all of the blocks on all of the replicated disks. This is similar to the initial sync but faster because only changed blocks are copied. A rescan progress bar is displayed. + **Stalled**: data is not flowing. You may need to intervene. When stalled, either the initial sync never completes, or the difference between the state of the replicated data and that of the source server continues to grow. When the state is stalled, then the replication initiation checklist is shown and indicates where the error occurred that caused the stall. 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 will be 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 shows a **Healthy** status. If there are initialization, replication, or connectivity errors, the **Data replication status** section shows 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**. ## Understand the state of post-launch actions The **Post-launch actions** view shows the current execution status of post-launch actions. The status includes: + Name – the name of the action is a link to the detailed execution status in the [AWS Systems Manager](https://aws.amazon.com/systems-manager/) console. + Execution status – provides the current action status. + Start time – the start time of the execution of the action script. This column is empty for actions that have not yet started execution. + End time – the end time of the execution of the action script. This column is empty for actions that have not yet completed execution. + Details – error messages are shown in this column. + Link – used by the “DR after migration” action. Provides a link to the replicated server in the [AWS Elastic Disaster Recovery](https://aws.amazon.com/disaster-recovery/) console. ## Review events and metrics in AWS CloudTrail Events and metrics You can review AWS Application Migration Service events and metrics in AWS CloudTrail. Click on **View CloudTrail Event** History to openAWS CloudTrail in a new tab. Learn more about [monitoring AWS MGN.](monitoring-overview.md) Learn more about AWS CloudTrail events in the [AWS CloudTrail user guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html). ## Understand server actions and replication control Server actions and replication control You can perform a variety of actions, control data replication, and manage your testing and cutover for an individual server from the server details view. **Topics** + [ ### Actions menu ](#server-actions) + [ ### Replication menu ](#server-replication) + [ ### Test and cutover menu ](#server-test-cutover) + [ ### Alerts and errors ](#server-test-cutover-alert) ### Actions menu The **Actions** menu allows you to perform these actions: + **Add servers** – Choosing the **Add servers** option opens the Add servers prompt, through which you can construct a custom installation command to use when adding Linux or Windows source servers. To construct a custom installation command, take these steps: 1. Select your operating system. The installation command is different for Windows and Linux. **Note** If you want to install the AWS Replication Agent on a legacy Windows OS (Windows Server 2003, Windows Server 2008 or Windows Server 2008 R2), you must choose the** Legacy OS: Windows Server 2003 or Windows Server 2008** box. This downloads a unique version of the AWS Replication Agent installer that is only valid for legacy Windows OSs (`AwsReplicationWindowsLegacyInstaller.exe`). **Do not** use this installer file to install the agent on any other OS types. 1. Select your replication preferences for the source server. The selected preferences are added as installation prompts to the custom installation command that are generated by this form. Choose the **Replicate all disks** option to replicate all of the disks of the source server. This is the default option. This option adds the `--no-prompt` prompt to the installation command. Select the **Choose which disks to replicate** option to choose which specific disks you want to replicate. You are prompted to select which disks to replicate during agent installation. 1. Enter the credentials that [you previously generated for AWS Replication Agent installation](credentials.md). The form does not send the secret, but does add it to the installation command. 1. If you have not yet obtained the necessary credentials, [follow these instructions](credentials.md). 1. If you are adding a Windows source server to AWS MGN, download the installer onto the source server. The installer is downloaded from the AWS Region of your account. If you're adding a Linux source server, skip this step. 1. Copy the generated custom installation command and either input it into the command line on your source server. Proceed with [AWS Replication Agent installation as instructed in the documentation](agent-installation.md). + **View server details** – Choosing this option to open the server details view for the selected server. This option is only available when a single server is selected. + **Disconnect from service** – Choose this option to disconnect the selected server from Application Migration Service and AWS. This option disconnects the source server and should be used when data replication is complete. 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. If you need to restart data replication for this server, you need to reinstall the agent. This action does not affect any test or cutover 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. + **Mark as archived** – Choose this option to archive the server. You should only archive servers for which you have already performed a cutover. Archived servers are removed from the main **Source servers** page, but can still be accessed through filtering options. On the **Archive X servers** dialog, select **Archive**. To see your archived servers, open the **Preferences** menu by clicking the gear button. Select the **Show only archived servers** option and click **Confirm**. You can now see all of your archived servers. Unselect this option to see your non-archived servers. ### Replication menu The Replication menu allows you to manage data replication for your source servers through these actions: + **Edit replication settings** – Choose this option to be redirected to the **Edit replication settings** page, where you can edit specific replication settings for the selected source server. [Learn more about editing replication settings.](replication-settings-template.md) ### Test and cutover menu The **Test and cutover menu** allows you to manage your test and cutover instances. + **Launch test instances** – Choose this option to launch a test instance for this server. When the **Launch test instances for X** servers dialog appears, click **Launch** to begin the test. The AWS Application Migration Service console indicates **1 launch job complete** after the test has been completed successfully. + **Finalize testing** – Choose the **Mark as "Ready for cutover"** option to finalize testing for this server after you have completed all of the necessary tests in preparation for cutover. When the **Mark X servers as "Ready for cutover"** dialog appears, select whether you want to terminate the launched instances used for testing. We recommend that you terminate these instances, as you will be charged for them even though you no longer need them. Check the **Yes, terminate launched instances (recommended)** box and click **Continue**. The AWS Application Migration Service console indicates that testing has been finalized. The selected source servers' **Migration lifecycle** column shows the **Ready for cutover** status and the launched test instances are deleted if that option was selected. + **Revert to "ready for testing"** – Choose this option to revert a finalized test for this server if you want to run further tests prior to initiating a cutover. When the **Revert testing for X servers** dialog appears, select whether you want to terminate the launched instances used for testing. We recommend that you terminate these instances, as you will be charged for them even though you no longer need them. Check the **Yes, terminate launched instances (recommended)** box and choose **Revert**. The AWS Application Migration Service console indicates that testing has been reverted. The selected source servers' **Migration lifecycle** column shows the **Ready for testing** status and the launched test instances are deleted if that option was selected. + **Launch cutover instances** – Choose this option to launch a cutover instance for this server after you have finalized all of your testing and are ready to initiate a cutover. When the **Launch cutover instances for X** **servers** dialog appears, click **Launch** to begin the cutover. The AWS Application Migration Service console indicates **1 launch job complete** after the cutover has been completed successfully. This changes your source servers' **Migration lifecycle** status to **Cutover in progress**, indicating that the cutover is in progress but has not yet been finalized. + **Finalize cutover** – Choose this option to finalize the cutover for this server after you have successfully performed a cutover. This changes your source servers' **Migration lifecycle** status to **Cutover complete**, indicating that the cutover is complete and that the migration has been performed successfully. In addition, this stops data replication and cause all replicated data to be discarded. All AWS resources used for data replication are terminated. When the **Finalize cutover for X servers** dialog appears, click **Finalize**. The AWS Application Migration Service console indicates **X servers cutover. Data replication has been stopped for servers** once the cutover has been completed successfully. The AWS Application Migration Service console automatically stops data replication for the cutover source servers to save resource costs. The selected source servers' **Migration lifecycle** column shows the **Cutover** status, the **Data replication** column shows **Disconnected** and the **Next step** column states **Mark as archived**. The source servers have now been successfully migrated into AWS and can be archived. **Note** This action does not uninstall the AWS Replication Agent from the source server. Use the **Disconnect from service** option under the **Actions** menu when you have completed the migration and want to uninstall the agent from your source server. + **Revert to "ready for cutover"** – Choose this option to revert a finalized cutover for this server if you encounter any issues or want to reverse the cutover for any reason. This reverts your source servers' **Migration lifecycle** to the **Ready for cutover** status, indicating that these servers have not undergone cutover. When the **Revert cutover for X servers** dialog appears, click **Revert**. + **Edit launch settings** – Use this option to edit the launch settings for this server. This redirects you to the **Launch settings** tab. [Learn more about Launch settings.](launching-target-servers.md) + **Terminate launched instance** – Choose this option if you want to delete your test or cutover instance for any reason at any time. This option can only be selected for a server that has a launched test or cutover instance. When the **Terminate launched instance** dialog appears, click **Terminate**. + **Edit post-launch settings** – Choose this option to edit the post-launch settings for the selected source server or group of source servers. [Learn more about post-launch settings.](source-post-launch-settings.md) ### Alerts and errors You can easily distinguish between healthy servers and servers that are experiencing issues on the **Migration dashboard**. The AWS Application Migration Service console is color-coded for ease of use. + Healthy servers with no errors are characterized by the color blue in both the **Lifecycle** and **Data replication** **status** boxes. + Servers that are experiencing temporary issues such as lagging or rescanning, are characterized by the color yellow. These issues do not halt the replication, but may delay it or indicate a bigger problem. + Servers that are experiencing serious issues such as a loss of connection or a stall are characterized by the color red. You have to fix these issues for data replication to resume. The **Next actions** box provides additional information. For example, if a stall occurred during initiation, you would scroll down to** Replication initiation steps**, where the problematic step is marked with a red 'x'. # Review source server information Server info The **Server info** tab displays 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 source server name 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** + **Hostname** + **Fully qualified domain name** + **VMware virtual machine identifier (if relevant)** + **AWS instance ID** + **AWS ID** + **ARN** + **Operating system** information + **CPUs** + **RAM** + **Primary network interface** Displays the IPv6 address of the interface. + **Recommended instance type** # Add or remove tags assigned to source servers 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 and can be used to search and filter your resources or track your AWS costs. Each tag consists of a key and an optional value. Learn more about AWS tags in [this Amazon EC2 article.](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html) To add tags, take these steps: + Click **Manage tags**. + The **Manage tags** page opens. Click **Add new tag**. + Add a tag **Key** and an optional tag **Value**. + Click **Save**. To remove a tag, take these steps: + Click **Remove**, located to the right of the tag you want to remove. + Click **Save**. # Review disk settings for source servers Disk settings The **Disk settings** tab shows a list of all of the disks on the source server and information for each disk. Disk settings include: + **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. # 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, select the circle to the left of each disk name and choose **Change staging disk type**. On the **Change staging disk type** dialog, select the type of EBS volume to use for the disk or group of disks. Select the **AUTO** option if you want AWS Application Migration Service 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 (gp3)** option). AWS Application Migration Service 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 Application Migration Service always uses EBS magnetic volumes for disks that are under 500 GiB in size when the **AUTO** option is selected. If you do not want AWS Application Migration Service to automatically select a disk, you can select a disk manually. Select the disk type from the**EBS volume type** menu. **Note** When replicating into an AZ, ensure that the AZ supports the staging disk type chosen. 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. For **General Purpose SSD (gp3)** disks, you'll also be able to set the **Throughput**. General Purpose SSD (gp3) volumes have a baseline performance of 125 MiB/s. You can provision additional throughput of 0.25 MiB/s per provisioned IOPS up to a maximum of 1,000 MiB/s (at 4,000 IOPS or higher). Choose **Change** to confirm the change. # Edit replication settings for a source server 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 Application Migration Service, 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 through the **Replication settings** tab. Edit each setting as required and then choose **Save replication settings**. [Learn more about replication settings.](replication-settings-template.md) # Review launch settings for a source server Launch settings The launch settings are a set of instructions that comprise an EC2 launch template and other settings, which determine how a test or cutover 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 Application Migration Service. 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.](launch-settings.md) # Review post-launch settings Post-launch settings Post-launch settings allow you to control and automate actions performed after the server has been launched in AWS. These settings are created automatically based on the **Post-launch settings template.** You must activate the post-launch actions using one of these options: + **Activating the post-launch actions for a specific server**: + Navigate to the **Source servers** page and select a source server. + Click **Post-launch settings > Edit**. + You are redirected to the **Edit post-launch settings** screen. Activate the toggle and click **Save settings**. Alternatively, you can select a specific source server, open the **Test and cutover** drop-down menu located in the top right corner of the screen and select **Edit post-launch settings** . + **Activating the post-launch actions for all servers**: + Navigate to the **Settings** page and choose **Post-launch settings template**. You only need to do this once and the change applies to all newly added servers. After the post-launched actions have been activated from the template, you can deactivate and activate them for individual servers. [Learn more about activating post-launch settings.](post-launch-settings.md#post-launch-settings-activation) The settings configured in the template are applied to every newly added server. You can change the settings for existing and newly added servers individually within the server details view. The **Post-launch settings** template allows you to control various post-launch actions, including: + Deployment of test and cutover instances + Disaster recovery configuration (installing the AWS Replication Agent for AWS DRS and configuring the target disaster recovery AWS Region) + Operating system conversion on the target machine + License and subscription changes on the target machine # Editing the post-launch settings To edit the post-launch settings for a single source servers, check the box to the left of the Hostname of each source server for which you want to edit the post-launch settings, open the **Replication** menu, and choose **Edit post-launch settings**. Alternatively, when editing the settings for a single server, you can choose **Edit** from the **Post-launch settings** tab. These settings can be edited within the post-launch settings template. Once you have edited all your settings, click **Save template**. ## Types of post-launch actions AWS MGN supports post-launch modernization actions, giving you the opportunity to move and improve. All post-launch actions are based on SSM documents (either public or ones you created) that can executed on your EC2 launch instances. There are 2 types of post-launch actions: + **Predefined post-launch actions** – These out-of-the box actions are based on public SSM documents that cannot be changed and have certain unchangeable parameters such as the platform name and order. Fields are prepopulated with the necessary values and only need to be activated or deactivated. For a list of the available actions, see [Predefined post-launch actions reference](predefined-post-launch-actions.md) + **Custom post-launch actions** – These actions are based on SSM documents that you create and upload to your account. To add a custom post-launch action, see [Create a custom post-launch action](post-launch-settings.md#post-launch-settings-custom-actions-add). To edit a custom post-launch action, see [Edit custom post-launch actions](post-launch-settings.md#post-launch-settings-custom-actions-edit). Use the **Filter by** options on the left-hand side to filter the available actions according to your preferences. Click the settings icon in the right-hand corner of the screen to alternate between card and list view, according to your preferences. # Activating and deactivating post-launch actions This setting controls whether post-launch actions are active or inactive. You must leave the **Install Systems Manager agent and allow executing actions on launched servers** option toggled in order for post-launch actions to work. Untoggling the option disallows AWS MGN to install the SSM Agent on your servers and post-launch actions are no longer executed on them. The feature is activated and deactivated at the account level from the **Settings > Post-launch template** screen. [Learn more about activating post-launch settings](post-launch-settings.md#post-launch-settings-activation). After it was activated once, the feature can also be deactivated and reactivated for a single server. Simply selecting a server, go to the **Post-launch settings** tab and click **Edit**. When the feature is inactive: + All actions are hidden. + You are not able to activate actions at the account level or the feature level. When the feature is active: + The actions are visible. + You can activate them. # Deploying post-launch actions Use this setting to choose whether to deploy the post-launch actions only on your cutover instances or on both cutover and test instances.