Migrating Windows workloads to AWS
summary
Three concrete migration patterns for Windows workloads with tool names and outcomes: extend on‑prem AD by promoting EC2 instances as domain controllers, or use AWS Managed Microsoft AD or AD Connector to proxy auth; move SQL Server with DMS replication instance and CDC, agentless SMS or CloudEndure agent block‑replication (agent encrypts and ships EBS volumes), or use SQL native distributed availability groups; migrate .NET with Windows Web App Migration Assistant, App2Container (containerization in about 30 minutes), or EMP compatibility packaging; MAP and OLA provide assessment, licensing and scoped lift‑and‑shift/modernization plans.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:55Common Microsoft workload migration patterns
- 1:20Microsoft Active Directory (AD) migration patterns
- 1:53Self-managed Active Directory on EC2
- 5:44AD Connector
- 6:47Running SQL Server on AWS
- 7:14SQL Server migration paths
- 7:51Migrate SQL Server database using AWS DMS
- 9:00Migrate SQL Servers to Amazon EC2 using CloudEndure
- 10:14Migrate SQL Servers to Amazon EC2 AWS SMS
- 11:32Migrate SQL Server database to Amazon EC2 using distributed availability groups
- 12:50Platforms to host your .NET application
- 13:54Windows Web Application Migration Assistant
- 18:31End-of-Support Migration Program for Windows Server
- 19:50AWS Migration Acceleration Program
- 20:41AWS Optimization and Licensing Assessment
- 21:26Learn migration with AWS Training and Certification
related talks
27mMigrating Microsoft workloads to AWS
01h 00mWin the market opportunity for Microsoft workloads on
30mTransform with Microsoft on AWS
33mSimplifying Microsoft Architectures with AWS Services
50mMigrate and modernize enterprise workloads with
01h 03mWindows at Scale
25mMigrate Your Enterprise Applications to the Cloud
32mDive into technical decisions from successful migrations