Options, tools, and best practices for migrating Microsoft workloads to AWS - AWS Prescriptive Guidance

Options, tools, and best practices for migrating Microsoft workloads to AWS

Jerroll Harewood, Christine Megit, Dror Helper, Daniel Maldonado, Phil Ekins, Mani Pachnanda, Siddharth Mehta, Rich Benoit, Rob Higareda, Saleha Haider, Siavash Irani, and Yogi Barot, Amazon Web Services (AWS)

April 2024 (document history)

Overview

Organizations have been migrating and running their Microsoft workloads on AWS for over a decade—longer than any other cloud provider. Based on the knowledge and expertise that AWS has gained from migration and modernization efforts over the years, this guide is designed to streamline the migration of your Microsoft workloads to the AWS Cloud. You can use this guide to plan and implement all phases of your Windows migration. This guide is applicable to a variety of migration use cases, including the following:

  • You're starting a Windows migration as part of a digital transformation and modernization journey in your organization.

  • The lease on the data center where you run your Microsoft workloads is nearing expiration.

  • You have a variety of Windows applications with varying availability requirements, but you don't have the resources to deploy your workloads across geographically distributed locations.

In this guide, you learn about a variety of AWS tools that can help streamline your migration journey, such as AWS Migration Hub, AWS Application Migration Service, and more. To align with AWS best practices, this guide follows the three-phase AWS migration process: assess, mobilize, and migrate and modernize. This process is based on a time-tested migration framework that can help you structure and streamline your Windows migration. In the assess phase, you evaluate your readiness for operating in the cloud. In the mobilize phase, you draft migration plans and close readiness gaps identified in the assess phase. Then, you start to migrate your workloads in the migrate and modernize phase by using a combination of automation tools and templates to systematically migrate your workloads and meet your business requirements.

Intended audience

This guide is intended for IT architects, migration leads, technical leads, AWS Partner teams, and other roles responsible for the following:

  • Migrating Microsoft workloads from a data center to the AWS Cloud

  • Managing a Windows environment in the AWS Cloud

Targeted business outcomes

This guide can help you and your organization achieve the following objectives:

  1. Learn about the strategies, programs, and services available for migrating Microsoft workloads to AWS.

  2. Understand the AWS migration paths for specific Microsoft workloads, such as Active Directory, Windows File Server, SQL Server, and .NET workloads.

  3. Run your Microsoft workloads on AWS while meeting your security, availability, and reliability requirements.

  4. Familiarize yourself with licensing best practices for running Microsoft workloads on AWS.