Pilot Wave – Migration Activities for On-Premises to AWS


Pilot Wave – Migration Activities for On-Premises Servers to AWS

The following table outlines key activities in the Pilot Wave for migrating on-premises servers to AWS.
Each activity includes the objective and a detailed breakdown of associated tasks.

Activity Objective Detailed Tasks
Identifying KMS Keys for EBS Volumes Ensure data-at-rest encryption policies are consistent with security and compliance requirements.
  • Inventory existing KMS keys in the target AWS account(s).
  • Determine if AWS-managed or Customer-managed CMKs will be used.
  • Verify key policies allow access for AWS MGN, Cloud Migration Factory (CMF), and replication roles.
  • Tag and document key IDs for mapping to EBS volumes.
  • Enable KMS key sharing across accounts via AWS Resource Access Manager (RAM) if applicable.
Installing Cloud Migration Factory (CMF) in Core Network Hub Account Deploy the orchestration platform that coordinates migration waves.
  • Deploy CMF stack using CloudFormation or Terraform in the Hub Account.
  • Validate creation of IAM roles, Lambda functions, Step Functions, and DynamoDB tables.
  • Integrate CMF with AWS MGN, Migration Hub, and Service Catalog.
  • Configure CMF networking for private communication with on-prem replication agents.
  • Define migration waves and associate discovered servers.
On-Prem Connectivity to AWS via Private Endpoints Securely enable replication and control plane communications over private connectivity.
  • Establish Direct Connect or VPN tunnel between on-premises and AWS.
  • Deploy VPC endpoints for AWS MGN, SSM, KMS, and S3.
  • Validate Route Tables and Security Groups for replication/control channel traffic.
  • Confirm data transfer remains private (no internet exposure).
  • Perform ICMP/TCP connectivity validation tests.
Kick-off Installation of AWS MGN Agents on On-Prem Servers Begin block-level replication of source servers.
  • Deploy MGN agents via SSM Run Command, Ansible, or manual setup.
  • Ensure connectivity to MGN Replication Servers via private endpoints.
  • Verify agent registration in MGN Console.
  • Tag each server for wave mapping.
  • Document installation outcomes and remediate failures.
Test Replication of Servers to AWS Validate end-to-end replication integrity and readiness for cutover.
  • Monitor initial sync status in AWS MGN dashboard.
  • Validate replication lag and performance metrics.
  • Launch test instances in a non-production subnet.
  • Confirm OS boot, network configuration, and application integrity.
  • Record and analyze replication performance data.
Actual Cutover of Instances Using Cloud Migration Factory Execute controlled transition from on-premises to AWS production.
  • Freeze application writes and stop on-prem workloads.
  • Execute cutover workflows from CMF or Step Functions.
  • Launch final instances from latest replication snapshots.
  • Validate service availability, monitoring, and tagging.
  • Update CMDB and designate instances as Production.
Updates to DNS Route 53 Records Redirect application and user traffic to new AWS infrastructure.
  • Identify DNS zones and records affected by migration.
  • Update A, CNAME, or Alias records to target AWS endpoints (EC2, ALB, NLB, etc.).
  • Adjust TTL values to reduce propagation time.
  • Test end-to-end resolution and application access.
  • Document rollback procedures if issues arise post-migration.

Deliverables for Pilot Wave

  • KMS Key Mapping Document
  • Successful CMF Deployment Validation Report
  • Private Connectivity and Endpoint Validation Report
  • MGN Agent Installation Log and Status Summary
  • Replication Validation and Test Checklist
  • Cutover Execution Report
  • Updated Route 53 Change Log