AWS DMS release notes - AWS Database Migration Service

AWS DMS release notes

Following, you can find release notes for current and previous versions of AWS Database Migration Service (AWS DMS).

AWS DMS uses a semantic versioning scheme to identify a service release. A version consists of a three-component number in the format of X.Y.Z where X represents an epic version, X.Y represents a major version, and Z represents a minor version (Epic.Major.Minor).

Note

You can upgrade any version of AWS Database Migration Service to AWS DMS version 3.4.4. The upgrade path to 3.4.5 is not available. To upgrade to AWS DMS version 3.4.5, create a new replication instance and move your replication tasks to the new instance. For information about moving tasks, see Moving a task.

To stay current with the latest features, enhancements, and performance improvements, upgrade to AWS DMS version 3.4.5.

AWS Database Migration Service 3.4.5 release notes

The following table shows the new features and enhancements introduced in AWS Database Migration Service (AWS DMS) version 3.4.5.

New feature or enhancement Description
Support for Redis as a target AWS DMS now supports Redis as a target. Using AWS DMS, you can now migrate live data from any AWS DMS supported source to a Redis data store, with minimal downtime. For information about AWS DMS targets, see Targets for data migration.
Support for MongoDB 4.2 and 4.4 as sources AWS DMS now supports MongoDB 4.2 and 4.4 as sources. Using AWS DMS, you can now migrate data from MongoDB 4.2 and 4.4 clusters to any AWS DMS supported target including Amazon DocumentDB (with MongoDB compatibility), with minimal downtime. For information about AWS DMS sources, see Sources for data migration.
Support for multiple databases using MongoDB as a source AWS DMS now supports migrating multiple databases in one task using MongoDB as a source. Using AWS DMS, you can now group multiple databases of a MongoDB cluster, and migrate them using one database migration task. You can migrate to any AWS DMS supported target, including Amazon DocumentDB (with MongoDB compatibility), with minimal downtime.
Support for automatic segmentation using MongoDB or Amazon DocumentDB (with MongoDB compatibility) as a source AWS DMS now supports automatic segmentation using MongoDB or Amazon DocumentDB as a source. Using AWS DMS, you can configure database migration tasks to segment the collection of a MongoDB or DocumentDB cluster automatically. You can then migrate the segments in parallel to any AWS DMS supported target, including Amazon DocumentDB, with minimal downtime.
Amazon Redshift full load performance improvement AWS DMS now supports using parallel threads when using Amazon Redshift as a target during full load. By taking advantage of the multithreaded full load task settings, you can improve the performance of your initial migration from any AWS DMS supported source to Amazon Redshift. For information about AWS DMS targets, see Targets for data migration.

The issues resolved in AWS DMS 3.4.5 include the following:

  • Fixed an issue where data could potentially be missing or duplicated after resuming, when using PostgreSQL as a source with high transaction concurrency.

  • Fixed an issue where database migration tasks fail with error Could not find relation id … when using PostgreSQL as a source, with the pglogical plugin enabled.

  • Fixed an issue where VARCHAR columns are not replicated correctly when using PostgreSQL as a source and Oracle as a target.

  • Fixed an issue where delete operations are not properly captured when the primary key is not the first column in the table definition, when using PostgreSQL as a source.

  • Fixed an issue where database migration tasks miss LOB updates in a special metadata setting when using MySQL as a source.

  • Fixed an issue where TIMESTAMP columns are treated as DATETIME in full LOB mode when using MySQL version 8 as a source.

  • Fixed an issue where database migration tasks fail when parsing NULL DATETIME records when using MySQL 5.6.4 and above as a source.

  • Fixed an issue where database migration tasks get stuck after encountering a Thread is exiting error when using Amazon Redshift as a target with parallel apply.

  • Fixed an issue where data could potentially be lost, when database migration tasks disconnect with a Amazon Redshift target endpoint during batch-apply CDC.

  • Improved the performance of full load by calling ACCEPTINVCHARS when using Amazon Redshift as a target.

  • Fixed an issue where duplicated records are replicated when reverting from one-by-one mode to parallel apply mode using Amazon Redshift as a target.

  • Fixed an issue where database migration tasks do not switch Amazon S3 object ownership to bucket owner with cannedAclForObjects=bucket_owner_full_control when using Amazon S3 as a target.

  • Improved AWS DMS by supporting multiple archive destinations with ECA additionalArchivedLogDestId when using Oracle as a source.

  • Fixed an issue where database migration tasks fail with error OCI_INVALID_HANDLE while updating a LOB column in full LOB mode.

  • Fixed an issue where NVARCHAR2 columns are not migrated properly during CDC when using Oracle as a source.

  • Improved AWS DMS by enabling SafeguardPolicy when using RDS for SQL Server as a source.

  • Fixed an issue where database migration tasks report error on rdsadmin when using a non-RDS SQL Server source.

  • Fixed an issue where data validation fails with UUID as the primary key in a partition setting when using SQL Server as a source.

  • Fixed an issue where full load plus CDC tasks might fail if the required LSN cannot be found in the database log when using Db2 LUW as a source.

  • Improved AWS DMS by supporting custom CDC timestamps when using MongoDB as a source.

  • Fixed an issue where database migration tasks get stuck when stopping, using MongoDB as a source, when the MongoDB driver errors on endSessions.

  • Fixed an issue where AWS DMS fails to update non-primary fields when using DynamoDB as a target

  • Fixed an issue where data validation reports false positive mismatches on CLOB and NCLOB columns.

  • Fixed an issue where data validation fails on whitespace-only records when using Oracle as a source.

  • Fixed an issue where database migration tasks crash when truncating a partitioned table.

  • Fixed an issue where database migration tasks fail when creating the awsdms_apply_exceptions control table.

  • Extended support of the caching_sha2_password authentication plugin when using MySQL version 8.

AWS Database Migration Service 3.4.4 release notes

The following table shows the new features and enhancements introduced in AWS DMS version 3.4.4.

New feature or enhancement Description
Support TLS encryption and TLS or SASL authentication using Kafka as a target AWS DMS now supports TLS encryption and TLS or SASL authentication using Amazon MSK and on-premises Kafka cluster as a target. For more information on using encryption and authentication for Kafka endpoints, see Connecting to Kafka using Transport Layer Security (TLS).

The issues resolved in AWS DMS 3.4.4 include the following:

  • Improved AWS DMS logging on task failures when using Oracle endpoints.

  • Improved AWS DMS task execution continues processing when Oracle source endpoints switch roles after Oracle Data Guard fail over.

  • Improved error handling treats ORA—12561 as a recoverable error when using Oracle endpoints.

  • Fixed an issue where EMPTY_BLOB() and EMPTY_CLOB() columns are migrated as null when using Oracle as a source.

  • Fixed an issue where AWS DMS tasks fail to update records after add column DDL changes when using SQL Server as a source.

  • Improved PostgreSQL as a source migration by supporting the TIMESTAMP WITH TIME ZONE data type.

  • Fixed an issue where the afterConnectScript setting does not work during a full load when using PostgreSQL as a target.

  • Introduced a new mapUnboundedNumericAsString setting to better handle the NUMERIC date type without precision and scale when using PostgreSQL endpoints.

  • Fixed an issue where AWS DMS tasks fail with “0 rows affected” after stopping and resuming the task when using PostgreSQL as a source.

  • Fixed an issue where AWS DMS fails to migrate the TIMESTAMP data type with the BC suffix when using PostgreSQL as a source.

  • Fixed an issue where AWS DMS fails to migrate the TIMESTAMP value “±infinity” when using PostgreSQL as a source.

  • Fixed an issue where empty strings are treated as NULL when using S3 as a source with the csvNullValue setting set to other values.

  • Improved the timestampColumnName extra connection attribute in a full load with CDC to be sortable during CDC when using S3 as a target.

  • Improved the handling of binary data types in hex format such as BYTE, BINARY, and BLOB when using S3 as a source.

  • Fixed an issue where deleted records are migrated with special characters when using S3 as a target.

  • Fixed an issue to handle empty key values when using Amazon DocumentDB (with MongoDB compatibility) as a target.

  • Fixed an issue where AWS DMS fails to replicate NumberDecimal or Decimal128 columns when using MongoDB or Amazon DocumentDB (with MongoDB compatibility) as a source.

  • Fixed an issue to allow CDC tasks to retry when there is a fail over on MongoDB or Amazon DocumentDB (with MongoDB compatibility) as a source.

  • Added an option to remove the hexadecimal “0x” prefix to RAW data type values when using Kinesis, Kafka, or OpenSearch as a target.

  • Fixed an issue where validation fails on fixed length character columns when using Db2 LUW as a source.

  • Fixed an issue where validation fails when only the source data type or the target data type is FLOAT or DOUBLE.

  • Fixed an issue where validation fails on NULL characters when using Oracle as a source.

  • Fixed an issue where validation fails on XML columns when using Oracle as a source.

  • Fixed an issue where AWS DMS tasks crash when there are nullable columns in composite keys using MySQL as a source.

  • Fixed an issue where AWS DMS fails to validate both UNIQUEIDENTIFIER columns from SQL Server source endpoints and UUID columns from PostgreSQL target endpoints.

  • Fixed an issue where a CDC task does not use an updated source table definition after it is modified.

  • Improved AWS DMS fail over to treat task failures caused by an invalid user name or password as recoverable errors.

  • Fixed an issue where AWS DMS tasks fail because of missing LSNs when using RDS for SQL Server as a source.

AWS Database Migration Service 3.4.3 release notes

The following table shows the new features and enhancements introduced in AWS DMS version 3.4.3.

New feature or enhancement Description
New Amazon DocumentDB version Amazon DocumentDB version 4.0 is now supported as a source.
New MariaDB version MariaDB version 10.4 is now supported as both a source and target.
Support for AWS Secrets Manager integration You can store the database connection details (user credentials) for supported endpoints securely in AWS Secrets Manager. You can then submit the corresponding secret instead of plain-text credentials to AWS DMS when you create or modify an endpoint. AWS DMS then connects to the endpoint databases using the secret. For more information on creating secrets for AWS DMS endpoints, see Using secrets to access AWS Database Migration Service endpoints.
Larger options for C5 and R5 replication instances You can now create the following larger replication instance sizes: C5 sizes up to 96 vCPUs and 192 GiB of memory and R5 sizes up to 96 vCPUs and 768 GiB of memory.
Amazon Redshift performance improvement AWS DMS now supports parallel apply when using Redshift as a target to improve the performance of on-going replication. For more information, see Multithreaded task settings for Amazon Redshift.

The issues resolved in AWS DMS 3.4.3 include the following:

  • Fixed an issue where commit timestamp became “1970-01-01 00:00:00” for deferred events when using Db2 LUW as a source.

  • Fixed an issue where AWS DMS tasks failed with an NVARCHAR column as primary key when using SQL Server as a source with Full LOB mode.

  • Fixed an issue of missing records during cached changes phase when using SQL Server as a source.

  • Fixed an issue where records were skipped after AWS DMS tasks were resumed when using RDS for SQL Server as a source.

  • Fixed an issue where AWS DMS ASSERTION logging component generates large logs for SQL Server.

  • Fixed an issue where data validation failed during CDC phase due to column parsing overflow when using MySQL as a source.

  • Fixed an issue where AWS DMS tasks crashed due to a segmentation fault during data validation when using PostgreSQL as a target.

  • Fixed an issue where data validation failed on DOUBLE data type during CDC when using PostgreSQL as a source and a target.

  • Fixed an issue where records inserted by copy command were not replicated correctly when using PostgreSQL as a source and Redshift as a target.

  • Fixed a data loss issue during cached changes phase when using PostgreSQL as a source.

  • Fixed an issue which could potentially cause either data loss or record duplicates when using PostgreSQL as a source.

  • Fixed an issue where schemas with mixed cases failed to migrate with pglogical when using PostgreSQL as a source.

  • Fixed an issue where the Last Failure Message did not contain the ORA error when using Oracle as a source.

  • Fixed an issue where AWS DMS tasks failed to build UPDATE statements when using Oracle as a target.

  • Fixed an issue where AWS DMS tasks did not replicate data when using Oracle 12.2 as a source with ASM and Pluggable Database configuration.

  • Improved record parsing by preserving quotes to be compliant with RFC 4180 when using S3 as a source.

  • Improved the handling of timestampColumnName so that the column from Full Load is sortable with that from CDC.

  • By introducing a new endpoint setting MessageMaxBytes, fixed an issue where AWS DMS tasks failed when there are LOB elements larger than 1MB .

  • Fixed an issue where AWS DMS tasks crashed due to a segmentation fault when using Redshift as a target.

  • Improved error logging for Redshift test connection.

  • Fixed an issue where AWS DMS did not transfer all documents from MongoDB to DocumentDB during Full Load.

  • Fixed an issue where AWS DMS tasks reported fatal error when no tables were included in the table mapping rules.

  • Fixed an issue where schemas and tables created before restarting AWS DMS tasks did not replicate to the target when using MySQL as a source.

  • Fixed an issue where wildcard escape [_] cannot escape wildcard “_” in exclude rule when using MySQL as a source.

  • Fixed an issue where column of data type UNSIGNED BIGINT did not replicate correctly when using MySQL as a source.

AWS Database Migration Service 3.4.2 release notes

The following table shows the new features and enhancements introduced in AWS DMS version 3.4.2.

New feature or enhancement Description
Support for privately connecting your Amazon Virtual Private Cloud (Amazon VPC) to AWS Database Migration Service (DMS) without requiring an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. You can now connect to and access AWS DMS from your Amazon VPC through a VPC interface endpoint that you create. This interface endpoint allows you to isolate all network activity of your AWS DMS replication instance within the Amazon network infrastructure. By including a reference to this interface endpoint in all API calls to AWS DMS using the AWS CLI or an SDK, you ensure that all AWS DMS activity remains invisible to the public Internet. For more information, see Infrastructure security in AWS Database Migration Service.
Note

This feature is available using all supported AWS DMS engine versions.

CDC date-based folder partitioning using Amazon S3 as a target

AWS DMS now supports date-based folder partitioning when replicating data using S3 as a target. For more information, see Using date-based folder partitioning.

The issues resolved in AWS DMS 3.4.2 include the following:

  • Added a STATUPDATE option when performing a migration using Redshift as a target.

  • Improved validation tasks by introducing a new setting. ValidQueryCdcDelaySecond delays the first validation query on both source and target endpoints to help reduce resource contention when migration latency is high.

  • Fixed an issue where AWS DMS took a long time to start validation tasks.

  • Fixed an issue where empty records were generated when starting or stopping replication tasks using S3 as a target.

  • Fixed an issue where tasks got stuck after a full load completed.

  • Fixed an issue where tasks got stuck when a source table has data errors while using S3 as a source .

  • Fixed an issue where tasks got stuck while starting when the user account of the source endpoint is disabled.

  • Fixed an issue where tasks crashed when using PostgreSQL as a source with REPLICA IDENTITY FULL.

  • Fixed an issue where tasks missed transactions when using PostgreSQL as a source with pglogical plugin.

  • Fixed an issue when AWS DMS didn't delete compressed source files when using Redshift as a target.

  • Fixed an issue where validation tasks reported false negatives when using MySQL as both source and target with data type BIGINT UNSIGNED.

  • Fixed an issue where validation tasks reported false positives when using SQL Server as a source with a primary key column as CHAR type.

  • Fixed an issue where AWS DMS doesn't clear target objects when using start-replication to start replication tasks using S3 as a target.

  • Fixed several issues on data validation when using Db2 as a source.

  • Fixed an issue where validation tasks got stuck when using SQL Server as a source with VARCHAR column as primary key.

  • Added support for data type TIMESTAMP WITH TIMEZONE when using PostgreSQL as a source

AWS Database Migration Service 3.4.1 Beta release notes

The following table shows the new features and enhancements introduced in AWS DMS version 3.4.1 Beta.

New feature or enhancement Description
New MongoDB version

MongoDB version 4.0 is now supported as a source.

TLS 1.2 support for SQL Server

AWS DMS now supports TLS 1.2 for SQL Server endpoints.

The issues resolved in AWS DMS 3.4.1 Beta include the following:

  • Improved Oracle 19c TDE support.

  • Improved support of utf8mb4 character set and identity data type using Redshift as a target.

  • Improved replication task failure handling when using MySQL as a source and binary log is not present.

  • Improved data validation support on various data types and character sets.

  • Improved null value handling with a new endpoint setting IncludeNullAndEmpty when using Kinesis and Kafka as a target.

  • Improved error logging and handling when using Kafka as a target.

  • Improved DST time offset when using SQL Server as a source.

  • Fixed an issue where replication tasks try to create existing tables for Oracle as a target.

  • Fixed an issue where replication tasks get stuck after the database connection is killed when using Oracle as a source.

  • Fixed an issue where replication tasks failed to detect and reconnect to the new primary when using SQL Server as a source with AlwaysON setting.

  • Fixed an issue where replication tasks do not add a "D" for "OP" column under certain conditions for S3 as a target.

AWS Database Migration Service 3.4.0 Beta release notes

The following table shows the new features and enhancements introduced in AWS DMS version 3.4.0

New feature or enhancement Description
New MySQL version

AWS DMS now supports MySQL version 8.0 as a source, except when the transaction payload is compressed.

TLS 1.2 support for MySQL

AWS DMS now supports TLS 1.2 for MySQL endpoints.

New MariaDB version

AWS DMS now supports MariaDB version 10.3.13 as a source.

Non-SysAdmin access to self-managed Microsoft SQL Server sources

AWS DMS now supports access by non-SysAdmin users to on-premise and EC2-hosted SQL Server source endpoints.

Note

This feature is currently in Beta. If you want to try it out, contact AWS support for more information.

CDC tasks and Oracle source tables created using CREATE TABLE AS

AWS DMS now supports both full-load and CDC and CDC-only tasks running against Oracle source tables created using the CREATE TABLE AS statement.

The issues resolved in AWS DMS 3.4.0 include the following:

  • Improved premigration task assessments. For more information, see Enabling and working with premigration assessments for a task.

  • Improved data validation for float, real, and double data types.

  • Improved Amazon Redshift as a target by better handling this error: "The specified key does not exist."

  • Supports multithreaded CDC load task settings, including ParallelApplyThreads, ParallelApplyBufferSize, and ParallelApplyQueuesPerThread, for Amazon OpenSearch Service (OpenSearch Service) as a target.

  • Improved OpenSearch Service as a target by supporting its use of composite primary keys.

  • Fixed an issue where test connection fails when using PostgreSQL as a source and the password has special characters in it.

  • Fixed an issue with using SQL Server as a source when some VARCHAR columns are truncated.

  • Fixed an issue where AWS DMS does not close open transactions when using Amazon RDS SQL Server as a source. This can result in data loss if the polling interval parameter is set incorrectly. For more information on how to setup a recommended polling interval value, see Using a Microsoft SQL Server database as a source for AWS DMS.

  • Fixed an issue for Oracle Standby as source where CDC tasks would stop unexpectedly when using Binary Reader.

  • Fixed an issue for IBM DB2 for LUW where the task failed with the message "The Numeric literal 0 is not valid because its value is out of range."

  • Fixed an issue for a PostgreSQL to PostgreSQL migration when a new column was added on the PostgreSQL source and the column was created with a different data type than the data type for which the column was originally created on the source.

  • Fixed an issue with a MySQL source the migration task stopped unexpectedly when it was unable to fetch binlogs.

  • Fixed an issue related to an Oracle target when BatchApply was being used.

  • Fixed an issue for MySQL and MariaDb when migrating the TIME data type.

  • Fixed an issue for an IBM DB2 LUW source where migrating tables with LOBs fail when the tables don't have a primary key or unique key.

AWS Database Migration Service 3.3.4 release notes

The issues resolved in AWS DMS 3.3.4 include the following:

  • Fixed an issue where transactions are dropped or duplicated when using PostgreSQL as a source.

  • Improved the support of using dollar sign ($) in schema names.

  • Fixed an issue where replication instances do not close open transactions when using RDS SQL Server as a source.

  • Fixed an issue where test connection fails when using PostgreSQL as a source and the password has special characters in it.

  • Improved Amazon Redshift as a target by better handling this error: "The specified key does not exist."

  • Improved data validation support on various data types and character sets.

  • Fixed an issue where replication tasks try to create existing tables for Oracle as a target.

  • Fixed an issue where replication tasks do not add a "D" for "OP" column under certain conditions for Amazon S3 as a target.

AWS Database Migration Service 3.3.3 release notes

The following table shows the new features and enhancements introduced in AWS DMS version 3.3.3.

New feature or enhancement Description
New PostgreSQL version

PostgreSQL version 12 is now supported as a source and target.

Support for composite primary key with Amazon OpenSearch Service as target

As of AWS DMS 3.3.3, use of a composite primary key is supported by OpenSearch Service targets.

Support for Oracle extended data types

Oracle extended data types for both Oracle source and targets are now supported.

Increased number of AWS DMS resources per account

The limit on the number of AWS DMS resources you can create has increased. For more information, see Quotas for AWS Database Migration Service.

The issues resolved in AWS DMS 3.3.3 include the following:

  • Fixed an issue where a task crashes using a specific update statement with Parallel Apply in Amazon Kinesis.

  • Fixed an issue where a task crashes on the ALTER TABLE statement with Amazon S3 as a target.

  • Fixed an issue where values on polygon columns are truncated when using Microsoft SQL Server as a source.

  • Fixed an issue on Unicode converter of JA16SJISTILDE and JA16EUCTILDE when using Oracle as a source.

  • Fixed an issue where MEDIUMTEXT and LONGTEXT columns failed to migrate from MySQL to S3 comma-separated value (CSV) format.

  • Fixed an issue where boolean columns were transformed to incorrect types with Apache Parquet output.

  • Fixed an issue with extended varchar columns in Oracle.

  • Fixed an issue where data validation tasks failed due to certain timestamp combinations.

  • Fixed an issue with Sybase data definition language (DDL) replication.

  • Fixed an issue involving an Oracle Real Application Clusters (RAC) source crashing with Oracle Binary Reader.

  • Fixed an issue with validation for Oracle targets with schema names' case.

  • Fixed an issue with validation of IBM Db2 versions 9.7 and 10.

  • Fixed an issue for a task not stopping two times with StopTaskCachedChangesApplied and StopTaskCachedChangesNotApplied enabled.