Community OpenAPI document · agent-readyCloud InfrastructureComputeapiKey17 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Track progress, status, and artifacts of an AWS migration across multiple tools by reporting and querying migration tasks, discovered resources, and application state.
Use for: I need to register a custom migration tool's progress in Migration Hub, Import a migration task for a server being moved to AWS, Update the status of an in-progress migration task, List all migration tasks in a progress update stream
Not supported: Does not perform server replication, schema conversion, or data movement. Use for migration progress tracking and artifact reporting only.
AWS Migration Hub provides a single place to track the progress of application migrations into AWS across multiple migration tools, including Application Migration Service, Database Migration Service, partner tooling, and custom scripts. The API lets a tool register progress update streams, import migration tasks, associate discovered resources and created artifacts, and report task and application state. Migration Hub itself does not move workloads; it aggregates the operational signal from the tools that do.
Install Jentic One Beta
Connect the AWS Migration Hub to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Migration Hub, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Fawsmigrationhub" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Fawsmigrationhub" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AWS Migration Hub API.
Create and delete progress update streams that namespace migration data per migration tool
Import migration task records and update their status as workloads move
Associate discovered resources with migration tasks so Migration Hub knows which servers each task covers
Associate created artifacts (AMIs, EBS volumes, CloudFormation stacks) with the migration task that produced them
Set application migration state to track which business applications are not started, in progress, or completed
List migration tasks across streams and applications, filtered by status and resource
Notify Migration Hub about ongoing task heartbeats so the dashboard reflects current activity
Use Cases
Patterns agents use AWS Migration Hub API for, with concrete tasks.
★ Custom Migration Tool Reporting
Surface a homegrown migration script's progress in the same Migration Hub dashboard the central program team watches. Call CreateProgressUpdateStream once for the tool, then ImportMigrationTask plus NotifyMigrationTaskState for every server the script handles. Migration Hub renders the tasks alongside Application Migration Service and Database Migration Service tasks, giving the program manager one pane of glass.
Create a progress update stream named legacy-vmware-mover, then import a migration task for source server srv-prod-01 with status IN_PROGRESS and a 50 percent ProgressUpdateTime.
Application Roll-Up Reporting
Group server-level migration tasks under a business application so executives see migration status at the level they care about: Order Management is 60 percent migrated rather than a list of EC2 instances. Use NotifyApplicationState with values NOT_STARTED, IN_PROGRESS, or COMPLETED to set rollup state, and ListApplicationStates to read it back.
Call NotifyApplicationState with ApplicationId=app-ordermgmt-01 and Status=IN_PROGRESS, then verify with ListApplicationStates filtered to that ApplicationId.
Artifact Traceability for Audit
Maintain an auditable record of every AWS resource that a migration task created, including AMI IDs, EBS snapshot IDs, and CloudFormation stack ARNs, so a future audit can prove which artifacts came from which on-prem source. Use AssociateCreatedArtifact each time the migration tool creates a resource, and ListCreatedArtifacts to retrieve the list per task.
Call AssociateCreatedArtifact on migration task task-srv-prod-01 with CreatedArtifact.Name set to ami-0abcdef and Description='Pre-cutover AMI snapshot taken 2026-06-01'.
Agent-Driven Migration Orchestrator
Let an agent supervise an in-flight migration wave: poll Migration Hub for tasks that have been IN_PROGRESS too long, retry failed tasks, and roll application state forward when all servers under it complete. The agent calls Migration Hub through Jentic, so AWS credentials never leave the vault and the orchestration logic is portable across customer accounts.
Search Jentic for 'list migration tasks in progress', execute it with the relevant ProgressUpdateStream, and for any task without a status update in 24 hours call NotifyMigrationTaskState to mark it FAILED.
Key Endpoints
17 endpoints — aws migration hub provides a single place to track the progress of application migrations into aws across multiple migration tools, including application migration service, database migration service, partner tooling, and custom scripts.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=AWSMigrationHub.CreateProgressUpdateStream
Create a progress update stream for a tool
POST
/#X-Amz-Target=AWSMigrationHub.ImportMigrationTask
Import a migration task record
POST
/#X-Amz-Target=AWSMigrationHub.ListMigrationTasks
List migration tasks across streams
POST
/#X-Amz-Target=AWSMigrationHub.AssociateCreatedArtifact
Associate a created artifact with a task
POST
/#X-Amz-Target=AWSMigrationHub.AssociateDiscoveredResource
Link a discovered resource to a task
POST
/#X-Amz-Target=AWSMigrationHub.NotifyApplicationState
Set application migration state
POST
/#X-Amz-Target=AWSMigrationHub.DescribeMigrationTask
Get a single migration task
POST
/#X-Amz-Target=AWSMigrationHub.ListApplicationStates
List application states across applications
POST
/#X-Amz-Target=AWSMigrationHub.CreateProgressUpdateStream
Create a progress update stream for a tool
POST
/#X-Amz-Target=AWSMigrationHub.ImportMigrationTask
Import a migration task record
POST
/#X-Amz-Target=AWSMigrationHub.ListMigrationTasks
List migration tasks across streams
POST
/#X-Amz-Target=AWSMigrationHub.AssociateCreatedArtifact
Associate a created artifact with a task
POST
/#X-Amz-Target=AWSMigrationHub.AssociateDiscoveredResource
Link a discovered resource to a task
POST
/#X-Amz-Target=AWSMigrationHub.NotifyApplicationState
Set application migration state
POST
/#X-Amz-Target=AWSMigrationHub.DescribeMigrationTask
Get a single migration task
POST
/#X-Amz-Target=AWSMigrationHub.ListApplicationStates
List application states across applications
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AWS Migration Hub
- AI-Aware (B-)61/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility38
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
38
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
53%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AWS Migration Hub by hand means holding an access key ID and secret access key, computing an AWS Signature Version 4 signature per request, targeting the correct regional mgh host and X-Amz-Target action header, and handling retries yourself. Through Jentic you install once, import AWS Migration Hub from the API Directory, store the AWS access key once, and your agent calls it.
Permission scoping
Migration Hub sends the task, stream, and application identifiers in the request body rather than the URL path, so scope your agent by the operations it needs, such as importing a migration task or listing migration tasks. You choose which operations it may call, so state changes like notifying application state are not included unless you add them.
Credential isolation
Your AWS access key ID and secret access key are stored once, encrypted, by your own Jentic One instance, and the Signature Version 4 signature is computed at execution time. The raw keys never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'import a migration task' or 'list migration progress', and Jentic returns the matching AWS Migration Hub operation with its input schema so the agent calls the right action without crawling the AWS reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Migration Hub API through Jentic.
What authentication does the AWS Migration Hub API use?
All requests use AWS Signature Version 4 with an access key ID and secret access key in the Authorization header. Through Jentic, those credentials sit encrypted in the vault and signing is performed server-side, so the agent never holds the raw key material.
Does Migration Hub actually move my workloads?
No. Migration Hub aggregates progress reported by other tools: Application Migration Service, Database Migration Service, partner tools, and custom scripts. The actual lift-and-shift, replatforming, or schema conversion happens inside those tools; Migration Hub records and visualises their progress.
What region do I call Migration Hub from?
Each AWS account has a single Migration Hub home region. You must call all Migration Hub APIs in that region or you receive a HomeRegionNotSetException. Set the home region once with the AWS Migration Hub Config API before importing tasks.
How do I report a custom tool's migration progress through Jentic?
Search Jentic for 'create a progress update stream', then 'import a migration task'. Execute the two operations to register your tool and create a task entry, and follow up with NotifyMigrationTaskState as the workload progresses. Migration Hub then surfaces the data in the central dashboard.
Are there per-application rate limits?
Migration Hub uses standard AWS service throttling and returns ThrottlingException when exceeded; AWS does not publish a fixed per-second limit. Heartbeat-style updates should be batched rather than sent on every step to avoid throttling on long migrations.
Is AWS Migration Hub free to use?
Migration Hub itself has no separate charge. You pay only for the underlying migration tools (Application Migration Service, Database Migration Service, etc.) and any AWS resources they create.
Can I limit what my agent is allowed to do with the AWS Migration Hub API?
Yes. Because your Jentic One instance is self-hosted, your own rules decide which Migration Hub operations the agent may call, so you can grant read-only actions like ListMigrationTasks and DescribeMigrationTask while withholding write actions like ImportMigrationTask or AssociateCreatedArtifact. Migration Hub passes task, stream, and application identifiers in the request body rather than the URL path, so scoping is done at the operation level rather than by path pattern. State-changing calls such as NotifyApplicationState are not available to the agent unless you explicitly add them to its allowed set.
GET STARTED