AWS · Cloud service
AWS Database Migration Service with OrchestrAI
Catalog exported 2026-09-02
Control AWS DMS replication tasks from chat: create, start, stop, and check status without the console.
OrchestrAI exposes 4 DMS operations: 1 is low-risk (read-only or low-impact), and 3 create or modify resources and run only after you confirm the plan. 3 of them also carry a step-level approval gate.
What teams use it for
Data teams use OrchestrAI during database migrations to create a replication task between existing endpoints, start it when the cutover window opens, watch its status and table statistics, and stop it if something looks wrong. Status checks are low risk, and create, start, and stop each wait for your confirmation. Replication instances and source or target endpoints are not covered, so those need to exist before you ask OrchestrAI to create a task.
Every DMS operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Get DMS Task Status |
Get AWS DMS replication task status | Low risk | No |
Create DMS Task |
Create AWS DMS replication task | Creates resources | Yes |
Start DMS Task |
Start AWS DMS replication task | Creates resources | Yes |
Stop DMS Task |
Stop AWS DMS replication task | Creates resources | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create a full-load-and-cdc DMS task from the legacy-mysql endpoint to the aurora-target endpoint on the migration-instance
- Start the orders-migration DMS task
- What is the status of the customers-cdc replication task and how many tables are loaded?
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI create DMS replication instances and endpoints?
- No, only replication tasks are covered. Create the instance and endpoints in the console first, then OrchestrAI can create, start, and stop tasks on them.
- Will OrchestrAI stop a DMS task without confirmation?
- No, stopping a task is medium risk and marked confirm, so it waits for your approval.
- Which DMS operations need an extra approval step?
- 3 operations carry a step-level approval gate on top of plan confirmation: Create DMS Task, Start DMS Task, Stop DMS Task. None of them is classed destructive.
Other AWS services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.