AWS Migration Hub Config

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

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputehmac3 EndpointsREST

For Agents

Set, describe, and list the AWS Migration Hub home region that aggregates migration status across tools.

Connect the AWS Migration Hub Config to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Migration Hub Config, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 Config API.

Create a Migration Hub home region control for the calling AWS account

Describe one or more existing home region controls to confirm setup

Retrieve the currently active home region for the account

Filter DescribeHomeRegionControls results by control ID, target, or home region

GET STARTED

Start building with AWS Migration Hub Config API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Migration Hub Config, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Migration Hub Config, keeping it validated and agent-ready. AWS Migration Hub Config lets organisations declare and inspect the home region for their Migration Hub data — the single AWS region where status from migration tools such as Application Migration Service (MGN), Database Migration Service (DMS), and partner tools is aggregated. Setting the home region is the first step before any migration tool can publish progress to Migration Hub, and it is a one-time control-plane decision per AWS account.

Use Cases

Patterns agents use AWS Migration Hub Config API for, with concrete tasks.

★ Migration Programme Bootstrapping

Cloud architects starting a migration programme set the Migration Hub home region exactly once per account so all tooling — MGN for servers, DMS for databases, partner tools — aggregates status into the same region. CreateHomeRegionControl records the choice; subsequent tools call GetHomeRegion at startup to know where to publish data. Choosing this early prevents fragmented reporting later in the programme.

Call CreateHomeRegionControl with HomeRegion='eu-west-1' and Target object specifying the AWS account ID, then call GetHomeRegion to confirm the value sticks

Multi-Account Home Region Auditing

Operators running migrations across many member accounts in an AWS Organisation use DescribeHomeRegionControls with filters to verify each account's home region matches the programme standard. The control-plane response shows the ControlId, HomeRegion, Target, and RequestedTime for each control, making it straightforward to flag accounts whose home region has not been configured yet.

Call DescribeHomeRegionControls with no filters, then iterate the HomeRegionControls array and flag any entries where HomeRegion does not equal 'eu-west-1'

Home Region Verification Before Tool Invocation

Migration automation that triggers MGN cutovers, DMS replication, or Server Migration Service jobs should call GetHomeRegion first to ensure the chosen home region is set. A missing home region causes downstream tools to fail with a configuration error, so a guard call here surfaces the problem before a long-running migration job is started.

Call GetHomeRegion and abort the migration job if HomeRegion is empty, returning an actionable error that the home region must be configured first

AI Agent Migration Onboarding

AI agents call Migration Hub Config through Jentic when onboarding a new account into an existing migration programme — they call CreateHomeRegionControl idempotently to align the account, then verify with DescribeHomeRegionControls. Jentic isolates the AWS access keys and exposes the three Migration Hub Config operations as discoverable tools, so the agent can answer 'set home region for account X' without learning the AWS SDK.

Search Jentic for 'set migration home region', load CreateHomeRegionControl, and execute it with HomeRegion='eu-west-1' and Target.Type='ACCOUNT' and Target.Id set to the account ID

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for aws migration hub config, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AWSMigrationHubMultiAccountService.CreateHomeRegionControl

Create a home region control for an account

POST

/#X-Amz-Target=AWSMigrationHubMultiAccountService.DescribeHomeRegionControls

Describe existing home region controls

POST

/#X-Amz-Target=AWSMigrationHubMultiAccountService.GetHomeRegion

Get the active home region for the account

POST

/#X-Amz-Target=AWSMigrationHubMultiAccountService.CreateHomeRegionControl

Create a home region control for an account

POST

/#X-Amz-Target=AWSMigrationHubMultiAccountService.DescribeHomeRegionControls

Describe existing home region controls

POST

/#X-Amz-Target=AWSMigrationHubMultiAccountService.GetHomeRegion

Get the active home region for the account

Why though Jentic?

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

Credential isolation

AWS keys are stored encrypted in the Jentic vault. Migration Hub Config calls are signed with Signature Version 4 server-side, and IAM scoping restricts the agent to the three migrationhub-config actions only.

Intent-based discovery

Agents search by intent (e.g. 'set migration home region' or 'check migration home region') and Jentic returns the three Migration Hub Config operations with their input schemas, so the agent picks the right one without browsing AWS docs.

Time to first call

Direct integration: a few hours at most given the small surface area. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Migration Hub

Migration Hub Config sets the home region; Migration Hub aggregates migration data into it

Use Migration Hub Config first to set the home region; use Migration Hub afterwards to aggregate and view migration progress across tools.

Complementary

AWS Application Migration Service

MGN reports progress into the home region defined by Migration Hub Config

Use Migration Hub Config first; MGN and other migration tools then publish progress into the chosen region.

Complementary

AWS Database Migration Service

DMS publishes status into the home region set by Migration Hub Config

Use Migration Hub Config to ensure DMS task progress shows up in the same region as other migration tools.

FAQs

Specific to using AWS Migration Hub Config API through Jentic.

Why is there no official OpenAPI spec for AWS Migration Hub Config?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Migration Hub Config via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS Migration Hub Config API use?

The API uses AWS Signature Version 4 (HMAC) with an access key ID and secret access key scoped via IAM. The migrationhub-config namespace covers the three actions in this spec; no other permissions are required to set or read the home region. Through Jentic, the keys live in the encrypted vault and Jentic signs each request server-side.

Can I change the Migration Hub home region after it is set?

Once a home region control is created via CreateHomeRegionControl, the home region applies to the account and downstream Migration Hub tools depend on it. Changing it later requires a coordinated reset of migration data and is generally avoided — pick the region carefully at programme start. The API does not expose an UpdateHomeRegionControl operation.

What are the rate limits for the AWS Migration Hub Config API?

AWS does not publish hard request-per-second limits for these three operations in the spec. The API is called rarely — typically once per account at programme start and ad-hoc for verification — so throttling is not a practical concern at normal usage volumes.

How do I set the home region through Jentic?

Search Jentic for 'set migration home region' to surface CreateHomeRegionControl. Load the schema with the Jentic SDK (pip install jentic), then execute it with HomeRegion (e.g. 'eu-west-1'), Target.Type='ACCOUNT', and Target.Id set to the AWS account ID. Call GetHomeRegion afterwards to confirm the value persisted.

Is AWS Migration Hub Config free?

Yes — AWS Migration Hub and the Migration Hub Config API are free to use. You only pay for the underlying migration tools (MGN, DMS, Server Migration Service) and any AWS resources they create at standard rates.