AWS Database Migration Service

Name: AWS Database Migration Service API
Brand: AWS Database Migration Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabasehmac69 EndpointsREST

For Agents

Provision DMS replication instances, configure source and target endpoints, run replication tasks, and retrieve premigration assessment and Fleet Advisor data.

Quickstart

Get started with AWS Database Migration Service in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a DMS replication task"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AWS Database Migration Service API.

Provision and tear down replication instances with CreateReplicationInstance and DeleteReplicationInstance sized to migration throughput

Define source and target endpoints for engines like Oracle, MySQL, PostgreSQL, SQL Server, and Aurora via CreateEndpoint

Start, stop, and resume replication tasks with StartReplicationTask, StopReplicationTask, and table-mapping JSON

Run premigration assessments to surface schema and data-type compatibility issues before cutover

GET STARTED

Start building with AWS Database Migration Service API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for AWS Database Migration Service, keeping it validated and agent-ready. AWS Database Migration Service (DMS) moves data between databases — homogeneous (Oracle to Oracle) or heterogeneous (Oracle to PostgreSQL) — with optional ongoing change-data-capture replication. The API covers the full migration lifecycle: replication instances, source and target endpoints, replication tasks, table mappings, premigration assessments, and Fleet Advisor inventory. Use it when an agent needs to orchestrate a migration plan, kick off a replication task, or pull assessment results back into a runbook.

Use Cases

Patterns agents use AWS Database Migration Service API for, with concrete tasks.

★ Plan and Execute a Heterogeneous Migration

Move an on-premises Oracle workload to Amazon Aurora PostgreSQL without long downtime. CreateEndpoint configures both source and target, CreateReplicationInstance provisions the worker, and CreateReplicationTask defines the table mappings and migration type (full load and CDC). The task runs a full load while change-data-capture replicates ongoing transactions until cutover.

Call CreateEndpoint twice (source Oracle, target Aurora PostgreSQL), CreateReplicationInstance with 100GB allocated storage, then CreateReplicationTask with MigrationType full-load-and-cdc.

Surface Schema Issues Before Cutover

Run StartReplicationTaskAssessmentRun to validate that the source schema converts cleanly to the target engine and surface unsupported data types or index strategies. The assessment results give the migration team a checklist of fixes — rebuilt CLOB columns, missing primary keys, function-based indexes — before kicking off the production migration.

Call StartReplicationTaskAssessmentRun on the configured task, poll DescribeReplicationTaskAssessmentRuns until status is COMPLETED, then DescribeReplicationTaskIndividualAssessments to surface failing checks.

Inventory On-Premises Databases with Fleet Advisor

Use CreateFleetAdvisorCollector and Fleet Advisor APIs to gather inventory from on-premises databases, then DescribeFleetAdvisorSchemaObjectSummary and recommendation operations to size and plan target environments. The output drives downstream DMS configuration without a manual discovery phase.

Call CreateFleetAdvisorCollector with the collector parameters, then DescribeFleetAdvisorSchemaObjectSummary to inspect the discovered schema.

Agent-Driven Migration Orchestration

An AI agent connected via Jentic can compose the full migration sequence — provision the replication instance, create endpoints, start the task, run assessments, and notify the team on completion — without writing AWS SDK glue. Jentic returns the matching DMS operation and schema so each step has a structured input contract and the agent can recover from validation errors.

Search Jentic for 'create a DMS replication task', load CreateReplicationTask, execute it with the source/target endpoints, replication instance ARN, and table mappings, then StartReplicationTask.

Key Endpoints

69 endpoints — jentic publishes the only available openapi specification for aws database migration service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateReplicationInstance

Provision a DMS replication instance

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateEndpoint

Define a source or target endpoint

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateReplicationTask

Create a replication task

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateReplicationSubnetGroup

Create a subnet group for the instance

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateEventSubscription

Create an SNS event subscription

POST

/#X-Amz-Target=AmazonDMSv20160101.AddTagsToResource

Apply tags to DMS resources

POST

/#X-Amz-Target=AmazonDMSv20160101.CancelReplicationTaskAssessmentRun

Cancel a running assessment

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateReplicationInstance

Provision a DMS replication instance

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateEndpoint

Define a source or target endpoint

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateReplicationTask

Create a replication task

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateReplicationSubnetGroup

Create a subnet group for the instance

POST

/#X-Amz-Target=AmazonDMSv20160101.CreateEventSubscription

Create an SNS event subscription

Why though Jentic?

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

Credential isolation

AWS access keys for DMS are stored encrypted in the Jentic vault. Jentic signs each DMS request with SigV4 at execution time and the agent only sees scoped, short-lived access — raw access keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create a DMS replication task' or 'run a premigration assessment') and Jentic returns the matching DMS operation with its input schema, so the agent can call the right endpoint without browsing AWS documentation.

Time to first call

Direct DMS integration: 3-7 days for SigV4 signing, multi-step lifecycle, table-mapping JSON, and assessment polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS RDS Data API

HTTP-based access to RDS targets that DMS migrates data into.

Choose RDS Data API when the agent needs to query or modify data on the RDS target after migration is complete.

Complementary

Amazon DocumentDB

Document database control plane often used as a DMS target.

Choose DocumentDB when migrating to a MongoDB-compatible target and the agent needs to manage the cluster itself.

Alternative

AWS Data Pipeline

General-purpose data movement and processing rather than database replication.

Choose Data Pipeline when the workload is batch ETL across heterogeneous sources rather than DB-to-DB migration.

FAQs

Specific to using AWS Database Migration Service API through Jentic.

Why is there no official OpenAPI spec for AWS Database Migration Service?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Database Migration Service 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 DMS API use?

DMS uses AWS Signature Version 4 (HMAC) signing with an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in the Jentic vault and are injected into signed requests at execution time, so the agent never sees the raw secret access key.

Can I run change-data-capture between two databases with this API?

Yes. Set MigrationType to cdc or full-load-and-cdc on CreateReplicationTask. DMS continuously replicates committed changes from the source endpoint to the target until the task is stopped, enabling near-zero-downtime cutover.

What are the rate limits for the AWS DMS API?

DMS shares standard AWS service quotas, which are managed per account and region rather than published as fixed per-second limits in the spec. Account-level limits also apply to the number of replication instances and tasks; ThrottlingException responses should trigger backoff.

How do I orchestrate a migration through Jentic?

Search Jentic for 'create a DMS replication task', load CreateReplicationTask, execute it with the source endpoint ARN, target endpoint ARN, ReplicationInstanceArn, and TableMappings JSON. Run pip install jentic and use the async search and execute pattern.

Does this API include the data conversion logic, or just the orchestration?

DMS itself performs both — it executes the replication and applies built-in data type conversion as part of running the task. The API exposes orchestration: defining endpoints, replication instances, and tasks, and starting and stopping them.