Skip to Content
Cloud Engineering Academy
13. Microsoft-to-AWS Migration

Module 13: Microsoft-to-AWS Migration

A dedicated path for experienced .NET developers moving a Microsoft and Azure estate to AWS, with side-by-side examples for every major service. You learn how to assess a portfolio, apply the 7 Rs, port .NET Framework code, migrate SQL Server data, and plan a cut-over with a tested rollback.

SAP-C03SAA-C03

Assumes: .NET 10 LTS · .NET Framework 4.8 (source app) · AWS SDK for .NET v4 · Region us-east-1. Verified against official sources on 2026-11-18.

A dedicated path for experienced .NET developers moving a Microsoft and Azure estate to AWS, with side-by-side examples for every major service. You learn how to assess a portfolio, apply the 7 Rs, port .NET Framework code, migrate SQL Server data, and plan a cut-over with a tested rollback.

Estimated timeAbout 16 hours (lessons 10 h · labs 4 h · assignment 2 h)
Priority for you⭐ Critical — priority 1 (this is your organisation's real project)
LevelIntermediate → advanced
CertificationsSAP-C03 (primary) · SAA-C03
Cost profile🟢 assessment, porting and local SQL Server · 🟡 short DMS run · 🔴 Windows/RDS SQL Server (deploy-and-destroy or design-only)

Why this matters in banking

Your bank is moving from the Microsoft ecosystem to AWS, and you will be the person who knows both sides. Migrations fail for predictable reasons: a database cut-over that loses transactions, a Windows licence bill nobody forecast, an identity integration that locks out staff, or a rollback plan that was never rehearsed. In a regulated bank, a migration is also a material change: risk, change-approval boards and possibly the regulator need evidence of testing, data reconciliation and fall-back. This module gives you the vocabulary, the tools and a repeatable plan.

Analogy: moving a bank branch to a new building. Some furniture moves as-is (rehost), some gets refurbished (replatform), some is rebuilt to fit the new space (refactor), and some is thrown away (retire). You keep the old branch open until the new one has balanced its tills.

From .NET/Azure to AWS

You know (Microsoft/Azure)AWS equivalentWhat's different
Azure App ServiceElastic Beanstalk, ECS on Fargate, ECS Express ModeApp Runner is closed to new customers; ECS Express Mode is the simple path
Azure FunctionsAWS LambdaTriggers become event source mappings and EventBridge rules
Azure SQL / SQL Server on VMsRDS for SQL Server, Aurora PostgreSQL (with Babelfish)Babelfish lets Aurora PostgreSQL understand much T-SQL; test thoroughly
Blob StorageAmazon S3Bucket policies and Block Public Access replace container access levels
Azure API ManagementAmazon API GatewayPolicies become authorisers, usage plans, WAF and mapping templates
Service Bus queues/topicsSQS, SNS, EventBridgeSessions map loosely to SQS FIFO message groups
Event GridAmazon EventBridgeRules, schema registry, archive and replay
Azure DevOps PipelinesCodePipeline/CodeBuild or GitHub Actions with OIDCNo stored cloud keys; roles assumed per run
Key VaultSecrets Manager + AWS KMS (+ CloudHSM)Secrets and keys are separate services
Azure Monitor / Application InsightsCloudWatch, X-Ray, OpenTelemetry (ADOT)Correlation via trace IDs; Logs Insights instead of KQL
Entra IDIAM Identity Center (workforce), Cognito (customers)Federate Entra ID into Identity Center via SAML/SCIM
Active Directory Domain ServicesAWS Managed Microsoft AD, AD ConnectorSimple AD is in maintenance; don't plan on it
ARM / BicepCloudFormation / CDK (C#)CDK lets you write infrastructure in C#
Azure MigrateAWS Transform, AWS Application Migration Service (MGN), AWS DMSDiscovery and assessment have moved to AWS Transform

Learning objectives

By the end of this module you can:

  • Map each Azure service in your estate to its AWS equivalent and explain the important behavioural differences.
  • Run a portfolio assessment and classify each application with the 7 Rs: rehost, replatform, refactor, repurchase, retain, retire, relocate.
  • Port a .NET Framework 4.8 application towards .NET 10 using AWS Transform for .NET and the .NET Upgrade Assistant, then containerise it.
  • Plan a SQL Server migration: target choice (RDS SQL Server, Aurora PostgreSQL with Babelfish), schema conversion, full load plus change data capture with DMS, and reconciliation.
  • Design identity integration (Entra ID or on-premises AD to IAM Identity Center and Managed Microsoft AD) and hybrid network connectivity.
  • Explain Windows and SQL Server licensing options on AWS and their cost impact.
  • Write a cut-over and rollback plan with go/no-go criteria and data reconciliation checks.

Prerequisites

How the pieces fit

Lessons

  1. Azure vs AWS: the big picture — account model, Regions, identity, networking and support differences that surprise Azure engineers.
  2. Hosting side by side — Microsoft hosting (IIS, App Service) vs Elastic Beanstalk, ECS Express Mode, ECS/Fargate and EC2 Windows, with the same app deployed each way.
  3. Azure Functions to AWS Lambda — triggers, bindings vs SDK calls, durable functions vs Step Functions.
  4. Data services side by side — Azure SQL/SQL Server vs RDS/Aurora (including Babelfish), Cosmos DB vs DynamoDB, Blob Storage vs S3.
  5. Integration side by side — API Management vs API Gateway, Service Bus vs SQS/SNS/EventBridge, Event Grid vs EventBridge.
  6. DevOps, IaC and secrets side by side — Azure DevOps vs CodePipeline/GitHub Actions, ARM/Bicep vs CloudFormation/CDK, Key Vault vs Secrets Manager/KMS.
  7. Monitoring and identity side by side — Azure Monitor/App Insights vs CloudWatch/X-Ray, Entra ID vs IAM Identity Center/Cognito, identity integration patterns.
  8. The 7 Rs of migration — retire, retain, relocate, repurchase, rehost, replatform and refactor, with an ordered decision rule and a banking example of each.
  9. Lab 13.1: classify an estate with the 7 Rs — the hands-on checkpoint for lessons 1 to 8 (see the labs section below).
  10. Migration assessment and portfolio discovery — inventory, dependency mapping, wave planning and business-case basics with AWS Transform.
  11. Rehosting with AWS Application Migration Service — replication agents, test launches, cut-over launches and post-launch actions. AWS documentation now brands the service "AWS Transform MGN" ⚠ VERIFY whether the API and CLI names change.
  12. .NET Framework to modern .NET — AWS Transform for .NET, the .NET Upgrade Assistant, WCF/Web Forms blockers and when to stay on Windows.
  13. SQL Server database migration — target choice, Babelfish compatibility checks, DMS full load plus CDC, validation and EF Core changes.
  14. Network migration and hybrid architecture — VPN and Direct Connect, hybrid DNS with Route 53 Resolver, coexistence during long migrations.
  15. Windows and SQL Server licensing on AWS — license-included vs bring-your-own-licence, Dedicated Hosts, and the cost of staying on Windows. Informational, not licensing or legal advice.
  16. Cut-over and rollback planning — freeze windows, reconciliation, go/no-go criteria, rollback triggers and evidence for change boards.

Labs and module project

  • Lab 13.1 (🟢): classify an estate with the 7 Rs — run and extend a tested C# rule engine that classifies a fifteen-component fictional bookshop estate into the seven strategies, groups chatty components into waves and prints a change-board report. The estate is an invented inventory modelled on a classic .NET Framework and SQL Server monolith; it is not the real component list of the bobs-used-bookstore-classic sample. 61 tests, no AWS account. The code is in labs/m13-migration-classifier/.
  • Lab 13.2 (🟢) — coming: port a slice of the bookstore to .NET 10 with the .NET Upgrade Assistant (AWS Transform for .NET as an optional paid path), and containerise it locally. The lesson .NET Framework to modern .NET has a scanner exercise in the meantime.
  • Lab 13.3 (🟢) — coming: SQL Server in Docker as the "on-premises" source, with fictional bookstore and customer data from a seeded C# generator.
  • Lab 13.4 (🟡) — coming: a short DMS run from a local or tiny source to Aurora PostgreSQL or RDS, with validation; destroy the replication instance the same day. The walkthrough is in SQL Server database migration.
  • Lab 13.5 (🟢) — coming: write the cut-over runbook and rollback plan for the bookstore and review it against a checklist. The method is in Cut-over and rollback planning.

Module assignment — migration plan. Produce a migration plan for a fictional bank's three-application portfolio: a 7 Rs classification, target architecture diagram, data migration approach, licensing estimate, cut-over timeline and rollback triggers. This feeds Capstone 6 — Legacy .NET Framework Migration (assess → port/containerise → migrate SQL Server data with DMS → deploy → cut-over → rollback plan).

When you finish, keep the Module 13 cheat sheet handy for revision.

Cost profile

PartLabelFree alternative
Service mapping, 7 Rs, assessment, cut-over planning🟢 freeDesign and documentation work
Porting with .NET Upgrade Assistant, local containers🟢 freeRuns on your machine
SQL Server source database🟢 freeSQL Server Developer or Express edition in Docker
AWS Transform for .NET🟡 creditsCheck current pricing before use ⚠ VERIFY; the Upgrade Assistant is a free fallback
DMS replication instance + Aurora/RDS target🟡 creditsSmallest instance, small dataset, destroy the same day
EC2 Windows / RDS for SQL Server (licence included)🔴 paidDeploy-and-destroy within an hour, or design-only
Application Migration Service rehost test🔴 paidDesign-only walkthrough of the replication and cut-over steps
Managed Microsoft AD, Direct Connect🔴 paidDesign-only exercise

Certification alignment

ExamDomains (weight)What this module covers
SAP-C03Resilience & Migration (weight ⚠ VERIFY) · Design (weight ⚠ VERIFY)Migration strategy, 7 Rs, tooling, hybrid design
SAA-C03Cost-Optimized (20%) · Resilient (26%)Target choices, licensing cost, database migration

The domain labels are short forms; see each exam page for the official wording and weights.

Service availability notes

Migration tooling has changed — verified 2026-11-17

AWS Migration Hub and AWS Application Discovery Service closed to new customers on 2025-11-07. AWS Transform is the recommended successor for discovery and assessment.

The AWS .NET Modernization Tools — Porting Assistant for .NET, App2Container, AWS Toolkit for .NET Refactoring and Microservice Extractor for .NET — closed to new customers on 2025-11-07. Use AWS Transform for .NET (GA May 2025) instead.

AWS App Runner is in maintenance and closed to new customers (announced 2026-03-31); AWS recommends Amazon ECS Express Mode. Elastic Beanstalk is active and offers a .NET 10 on Amazon Linux 2023 branch as well as Windows Server/IIS platforms.

AWS Directory Service – Simple AD is in maintenance (announced 2026-06-30); use AWS Managed Microsoft AD or AD Connector.

DMS Schema Conversion is the managed, no-additional-charge schema converter inside AWS DMS, with generative-AI-assisted conversion and (since July 2026) an offline SQL Server source. The status of the standalone desktop AWS Schema Conversion Tool (SCT) could not be confirmed ⚠ VERIFY.

AWS Application Migration Service (MGN) is active; AWS documentation now brands it AWS Transform MGN ⚠ VERIFY whether the API, CLI and IAM names change. Windows and SQL Server licensing rules change; confirm BYOL eligibility with Microsoft licensing terms ⚠ VERIFY.

Key AWS services

AWS Transform (including AWS Transform for .NET) · AWS Application Migration Service (AWS Transform MGN) · AWS Database Migration Service (DMS Schema Conversion) · Amazon RDS for SQL Server · Amazon Aurora PostgreSQL with Babelfish · AWS Elastic Beanstalk · Amazon ECS (Fargate, Express Mode) · Amazon EC2 Windows · AWS Lambda · Amazon S3 · Amazon API Gateway · Amazon SQS / SNS / EventBridge · AWS Secrets Manager · AWS KMS · IAM Identity Center · AWS Directory Service (Managed Microsoft AD, AD Connector) · AWS Site-to-Site VPN · AWS Direct Connect · Route 53 Resolver

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page