AWS DMS release notes
Following, you can find release notes for current and previous versions of AWS Database Migration Service (AWS DMS).
AWS DMS doesn't differentiate between major and minor versions when you enable Automatic version upgrade for your replication instance. DMS automatically upgrades the replication instance's version during the maintenance window if the version is deprecated.
Note that to upgrade your replication instance's version manually (using the API or CLI) from version 3.4.x to 3.5.x, you must set
the AllowMajorVersionUpgrade parameter to true. For information about the
AllowMajorVersionUpgrade parameter,
see
ModifyReplicationInstance in the DMS API documentation.
Note
The current default engine version for AWS DMS is 3.5.4.
The following table shows the following dates for active DMS versions:
The version's release date
The date after which you can't create new instances with the version
The date when DMS automatically updates instances of that version (the end-of-life (EOL) date)
| Version | Release date | No new instance date | EOL date |
|---|---|---|---|
| 3.6.1 | May 15, 2025 | TBD | TBD |
| 3.6.0 | December 27, 2024 | April 27, 2026 | July 27, 2026 |
| 3.5.4 | November 15, 2024 | January 31, 2027 | March 31, 2027 |
| 3.5.3 | May 17, 2024 | February 28, 2026 | June 30, 2026 |
| 3.5.2 | October 29, 2023 | March 30, 2025 | April 29, 2025 |
| 3.5.1 | June 30, 2023 | November 30, 2024 | March 15, 2025 |
| 3.4.7 | May 31, 2022 | September 30, 2024 | October 31, 2024 |
| 3.4.6 | November 30, 2021 | September 30, 2024 | October 31, 2024 |
AWS DMS 3.6.1 default engine and support timeline
We will make AWS DMS version 3.6.1 the default engine version. We have not yet scheduled the no-new-instance date and end-of-life (EOL) date for version 3.6.1, so they appear as TBD in the preceding table. We update the table after we schedule these dates. To provide a migration window to version 3.6.1, we extended the support timeline for version 3.5.4. The no-new-instance date is now January 31, 2027, and the EOL date is March 31, 2027.
AWS DMS 3.6.0 regional availability
AWS DMS version 3.6.0 is currently available in Asia Pacific (Sydney): ap-southeast-2 region.
AWS Database Migration Service 3.6.1 release notes
| New feature or enhancement | Description |
|---|---|
| DMS Data Resync | AWS DMS automatically fixes data inconsistencies identified through data validation between your source and target databases. The data resync feature is supported for Oracle and SQL Server as a source and PostgreSQL as a target databases. |
| IAM database authentication for MariaDB, MySQL, and PostgreSQL |
Introduced support connecting to Amazon RDS and Aurora MariaDB, MySQL, and PostgreSQL endpoints through AWS Identity and Access Management (IAM) database authentication. With this enhancement you can use IAM to centrally manage access to your database resources, instead of managing access individually on each database endpoint. |
| PostgreSQL Read Replica Support for Change Data Capture (CDC) Replication | AWS DMS supports using PostgreSQL read replicas as source endpoints for Change Data Capture (CDC) replication, available with PostgreSQL version 16.x and later, starting with AWS DMS version 3.6.1. This feature allows you to leverage read replicas for CDC tasks. For more information, see Using a PostgreSQL database as an AWS DMS source. |
| Enhanced logging for missing target columns | Enhanced logging to inform customers about missing target table columns at default logging level. This improvement changes the logging level from VERBOSE to WARNING, making column discrepancy notifications more visible without requiring detailed debug settings. |
| SQL Server Binary(16) to PostgreSQL UUID migration | Added support for migrating SQL Server Binary(16) data types to PostgreSQL UUID format. This enables seamless conversion of binary GUID data to native UUID types, improving data type compatibility between SQL Server and PostgreSQL endpoints. |
| Amazon DocumentDB CDC start position | Added support for specifying a change data capture (CDC) start position for Amazon DocumentDB 3.6.0 sources. |
| PostgreSQL UUID primary key validation | Added support for data validation of tables that use a PostgreSQL UUID column as the primary key. |
AWS DMS version 3.6.1 includes the following resolved issues:
| Resolved Issue | Description |
|---|---|
| Selection rules filtering with data masking issue | Table selection rule filters now work correctly with data masking transformation rules. The fix ensures proper filtering when data masking transformations are applied. |
| PostgreSQL target unbound numeric handling issue |
PostgreSQL target endpoints can handle unbound numeric data types through optimized memory allocation. This prevents task failures when migrating tables with large numeric values. |
| Amazon Redshift target LOB handling issue | Redshift target endpoints now maintain LOB data integrity during high-volume parallel migrations. The improved LOB handling prevents data corruption when using parallel apply threads. |
| Transformation rules metadata issue |
Fixed an issue with expressions in transformation rules that were incorrectly applied. |
| Metadata table drop and recreate issue | Replication tasks now resume successfully when source tables are dropped and recreated during task stoppage. Improved metadata handling and status synchronization for recreated source tables. |
SQL Server AlwaysOn primary replica issue |
Improved primary replica detection for SQL Server sources in
AlwaysOn configurations by handling case sensitivity
variations. |
| MySQL source TIME data type handling issue | Resolved migration issues with TIME values containing fractions and
hours exceeding 24 when loadUsingCSV is disabled. |
| Data validation NUL character handling issue | Data validation now handles NUL (0x00) characters correctly without failing. Improved validation processing for data containing NUL characters. |
| SQL Server data validation issue | Resolved validation comparison issues with
UNIQUEIDENTIFIER columns for SQL Server
sources. |
| Table pre-load validation issue | AWS DMS tasks now complete validation successfully when tables are in pre-load phase during CDC replication. |
| Oracle source logging issue | Oracle source error logs now display the correct SQL statement during timezone query execution. Improved logging accuracy for better troubleshooting capabilities. |
| SQL Server driver update | SQL Server driver support is updated from ODBC 17 to ODBC 18. |
| DB2 empty strings CDC migration issue | Resolved an issue where empty VARCHAR values from IBM DB2 LUW source databases were incorrectly captured as NULL values instead of empty strings during Change Data Capture (CDC) operations. |
| Oracle LOB lookup memory leak issue | Fixed memory leak in Oracle source endpoints during LOB lookups when full LOB mode is enabled. This prevents continuous memory growth and out-of-memory failures during replication tasks with LOB data. |
| Redshift CDC boolean column mapping issue | Redshift target endpoints now correctly map new boolean columns added during CDC when MapBooleanAsBoolean is enabled. This maintains data type consistency with PostgreSQL sources instead of creating varchar columns. |
| PostgreSQL UUID array inline LOB migration issue | PostgreSQL source endpoints now correctly migrate UUID array data types when inline LOB mode is enabled. |
| Data validation nullable column diff reporting issue | Data validation now correctly reports mismatch details for nullable columns. |
| SQL Server to Oracle validation filtering issue | Data validation now correctly formats date filter conditions for Oracle target endpoints when using SQL Server sources. |
| DO_NOTHING mode table creation warning message | Added warning log message when AWS DMS automatically creates target tables in DO_NOTHING mode. This improves visibility and helps users identify when tables are created despite selecting a mode that implies no automatic table creation. |
| SQL Server BIT to PostgreSQL SMALLINT conversion issue | Fixed SQL Server BIT to PostgreSQL SMALLINT conversion during CDC operations. |
| S3 cross-account bucket access validation issue | Enhanced S3 bucket ownership validation to improve security when using S3 as a migration target or source. |
| Redshift endpoint reconnection and initialization issue | Redshift endpoints now properly reconnect after connection termination and correctly validate credentials during initialization. This prevents "Server name must be supplied" errors and task failures during recovery. |
| Data validation memory leak issue | Fixed memory leak in data validation. This prevents out-of-memory failures during long-running validation tasks. |
| SQL Server CHAR primary key validation false positive issue | Fixed false positive MISSING_TARGET errors when validating SQL Server to PostgreSQL migrations with CHAR/NCHAR primary keys containing trailing spaces. |
| S3 validation Athena database conflict issue | Fixed race condition when multiple tasks share S3 endpoints by isolating Athena databases per task. |
| PostgreSQL target bulk-load security hardening | Improved the security of the PostgreSQL target bulk-load path. AWS DMS now runs the load utility directly rather than through a command shell, and validates connection-script and object-identifier inputs before use. |
| Amazon S3 extra connection attributes issue | Fixed an issue for Amazon S3 endpoints where non-supported extra connection attributes could be applied. Only supported settings are now used. |
| Amazon S3 resume folder path issue | Fixed an issue for Amazon S3 sources where resuming a task could misidentify the table name when the folder path contained a date partition, causing data to be read from the wrong location. |
| Amazon S3 empty string handling issue | Fixed an issue for change data capture to Amazon S3 where empty string values were written as NULL. |
| Amazon S3 orphaned CDC file retry issue | Fixed an issue for Amazon S3 sources where retries of orphaned CDC data files were not limited to the configured bucket folder. |
| Amazon DocumentDB/MongoDB capture crash issue | Fixed an issue for Amazon DocumentDB/MongoDB sources where change capture could stop unexpectedly. |
| Amazon DocumentDB/MongoDB change stream filter issue | Fixed an issue for Amazon DocumentDB/MongoDB sources where change stream filtering did not handle escaped wildcard characters in table names. |
| Amazon DocumentDB/MongoDB CDC latency metric issue | Fixed an issue where the CDCLatencySource metric reported inflated source latency during idle periods. |
| Amazon DocumentDB/MongoDB empty post-image issue | Fixed an issue where an empty change-stream post-image could cause the task to stop unexpectedly. |
| Amazon DocumentDB empty field name issue | Fixed an issue for Amazon DocumentDB targets where rows with NULL or empty-string columns produced an "Empty field name" error. |
| Oracle NULL column handling issue | Fixed an issue for Oracle sources where buffer management for NULL columns could cause data errors or task failures. |
| Oracle LogMiner rollback reconnect issue | Fixed an issue for Oracle sources using LogMiner where an empty ROLLBACK could cause a repeated reconnect loop. |
Oracle all-NUL CHAR validation issue |
Fixed an issue for Oracle-to-PostgreSQL migrations where data validation reported a false positive for Oracle CHAR columns containing only NUL (CHR(0)) characters. |
| Oracle archived redo log probe issue | Fixed an issue for Oracle sources where archived redo log probing could reduce CDC reliability. |
| Oracle disconnect handling issue | Fixed an issue for Oracle sources where the task could report errors at shutdown because internal threads were not stopped before disconnecting. |
| Oracle array binding overflow issue | Fixed an issue for Oracle sources where an integer overflow during array binding could abort the task. |
| PostgreSQL WAL stream shutdown issue | Fixed an issue for PostgreSQL sources where the task could stop unexpectedly at the tail of the write-ahead log (WAL) stream during shutdown. |
| PostgreSQL timeout error logging update | Improved error logging for PostgreSQL timeout and termination errors (SQLSTATE 57P01/57014) to aid troubleshooting. |
| PostgreSQL logical replication set name issue | Fixed an issue for PostgreSQL sources using logical replication where an internal replication set name could be truncated because its buffer did not account for the name prefix and null terminator. |
| Amazon Redshift batch apply issue | Fixed an issue for Amazon Redshift targets where batch-apply CDC could fail with an XX000 equijoin predicate error after a task moved to a new replication instance. |
| Amazon Redshift net-changes table issue | Fixed an issue for Amazon Redshift targets where quoted object names were not handled when dropping the intermediate net-changes table. |
| Amazon Redshift parallel load error issue | Fixed an issue for Amazon Redshift targets where parallel full-load COPY errors were not propagated to the task, which could result in data loss. |
| Amazon Redshift long object name issue | Fixed an issue for Amazon Redshift targets where metadata retrieval failed for object names longer than 63 characters. |
| Amazon Redshift CDC file naming issue | Fixed an issue for Amazon Redshift targets where CDC data file naming could cause a column mismatch. |
| SQL Server source connection issue | Fixed an issue for SQL Server sources where the auxiliary connection could be built with an invalid ODBC driver name, causing the task to fail to connect. |
| SQL Server error 8134 handling issue | Fixed an issue for SQL Server sources where error 8134 (divide by zero) was not classified as a table-level error, causing full-load retry loops. |
| Db2 LUW cached change issue | Fixed an issue for Db2 LUW sources where a cached change update could affect 0 rows. |
| Db2 LUW LOAD utility path issue | Fixed an issue for Db2 LUW targets where the LOAD utility path was not resolved because the DB2INSTANCE/INSTHOME environment was not set for the task. |
| SAP ASE password validation update | Added validation of the SAP ASE endpoint password for source and target endpoints. |
| Replication process shutdown issue | Fixed an issue where the replication process could stop unexpectedly during shutdown. |
| Partition ID warning log update | Removed a spurious partition-ID warning that appeared in task logs. |
| Full-load reload completion issue | Fixed an issue where a full-load table could be marked complete while it was still queued for reload. |
| Missing primary key handling issue | Fixed an issue where a data record missing primary key columns could cause the task to hang. |
| Mixed-case TRUNCATE issue | Fixed an issue where TRUNCATE was not handled correctly for mixed-case schema and table names. |
| Partition warning log update | Reduced the log severity of the "Could not find any partition" message from Error to Warning. |
| Out-of-scope table creation issue | Fixed an issue where CREATE TABLE operations were processed for tables outside the task's selection scope. |
| Transaction record memory leak issue | Fixed an issue where transaction records could cause a memory leak. |
| Concurrent statement handling issue | Fixed an issue where concurrent statements on an internal connection could cause statement corruption. |
AWS Database Migration Service 3.6.0 release notes
| New feature or enhancement | Description |
|---|---|
| New metadata variables for transformations | Introduced two new metadata variables for transformation rules: $AR_M_MODIFIED_SCHEMA and $AR_M_MODIFIED_TABLE_NAME. These variables allow you to create more dynamic and flexible transformations that can adapt to schema or table name changes during your migration process. |
| Support for LOB Column Replication in UPSERT Error-Handling Mode |
Introduced support for replication of Large Object (LOB) columns when using the "No record found for applying an UPDATE: Insert the missing target record" error-handling option. With this enhancement, you can now accurately replicate LOB columns, ensuring complete and accurate data replication. |
AWS DMS version 3.6.0 includes the following resolved issues:
| Resolved Issue |
|---|