Focus: Migrating a virtual machine from GCP to AWS using AWS Application Migration Service (MGN)
Overview of Network Architecture
Understanding how AWS MGN works for server replication
Process starts with installing a replication agent on the source VM
Source VMs can be from corporate data centers or other cloud providers
Key Components of AWS MGN
Replication Agent:
Installed on the source VM
Appears as a source server in AWS MGN service console
Replication Servers:
Created automatically by MGN to replicate source disks to a staging area
Creates equal number of EBS volumes to match source disks
Conversion Server:
Makes the staging area EBS volumes bootable for testing/cutover EC2 instances
Demo Steps
GCP Console Setup:
Created a simple Linux web server on GCP using Compute Engine
Goal: Migrate without changes
AWS Console Configuration:
Search for Application Migration Service
Configure replication and launch settings
Replication Template: Defines replication server configuration
Launch Template: Defines test and cutover EC2 instance configuration
Customizable settings: IP address, subnet choice, security groups
Server Addition:
Click "ADD server" and follow installation instructions
Choose between IAM user credentials or Single Sign-On (SSO) credentials
Replication Agent Installation:
Download and install commands prepared for you
Monitor installation progress and replication initiation in MGN console
Monitoring Replication
Initial replication process may take a few minutes
EC2 console shows creation of a new replication server
Job History:
Server info captured (hostname, CPUs, OS, memory, disks)
Disk settings can be customized for staging disks
Launching Test Instances
Once replication is ready, proceed to launch a test instance
Check job history for conversion status
Temporary conversion starts to make EBS volumes bootable
New EC2 instance appears in console, replicating the source server
Testing Migration
Copy public IP of the launched test instance
Confirm successful migration by accessing the application
Final Steps
After testing, mark the source server as ready for cutover
This will terminate test servers and prepare for actual cutover
Important Note: Once a test or cutover instance is launched, the source server and the new instance are no longer in sync, but replication continues to the staging area as long as the replication server is active
Conclusion
Overview of migration process from GCP to AWS using AWS Application Migration Service
Encouragement for feedback and comments on the demo.