Overview
This Guidance shows how to migrate your VMware virtual machines (VMs) to Amazon Elastic Compute Cloud (Amazon EC2) using AWS Application Migration Service (AWS MGN). Migrating on-premises VMware workloads to Amazon EC2 offers enhanced scalability, improved performance, and reduced operational costs. AWS MGN streamlines the migration process with seamless, automated block-level replication, allowing you to thoroughly test migrated VMs on Amazon EC2 while continuously replicating the original source server. This Guidance minimizes the cutover window and facilitates live migrations with no downtime or minimal customer impact.
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Implementation resources
A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
Open implementation guide
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages