Explanation
Why the waste happens and who it affects.
Without active replication tasks, these instances no longer serve any purpose but continue to incur hourly compute costs. In large organizations or decentralized migration projects, these idle instances may go unnoticed, contributing to persistent background spend.
Billing model
The pricing dimensions that drive this cost.
- DMS Replication Instances are charged per hour of uptime, based on instance size
- Charges accrue even if no replication tasks are actively running
- Additional storage charges may apply for logs and cached data, but the bulk of cost comes from the instance itself
How to detect
4 checks to find it in your estate.
- List all DMS replication instances in the account or region
- Check whether each instance has active replication tasks associated with it
- Flag instances with zero tasks or tasks in a stopped or completed state
- Review instance creation and last activity timestamps to identify long-idle resources
How to fix
4 ways to remove the waste.
- Delete DMS replication instances that are no longer associated with active or planned tasks, after stopping and deleting their tasks; replication instances cannot be stopped, so deletion is the only way to end instance charges
- Tag replication instances by project or migration wave to enable future clean-up
- Incorporate DMS instance lifecycle checks into post-migration workflows
- Use infrastructure-as-code where possible to ensure temporary resources are cleaned up automatically
Documentation
Vendor references for pricing and configuration.