canonical: https://jentic.com/apis/amazonaws.com/migrationhub-config

# AWS Migration Hub Config

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.

## For AI agents

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

## Scope

Does not handle migration progress, replication, cutover, or any tool-specific operations - use for choosing and inspecting the Migration Hub home region only.

## Capabilities

- 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
- Query the home region before invoking other Migration Hub tools
- Confirm that downstream migration tooling will report into the chosen region
- Tag and target controls at specific accounts when operating from a payer account

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **HomeRegionControls** — Records of the chosen home region per AWS account or target
- **HomeRegion** — The single AWS region where Migration Hub data is aggregated
- **Target** — The account or organisation entity the home region applies to

## Why Jentic

- **Setup:** Wiring AWS Migration Hub Config by hand means implementing Signature Version 4 signing, resolving the regional migrationhub-config host, and building the X-Amz-Target action headers yourself. Through Jentic you install once, import Migration Hub Config from the API Directory, store the AWS keys once, and your agent calls it.
- **Permission scoping:** Migration Hub Config is a JSON action API where the home-region control travels in the request body, so scope the agent to the operations it needs, such as GetHomeRegion and DescribeHomeRegionControls for read-only inspection. You choose the operations it may call, so CreateHomeRegionControl is not included unless you add it.
- **Credential handling:** Your AWS access keys are stored once, encrypted, by your own Jentic One instance and each request is signed with Signature Version 4 at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'set migration home region' or 'check migration home region', and Jentic returns the matching Migration Hub Config operation with its input schema, so the agent picks the right one without browsing the reference docs.

## Related APIs

- **AWS Migration Hub** — Migration Hub Config sets the home region; Migration Hub aggregates migration data into it
- **AWS Application Migration Service** — MGN reports progress into the home region defined by Migration Hub Config
- **AWS Database Migration Service** — DMS publishes status into the home region set by Migration Hub Config

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the AWS Migration Hub Config API?

Yes. Because you run Jentic One yourself, your own rules decide which of the three Migration Hub Config operations the agent may call and which AWS credentials it may use. For read-only inspection you can grant only GetHomeRegion and DescribeHomeRegionControls, so the agent can confirm the configured home region without changing it. CreateHomeRegionControl is not exposed unless you explicitly add it, keeping the one-time control-plane decision under operator control.