Migrating Windows Server

This section focuses on the different options available for migrating Windows Server to AWS.

Assess

First, identify the applications and workloads that need to be migrated to AWS. You can use AWS Application Discovery Service to create a map of your on-premises infrastructure and dependencies between applications. This helps you identify the servers, applications, and services that you need to migrate to AWS.

You can use AWS Migration Hub to create an inventory of your applications and evaluate their compatibility with AWS. Migration Hub provides a centralized view of your application portfolio and helps you plan, track, and manage your migration projects. You can also use third-party assessment tools that support AWS, such as Cloudamize or Evolve.

Mobilize

It can be a significant challenge to find the right path for rehosting (lift and shift) large scale infrastructure. While there are numerous best practices that are helpful, the choice of tool depends on multiple factors, such as workload type, affordable downtime, and operating system requirements. We recommend that you use AWS Application Migration Service to rehost.

AWS Application Migration Service

You can use Application Migration Service to quickly lift and shift physical, virtual, or cloud servers without compatibility issues, performance impact, or long cutover windows. Application Migration Service continuously replicates your source servers to your AWS account. Then, when you're ready to migrate, Application Migration Service automatically converts and launches your servers on AWS with minimal downtime. For more information, see What Is AWS Application Migration Service? in the Application Migration Service documentation.

AWS Migration Hub Orchestrator

AWS Migration Hub Orchestrator simplifies and automates the migration of servers and enterprise applications to AWS by using Application Migration Service. It provides a single location to run and track your migrations. You can use Migration Hub Orchestrator to migrate SAP NetWeaver-based applications—such as S/4HANA, BW/4HANA, SAP ECC on HANA, and others—to AWS and rehost supported custom applications to Amazon EC2. Migration Hub Orchestrator offers templates to create a migration workflow that can be customized to fit your unique migration requirements. Also, Migration Hub Orchestrator automates the steps in your chosen workflow and displays the status of migration.

VM Import/Export

VM Import/Export enables you to import VM images from your existing virtualization environment to Amazon EC2, and then export them back. This enables you to migrate applications and workloads to Amazon EC2, copy your VM image catalog to Amazon EC2, or create a repository of VM images for backup and disaster recovery. For more information, see What is VM Import/Export? in the Amazon EC2 documentation.

After assessing the workloads for migration, create a migration plan that outlines the migration strategy, timeline, and costs involved in the migration process. You can use AWS Pricing/TCO Tools to estimate the cost savings of running your applications on AWS. You can also use AWS Application Discovery Serviceto identify the right AWS services to host your migrated workloads.

Migrate

Migrating a Windows workload to AWS involves several phases, including the migration planning, readiness assessment, and migration implementation phases. The migrate phase is the last phase, which involves migrating the Windows workload to AWS. The following are some steps to consider during the migrate phase:

• Prepare the AWS environment – Before you begin the migration process, you must prepare the AWS environment by creating an Amazon Machine Image (AMI) and setting up a VPC where you're migrating the workload.

• Select the migration tool – There are various migration methods to choose from, including Migration Hub, Application Migration Service, and VM Import/Export. Choose the method that best suits your needs.

• Configure the migration – Configure the migration by selecting the source server and specifying the target instance type, storage, and network settings.

• Perform the migration – After the configuration is complete, perform the migration. The process involves replicating the data, testing the migrated workload, and performing final cutovers to switch over to the migrated workload. The migration tool you selected above will guide you through these steps.

• Validate the migration – After the migration is complete, validate that the migrated workload is functioning as expected. Perform tests and ensure that the security and compliance requirements are met.

• Optimize the migrated workload – Optimize the migrated workload by resizing the instance, configuring auto-scaling, and implementing cost-saving strategies such as Reserved Instances or Spot Instances.

• Monitor and manage the migrated workload – Continuously monitor and manage the migrated workload to ensure optimal performance and security. You can use Amazon CloudWatch for monitoring.