AWS Migration Hub

AWS Migration Hub provides a central console and API to track migration progress and inventory across AWS migration services and supported third-party tools. It aggregates status and discovery metadata from integrated discovery and migration tools so teams can view application and server migration progress in one place. It normally sits alongside discovery and migration tools rather than performing data transfer itself.

🗂 Resource Category

Migration and Transfer • Management and Governance

🧠 Exam Memory Hook

Think: "Central tracking + multiple migration tools + single console = AWS Migration Hub"

📖 Ownership

Classification: AWS Managed Service

AWS responsibilities: AWS operates and manages the Migration Hub control plane, console, APIs, and the underlying service platform and infrastructure; AWS secures and patches the service platform and physical infrastructure; AWS maintains service availability and the integration endpoints for supported AWS services.

Customer responsibilities: The customer configures IAM permissions, service integrations, and the Migration Hub application grouping and labels; the customer deploys and configures discovery agents (when used), configures and runs migration tools (for example AWS Application Migration Service or AWS Database Migration Service), monitors migration progress in the console, and secures and maintains source and target resources and data.

Patching responsibilities: AWS patches and maintains the underlying physical infrastructure, control plane, and managed service platform for Migration Hub. The customer is responsible for patching guest operating systems, installed runtimes, application libraries, dependencies, and customer-deployed applications on source and target servers; Migration Hub does not patch tracked resources.

🏗 Typical Architecture

💡 Top 5 Features

Centralized tracking of migration progress and status across multiple AWS and supported third-party migration tools.
Aggregates discovery metadata and migration task status so teams can view application- and server-level migration progress in one console.
APIs and integration points that allow migration tools and third-party products to push status and metadata into the hub.
Supports grouping of resources into applications or migration waves to simplify progress reporting and coordination.
Works with Migration Hub Orchestrator and native migration services to provide an operational view without performing data transfer itself.

✅ Top 5 Use Cases

Provide a single-pane-of-glass for tracking progress of large-scale server and application migrations that use multiple AWS migration tools.
Aggregate discovery metadata from AWS Application Discovery Service to help plan and prioritize migration waves and timelines.
Coordinate and report status for database migration projects where AWS Database Migration Service performs the data movement and Migration Hub tracks state.
Share migration status information with stakeholders and operations teams without giving direct access to each migration tool.
Integrate third-party migration tools with AWS by sending progress and inventory to a central tracking console.

🏗 Architecture Placement

Migration Hub sits as a management and tracking layer that receives status and discovery metadata from discovery and migration tools; migration tools and discovery agents send updates to the hub, and it provides a consolidated view for operators and stakeholders. It does not perform the migrations itself but references migration activity from services that perform the transfer. Placement is typically at the account-level console where operators and project managers view aggregated migration state.

🎯 Commonly Used With

- AWS Application Discovery Service
- AWS Application Migration Service
- AWS Database Migration Service
- AWS Migration Hub Orchestrator
- Amazon CloudWatch

🌍 5 Real-World Examples

A bank uses AWS Application Discovery Service to inventory on-premises servers and AWS Migration Hub to track which application waves have completed lift-and-shift migrations using AWS Application Migration Service.
A healthcare provider uses AWS Database Migration Service for continuous replication and uses Migration Hub to report migration status to compliance and operations teams.
A retail company coordinates a multi-team data center exit by grouping applications in Migration Hub so migration managers can monitor wave-by-wave progress.
A government IT organization standardizes reporting by integrating third-party migration tools with Migration Hub to produce a single migration status dashboard for stakeholders.
A technology company uses Migration Hub alongside Migration Hub Orchestrator to coordinate automated runbooks and to track orchestration progress across teams.

🎓 AWS Exam Clues

Used when you need centralized visibility of migration progress across multiple migration and discovery tools rather than performing the migration itself.
Integrates with discovery and migration services to aggregate status, so questions mentioning aggregation of migration status point to Migration Hub.
Choose Migration Hub when operational tracking, grouping by application or wave, and cross-tool reporting are required.
Not a data transfer service—if the question focuses on schema conversion or data replication the correct service may be DMS or Application Migration Service instead.
Requires customers to configure integrations and permissions; exam scenarios that mention permissions, agents, or integration setup are relevant to Migration Hub.

📝 Quick Revision

AWS Migration Hub is a central tracking and aggregation console for migration progress across AWS and supported third-party tools. Use it when you need a single view of discovery and migration status; remember it does not perform transfers and requires configuration of migration tools, agents, and IAM permissions.

🏷 Keywords

migration tracking • migration inventory • application discovery • migration progress • migration waves • Migration Hub Orchestrator • integration APIs • migration status • discovery metadata • application grouping • third-party integration • cross-account tracking