Step 7: Configure a migration automation server

Navigate to the AWS CloudFormation console and select the solution’s stack.

Select the Outputs tab, under the Key column, locate AutomationServerInstanceProfile and record the Value to use later in the deployment.

Outputs tab

Navigate to the Amazon Elastic Compute Cloud (EC2) console.

From the left navigation pane, select Instances.

On the Instances page, use the Filter Instances field and enter the name of the migration execution server to find the instance.

Select the instance and select Actions on the menu.

Select Security from the drop-down list, and then select Modify IAM role.

From the list of IAM roles, locate and select the IAM role containing the value for AutomationServerInstanceProfile that you recorded earlier in this procedure and choose Save.

Select the instance, then choose Connect.

On the Session Manager tab, verify that the status shows Connected.

Add the following tag to the migration automation server EC2 instance: Key= role and Value = mf_automation.

EC2 console

Navigate to the AWS CloudFormation console and select the solution’s stack.

Select the Outputs tab, under the Key column, locate AutomationServerIAMPolicy and record the value to use later in the deployment.

Outputs tab

Navigate to the AWS Identity and Access Management (IAM) console.

From the left navigation pane, select Users, then choose Add users.

In the User name field, create a new user.

Choose Next.

On the Set permissions page, under Permissions options, select Attach policies directly. A list of policies displays.

From the list of policies, locate and select the policy containing the value for AutomationServerIAMPolicy that you recorded in Launch the stack.

Choose Next, then verify that the correct policy is selected.

Choose Create user.

After you’re redirected to the Users page, choose the user you created in the previous step, and then choose the Security credentials tab.

In the Access keys section, choose Create access key.

To view the new access key pair, choose Show. You will not have access to the secret access key again after this dialog box closes. Your credentials will look something like this:

To download the key pair, choose Download .csv file. Store the keys in a secure location. You will not have access to the secret access key again after this dialog box closes.

After you download the –0—csv file, choose Close. When you create an access key, the key pair is active by default, and you can use the pair right away.

Use your remote desktop protocol (RDP) to log in to the migration execution server.

Signed in as an administrator, open a command prompt (CMD.exe).

Run the following command to configure the AWS credentials on the server. Replace <your_access_key_id>, <your_secret_access key>, and <your_region> with your values:

SETX /m AWS_ACCESS_KEY_ID <your_access_key_id>
SETX /m AWS_SECRET_ACCESS_KEY <your_secret_access key>
SETX /m AWS_DEFAULT_REGION <your_region>

Reboot automation server.

Install the SSM agent using Hybrid mode (on-prem servers).

To connect to the migration automation server, in the EC2 console, select the instance, and choose Connect > RDP client > Connect using Fleet Manager > Fleet Manager Remote Desktop. Log in as Administrator.

Download Python v3.14.4. Other versions of Python might also work if installed for all users using the standalone Python installer (not the Python install manager).

Run the Python installer and choose Customize installation.

Choose Next, and select Install for all users and Add Python to environment variables. Choose Install.

Migration Factory web interface Attribute Details tab

Verify that you have administrator privileges, open cmd.exe, and run the following commands to install the Python packages one at a time:

python -m pip install requests
python -m pip install paramiko
python -m pip install boto3

If any of these commands fail, upgrade pip by running the following command:

python -m pip install --upgrade pip

Install the AWS CLI (Command Line Interface) by running the following command:

msiexec.exe /i https://awscli.amazonaws.com/AWSCLIV2.msi

For more information, refer to Install or update to the latest version of the AWS CLI in the AWS CLI User Guide.

Open PowerShell, then install the PowerShell for AWS module, ensuring that you have the *-Scope AllUsers * parameter included in the command.

Install-Module -Name AWSPowerShell -Scope AllUsers

For more information, refer to Installing the AWS Tools for PowerShell in the AWS Tools for PowerShell User Guide.

To enable script execution, open PowerShell as Administrator and run the following command:

Set-ExecutionPolicy RemoteSigned