AWS Database Migration Service
Browse all Amazonaws APIs61
AI ReadinessAI-Aware (B-)61/100
Agent-ready OpenAPI document · curated by JenticStorageDatabasehmac69 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision DMS replication instances, configure source and target endpoints, run replication tasks, and retrieve premigration assessment and Fleet Advisor data.
Use for: Create a replication instance sized for a 500GB migration, Configure an Oracle source endpoint and a PostgreSQL target endpoint, Start a replication task that runs a full load plus CDC, Stop a replication task that is no longer needed
Not supported: Does not handle ETL transformations, data warehousing query execution, or backup/restore - use for database-to-database migration and replication only.
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.
Install Jentic One Beta
Connect the AWS Database Migration Service to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Database Migration Service, 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%2Faws-dms" | 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%2Faws-dms" | 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 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
Inspect Fleet Advisor collectors and recommendations to plan migrations from on-premises inventory
Subscribe to event notifications via CreateEventSubscription so cutover and failure events feed downstream tooling
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
POST
/#X-Amz-Target=AmazonDMSv20160101.AddTagsToResource
Apply tags to DMS resources
POST
/#X-Amz-Target=AmazonDMSv20160101.CancelReplicationTaskAssessmentRun
Cancel a running assessment
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 Database Migration Service
- AI-Aware (B-)61/100
99
Foundational Compliance62
Developer Experience & Jentic Compatibility38
AI-Readiness & Agent Experience91
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
95%
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.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
48%
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
51%
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.
91
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
91%
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 Database Migration Service by hand means building SigV4 request signing, resolving the regional dms.{region}.amazonaws.com host, and handling the X-Amz-Target action dispatch plus AWS retries yourself. Through Jentic you install once, import Database Migration Service from the API Directory, store the AWS access keys once, and your agent calls it.
Permission scoping
DMS dispatches every action through a single endpoint with the operation named in the request, so scope the agent to the operations it needs, such as creating a replication task or running a premigration assessment. Destructive operations like deleting a replication instance or endpoint stay out of that set unless you add them.
Credential isolation
Your AWS access keys for DMS are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a DMS replication task' or 'run a premigration assessment', and Jentic returns the matching DMS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the AWS DMS API?
Yes. Because you self-host Jentic One, your own rules decide which DMS operations and AWS credentials the agent may use, and DMS dispatches every action through a single endpoint with the operation named in the request, so you can scope the agent to just the operations it needs, such as CreateReplicationTask or StartReplicationTaskAssessmentRun. Destructive operations like DeleteReplicationInstance and DeleteEndpoint stay outside that set unless you explicitly add them. The AWS access keys are held encrypted by your instance and injected only when a permitted request is signed, so the agent never sees the raw secret.
GET STARTED