AWS Migration Hub

Name: AWS Migration Hub API
Brand: AWS Migration Hub
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeapiKey17 EndpointsREST

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.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with AWS Migration Hub API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access key ID and secret access key for AWS Migration Hub are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing credentials and the raw IAM secrets never enter the agent context. Jentic computes the AWS Signature Version 4 signature server-side for every request.

Intent-based discovery

Agents search Jentic by intent (for example, 'import a migration task') and Jentic returns matching AWS Migration Hub operations with their input schemas, the correct AWS service endpoint, and the required IAM action, so the agent can invoke the right call without crawling the AWS docs.

Time to first call

Direct AWS Migration Hub integration: 1-3 days for AWS SDK setup, IAM role configuration, Sigv4 signing, and error handling. Through Jentic: under 1 hour, search, load schema, execute.

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.

AWS Migration Hub

Connect the AWS Migration Hub to your agent

Capabilities

Start building with AWS Migration Hub API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs