AWS Migration Hub: Comprehensive SAA-C03 Study Guide
AWS Migration Hub provides a single location to track the progress of application migrations across multiple AWS and partner solutions. It doesn’t perform the migration itself; rather, it acts as the “Command Center” for your cloud transition.
The Analogy: The Airport Control Tower
Think of AWS Migration Hub as an Airport Control Tower. The tower doesn’t fly the planes (those are the migration tools like AWS MGN or SMS), and it doesn’t pack the suitcases (AWS Application Discovery Service). Instead, it provides a centralized dashboard where controllers can see every flight’s status, whether it’s taxiing, taking off, or has landed safely at the destination. Without the tower, you’d have to call every pilot individually to know where your fleet is.
Core Concepts & Well-Architected Framework
What and Why?
- What: A central dashboard that integrates with AWS Application Discovery Service, AWS Migration Strategies (Refactor, Rehost, etc.), and migration tools.
- Why (Operational Excellence): It provides visibility. In the AWS Well-Architected Framework, visibility is key to operational excellence. Migration Hub allows teams to identify bottlenecks in the migration pipeline across different portfolios.
- Why (Performance Efficiency): By tracking all migrations in one place, you can quickly see which applications are lagging and reallocate resources to maintain migration velocity.
Comparison of Migration Discovery & Tracking Tools
| Service | Primary Function | Key Benefit | Cost Aspect |
|---|---|---|---|
| Migration Hub | Central Tracking & Orchestration | Single pane of glass for all tools | Free (pay for integrated tools) |
| Application Discovery Service | Data Gathering (On-prem) | Identifies dependencies/usage | Free (usage limits apply) |
| Application Migration Service (MGN) | Rehosting (Lift-and-Shift) | Automated block-level replication | Free for first 2,160 hours per server |
| Database Migration Service (DMS) | Database Migration | Minimal downtime for DB moves | Pay for replication instances |
Scenario-Based Learning: Decision Matrix
If/Then Strategy
- If you need to visualize the dependencies between your on-premises servers then use AWS Application Discovery Service (integrated with Migration Hub).
- If you are using multiple tools (MGN, DMS, and 3rd party) and need a unified status report then use AWS Migration Hub.
- If you need to determine the best migration strategy (R-type) for your portfolio then use Migration Hub Strategy Recommendations.
- If you want to automate the migration of a large number of physical, virtual, or cloud servers then use AWS Application Migration Service (MGN).
Exam Tips: Golden Nuggets
- The “One Region” Rule: Migration Hub is a global service endpoint, but you must choose a home region. Once set, it cannot be changed. All migration data is stored in this region.
- Visibility Only: Remember that Migration Hub tracks progress; it is not the tool that performs the actual data transfer (that’s MGN, DMS, or DataSync).
- Discovery Requirement: To track an application, it must first be “discovered” or “imported” into the Migration Hub inventory.
- Distractor Alert: If a question asks for a tool to *move* data, don’t pick Migration Hub. If it asks to *track* the move, Migration Hub is the answer.
AWS Migration Hub Architecture
Centralized Tracking for Cloud Transformation
Flow: Discover & Inventory → Strategy Recommendation → Migrate → Track Status
Key Services
Integrates with Application Discovery Service (Agentless or Agent-based) to map server dependencies and performance data.
Common Pitfalls
Forgetting to set the Home Region. If you don’t set it, you can’t start tracking, and it’s permanent once chosen.
Quick Patterns
Rehost (Lift & Shift): Use MGN + Migration Hub.
Replatform: Use DMS + Migration Hub to track DB moves.