Install the AWS Replication Agent on a source server

What you need before step 1

Applies to: AWS Transform MGN (formerly AWS Application Migration Service) with physical, VMware, Hyper-V or other-cloud Windows and Linux servers, as documented by AWS

9 steps

1. 1

   Initialise the service in your target Region

   Where: AWS Management Console > Region selector (top right) > your target Region > search "MGN" > AWS Transform MGN

   Choose Get started. Create the replication settings template: select the staging area subnet, the replication server instance type (t3.small by default) and the EBS volume type (gp3 by default), then choose Create template. AWS says the service creates the IAM roles it needs for replication and launching servers. If the console later asks, choose Reinitialize service permissions on the replication settings page.

   You should see: The replication settings template is created and the Source servers page is available in the console navigation.
2. 2

   Create the agent installation role

   Where: AWS Management Console > IAM > Roles > Create role

   For Trusted entity type select AWS account > This account. On Add permissions search for and tick AWSApplicationMigrationAgentInstallationPolicy. Name the role MGN_Agent_Installation_Role and create it. AWS recommends temporary credentials over IAM user access keys.

   You should see: The role appears in IAM > Roles with the AWSApplicationMigrationAgentInstallationPolicy attached.
3. 3

   Generate temporary credentials

   Where: Your admin PC, in a terminal with the AWS CLI signed in to the target account

   Assume the role and copy AccessKeyId, SecretAccessKey and SessionToken from the output. AWS notes these credentials expire after one hour, so install the agent soon after.

   aws sts assume-role --role-arn arn:aws:iam::123456789012:role/MGN_Agent_Installation_Role --role-session-name mgn_installation_session_role

   You should see: JSON with a Credentials block containing AccessKeyId, SecretAccessKey, SessionToken and Expiration.
4. 4

   Optional: generate a ready-made install command

   Where: AWS Transform MGN console > Source servers > Add server

   Select the operating system, choose Replicate all disks (adds --no-prompt) or Choose which disks to replicate, and enter the credentials. The form builds a custom installation command for you to copy. It does not send the secret anywhere; it only adds it to the command.

   You should see: A custom installation command appears that you can copy to the source server.
5. 5

   Windows: download the installer

   Where: Windows source server: right-click Start > Windows PowerShell (Admin). AWS recommends PowerShell over Command Prompt because it supports Ctrl+V pasting

   Download the installer for your Region (example shown for ap-southeast-2). For Windows Server 2003 to 2008 R2 use AwsReplicationWindowsLegacyInstaller.exe and for Windows Server 2012 use AwsReplicationWindows2012LegacyInstaller.exe instead.

   Invoke-WebRequest -Uri "https://aws-application-migration-service-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/windows/AwsReplicationWindowsInstaller.exe" -OutFile .\AwsReplicationWindowsInstaller.exe

   You should see: AwsReplicationWindowsInstaller.exe is in the current folder.
6. 6

   Windows: run the installer

   Where: The same elevated PowerShell window

   Run the installer (or paste the command generated by Add server). Enter the AWS Region name, the access key ID, secret access key and session token when prompted, then press Enter to replicate all disks or type the disks to include.

   .\AwsReplicationWindowsInstaller.exe

   You should see: The installer identifies the disks, installs the agent and reports the source server ID.
7. 7

   Linux: download the installer

   Where: Linux source server, terminal as a user with sudo

   Download the installer for your Region (example for ap-southeast-2).

   wget -O ./aws-replication-installer-init https://aws-application-migration-service-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/latest/linux/aws-replication-installer-init

   You should see: wget reports the file was saved.
8. 8

   Linux: run the installer

   Where: The same terminal

   Pass the credentials as environment variables, which AWS recommends over command-line parameters because parameters are visible in the process list. --no-prompt runs silently and replicates all disks. To pick disks interactively, drop --no-prompt and type the disk paths (for example /dev/sda,/dev/sdb) when asked; the root disk is always replicated.

   export AWS_ACCESS_KEY_ID=ASIAIOSFODNN7EXAMPLE
   export AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
   export AWS_SESSION_TOKEN=AQoDYXdzEJr...EXAMPLE
   chmod +x aws-replication-installer-init
   sudo -E ./aws-replication-installer-init --region ap-southeast-2 --no-prompt

   You should see: The installer confirms all disks were identified, installs the agent and prints the source server ID.
9. 9

   Check the server in the console

   Where: AWS Transform MGN console > Source servers

   Find the server by hostname. Wait while it completes initial sync. Before testing, AWS says the Migration lifecycle should be Ready for testing and Data replication status Healthy.

   You should see: The server is listed and moves through initial sync to Ready for testing with Healthy replication.

Expert tips

How to confirm it worked

• AWS Transform MGN console > Source servers shows the server with Data replication status Healthy and Migration lifecycle Ready for testing.

• From the CLI: aws mgn describe-source-servers --region ap-southeast-2 lists the source server ID the installer printed.

• On the source server the agent log exists: /var/lib/aws-replication-agent/agent.log.0 (Linux) or C:\Program Files (x86)\AWS Replication Agent\agent.log.0 (64-bit Windows).

How to reverse it

Errors you might see

Questions

Official sources

Vendors change menus and requirements. Confirm on the source before you rely on a detail. Last checked 4 Nov 2026.