Perform a side-by-side upgrade in AWS DMS by moving tasks to minimize business impact
Database Blog
This article provides a guide on how to upgrade the AWS Database Migration Service (DMS) version while minimizing business impact by moving replication tasks to a new DMS instance with the desired version.
Specifically, the article covers:
- Different AWS DMS version upgrade options, such as in-place upgrade, using recovery checkpoints, AWS DMS Serverless, and the side-by-side upgrade approach
- Step-by-step instructions on performing a side-by-side upgrade using the AWS CLI, console, and API
- Considerations and potential issues during the upgrade process, like handling task state changes and failed moves
- Best practices for a successful AWS DMS version upgrade, including testing, monitoring, data validation, and error handling
- Conclusion highlighting the benefits of the side-by-side upgrade approach for minimizing downtime and business impact
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Apr 21
2025
2025
Best practices to handle AWS DMS tasks during PostgreSQL upgrades
Apr 1
2024
2024
Accelerate your database migration journey using AWS DMS Schema Conversion
May 7
2024
2024
Minimize downtime when migrating your Oracle database to Amazon RDS for Oracle with transportable tablespaces and AWS DMS
May 13
2024
2024
AWS DMS best practices for moving large tables with table parallelism settings
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.