Deploying the PoC environment
Many users prefer to thoroughly test all communication channels and migration steps in advance. Testing migration from isolated networks could be a challenge. To address that need, AWS provides two options:
An AWS CloudFormation template
that prepares all required resources on AWS. The template builds a proof of concept (PoC) environment that emulates the components of the data center environment and sets up the AWS infrastructure. It includes isolated source and target VPCs, subnets, and VPC endpoints. A dedicated workshop (Migrate the Well-Architected Way
) with detailed, step-by-step instructions to create your test environment (see the step Create VPC endpoints ).
Alternatively, you can deploy your PoC environment by following the steps in the next sections.
Manual deployment
The following list outlines the major steps for manual deployments in your environment. For more information, see Connect to AWS Transform MGN data and control planes over a private network.
Create the source VPC and staging area VPC with a private subnet.
Create the following VPC endpoints in the staging area subnet:
MGN, and enable the private DNS name (shared by the replication server and source server).
Amazon EC2, and enable the private DNS name (shared by the replication server and source server).
Amazon S3 (private DNS name not supported). Interface endpoints are supported across Direct Connect, AWS VPN, and VPC peering. Therefore, this is required for source servers only (and could be located on premises) to connect to the MGN control plane over a private network.
Note
The ssm and ssmmessages endpoints are optional and currently created to connect the source server through the AWS Systems Manager Session Manager.
Amazon S3 gateway endpoint in the staging area subnet. This is required by the replication server to connect to Amazon S3. You must update the routes for the staging area subnet.
Create an inbound resolver endpoint in the staging area VPC to allow resolution of the private DNS record (for VPC interface endpoints) from the source VPC.
Update the source VPC DHCP options with the inbound resolver endpoint of the staging area VPC as DNS server IP.
Enable peering between the source and staging VPCs, and update both VPC route tables.
Create a security group in the source and staging VPCs to allow the following ports.
Source
Destination
Port
Description
Source data center
Amazon S3 service URLs
443 (TCP)
Source data center
The MGN Region-specific console address
443 (TCP)
Communication between the source servers and MGN over TCP port 443
Source data center
Staging area subnet
1500 (TCP)
Communication between the source servers and the staging area subnet over TCP port 1500
Staging area subnet
The MGN Region-specific console address
443 (TCP)
Communication between the staging area subnet and MGN over TCP port 443
Staging area subnet
Amazon S3 service URLs
443 (TCP)
Staging area subnet
Amazon EC2 endpoint of its AWS Region
443 (TCP)
Initialize MGN in the staging area AWS Region by updating the staging area subnet details and enabling communication over private IP.
Create an AWS Identity and Access Management (IAM) role for installing MGN Agent. Attach managed policies and generate access keys and a secrets key.
Create an IAM profile to connect Amazon EC2 via the Session Manager.
Install an Agent on the source machines.
Automate agent deployments with Cloud Migration Factory
The Cloud Migration Factory on AWS
Manually run these scripts
from the command line, as described in the Run automations from command prompt section of the Cloud Migration Factory User Guide Add the scripts
to Migration Factory by following the instructions in the Scripts management section for full integration with Cloud Migration Factory
These scripts automate the following:
MGN Agent installation on a Windows server using private endpoints
MGN Agent installation on Linux servers using private endpoints
