AWS Migration Assessment and Tracking: Mastering AWS Migration Hub
Migration assessment and tracking tools (for example, AWS Migration Hub)
AWS Migration Assessment and Tracking: Mastering AWS Migration Hub
This study guide covers the essential tools and strategies for assessing and tracking workload migrations to AWS, a critical component of Domain 4 (Accelerate Workload Migration and Modernization) for the AWS Certified Solutions Architect - Professional (SAP-C02) exam.
Learning Objectives
After studying this guide, you should be able to:
- Identify the primary functions of AWS Migration Hub as a central tracking dashboard.
- Select appropriate assessment tools like AWS Application Discovery Service and AWS Schema Conversion Tool (SCT).
- Classify workloads according to the 7Rs migration strategy framework.
- Differentiate between various migration execution tools (MGN, DMS, DataSync).
- Evaluate migration readiness using portfolio assessment and TCO analysis.
Key Terms & Glossary
- AWS Migration Hub: A central location to collect inventory and tracking data from different AWS and third-party tools to provide a single view of the migration.
- Application Discovery Service (ADS): A tool that collects configuration and usage data from on-premises servers to help plan migrations.
- Schema Conversion Tool (SCT): Automates the conversion of database schemas from one engine to another (heterogeneous migration).
- Application Migration Service (MGN): The primary service for lift-and-shift (rehost) migrations of physical, virtual, or cloud-based servers.
- Wave Planning: The process of grouping applications into logical "waves" for migration based on dependencies and business priority.
The "Big Idea"
Migration is not a single event but a lifecycle consisting of four distinct phases: Assess, Mobilize, Migrate, and Modernize. Success depends on having high-fidelity data during the Assessment phase to avoid "migration stalls" caused by hidden dependencies. AWS Migration Hub acts as the "command center," providing the visibility needed to manage large-scale portfolios across these phases.
Formula / Concept Box
The 7Rs Migration Strategies
| Strategy | Description | Best For |
|---|---|---|
| Retire | Decommissioning applications no longer needed. | Cost savings on legacy debt. |
| Retain | Keeping applications on-premises for now. | High-latency or compliance needs. |
| Rehost | "Lift-and-shift" without changes. | Speed, large-scale migrations. |
| Relocate | Moving VMware/containers to AWS without changes. | VMware Cloud on AWS. |
| Replatform | "Lift-and-reshape" (e.g., move to Managed RDS). | Reducing operational overhead. |
| Refactor | Re-architecting for cloud-native features. | High performance/scalability. |
| Repurchase | Moving to a different product (e.g., SaaS). | Standard business functions. |
Hierarchical Outline
- Migration Assessment & Inventory
- AWS Application Discovery Service (ADS): Agent-based (deep data) vs. Agentless (VMware environment).
- Portfolio Assessment: Categorizing apps by complexity, business value, and technical fit.
- Tracking & Orchestration
- AWS Migration Hub: Integrates with ADS, MGN, and DMS.
- Status Tracking: Real-time visibility into server and database migration progress.
- Migration Tools for Execution
- AWS MGN: Block-level replication for servers.
- AWS DMS: Continuous data replication for databases.
- AWS SCT: Required for heterogeneous database moves (e.g., Oracle to Aurora).
Visual Anchors
Migration Lifecycle Flow
Migration Hub Connectivity
\begin{tikzpicture}[node distance=2cm, every node/.style={rectangle, draw, rounded corners, inner sep=5pt, text centered}] \node (hub) [fill=orange!20, font=\bfseries] {AWS Migration Hub}; \node (ads) [left of=hub, xshift=-2cm] {Application Discovery}; \node (mgn) [right of=hub, xshift=2cm] {Application Migration}; \node (dms) [below of=hub] {Database Migration}; \node (sct) [below of=ads] {Schema Conversion};
\draw[<->, thick] (ads) -- (hub);
\draw[<->, thick] (mgn) -- (hub);
\draw[<->, thick] (dms) -- (hub);
\draw[->, dashed] (sct) -- (dms) node[midway, right] {\tiny Mapping};\end{tikzpicture}
Definition-Example Pairs
- Heterogeneous Migration: A migration where the source and target database engines are different.
- Example: Converting a legacy on-premises IBM DB2 database to Amazon Aurora PostgreSQL using AWS SCT and DMS.
- Agentless Discovery: Collecting server metadata without installing software on the target OS.
- Example: Running the ADS Connector as a virtual appliance in a VMware vCenter environment to see CPU/RAM usage across 500 VMs.
- TCO (Total Cost of Ownership): Comparison of on-premises costs (hardware, power, cooling) vs. AWS costs.
- Example: Calculating that moving to AWS saves 30% annually by eliminating the need for a physical data center lease and hardware refresh cycles.
Worked Examples
Scenario: The Complex Database Move
Problem: A customer wants to migrate a 5TB Oracle database to AWS. They want to reduce licensing costs by moving to PostgreSQL, but the database uses complex stored procedures.
Step-by-Step Breakdown:
- Assess: Run the AWS SCT Assessment Report. This identifies that 80% of the code is convertible automatically, but 20% (the complex procedures) requires manual rewriting.
- Convert: Use SCT to generate the target schema in Amazon RDS for PostgreSQL.
- Migrate: Use AWS DMS with an "ongoing replication" task. This performs the Full Load of the 5TB and then keeps the target in sync via Change Data Capture (CDC).
- Track: Register the project in AWS Migration Hub to monitor the status of the migration task across different environments (Dev, Test, Prod).
Checkpoint Questions
- Which tool is specifically required if you are migrating an SQL Server database to Amazon Redshift?
- True or False: AWS Migration Hub can track migrations even if you use third-party migration tools.
- What is the main difference between ADS Agentless and Agent-based discovery?
- Which of the 7Rs involves the least amount of effort and architectural change?
[!NOTE] Answers: 1. AWS SCT (for schema conversion); 2. True (it provides an API for integration); 3. Agent-based provides deep process-level data and network dependencies; Agentless provides VM-level metadata; 4. Rehost (Lift-and-Shift).
Muddy Points & Cross-Refs
- SCT vs. DMS: Students often confuse these. Remember: SCT is for the "Container" (schema/code), while DMS is for the "Content" (data).
- Migration Hub vs. Control Tower: Migration Hub tracks the migration process; Control Tower is for landing zone governance and account setup.
- Further Study: Check the "AWS Prescriptive Guidance" on Migration Wave Planning to understand how to use ADS data to group applications.
Comparison Tables
Migration Execution Tool Comparison
| Feature | AWS MGN | AWS DMS | AWS DataSync |
|---|---|---|---|
| Primary Use | Server Rehosting (Lift-and-Shift) | Database Migration/Replication | File & Object Data Transfer |
| Source Types | Physical, VMware, Hyper-V, Cloud | RDBMS, NoSQL, S3 | NFS, SMB, S3, HDFS |
| Mechanism | Continuous Block-Level Replication | CDC (Change Data Capture) | Periodic Syncing of Files |
| Downtime | Minimal (Cutover window) | Minimal (Near-zero) | Dependent on file size/sync |