AWS dms high security documentation change
Summary
Added release notes for version 3.6.1 including IAM database authentication, PostgreSQL 17 support, and resolved issues related to data masking and transformation rules
Security assessment
The resolved issues include fixes for data masking and transformation rules that could have led to improper data handling or exposure. The addition of IAM database authentication enhances security by centralizing access control. The data masking fix addresses a potential security vulnerability where sensitive data might not be properly obfuscated.
Diff
diff --git a/dms/latest/userguide/CHAP_ReleaseNotes.md b/dms/latest/userguide/CHAP_ReleaseNotes.md index 16e36eeba..cacb0a2a7 100644 --- a//dms/latest/userguide/CHAP_ReleaseNotes.md +++ b//dms/latest/userguide/CHAP_ReleaseNotes.md @@ -5 +5 @@ -AWS DMS 3.6.0 release notesAWS DMS 3.5.4 release notesAWS DMS 3.5.3 release notesAWS DMS 3.5.2 release notesAWS DMS 3.5.1 release notesAWS DMS 3.5.0 Beta release notesAWS DMS 3.4.7 release notesAWS DMS 3.4.6 release notesAWS DMS 3.4.5 release notesAWS DMS 3.4.4 release notesAWS DMS 3.4.3 release notesAWS DMS 3.4.2 release notesAWS DMS 3.4.1 release notesAWS DMS 3.4.0 release notesAWS DMS 3.3.4 release notesAWS DMS 3.3.3 release notes +AWS DMS 3.6.1 release notesAWS DMS 3.6.0 release notesAWS DMS 3.5.4 release notesAWS DMS 3.5.3 release notesAWS DMS 3.5.2 release notesAWS DMS 3.5.1 release notesAWS DMS 3.5.0 Beta release notesAWS DMS 3.4.7 release notesAWS DMS 3.4.6 release notesAWS DMS 3.4.5 release notesAWS DMS 3.4.4 release notesAWS DMS 3.4.3 release notesAWS DMS 3.4.2 release notesAWS DMS 3.4.1 release notesAWS DMS 3.4.0 release notesAWS DMS 3.3.4 release notesAWS DMS 3.3.3 release notes @@ -31,0 +32 @@ Version | Release date | No new instance date | EOL date +**3.6.1** | May 15, 2025 | Sept 15, 2026 | Nov 15, 2026 @@ -43,0 +45,23 @@ The AWS DMS Version 3.6.0 is currently available in Asia Pacific (Sydney): ap-so +## AWS Database Migration Service 3.6.1 release notes + +New features in AWS DMS 3.6.1 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 Postgre SQL 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](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.html). With this enhancement you can use IAM to centrally manage access to your database resources, instead of managing access individually on each database endpoint. +Support for PostgreSQL 17 | Introduced support for PostgreSQL version 17. For more information, see: + + * [Using a PostgreSQL database as an AWS DMS source](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html) + * [Using a PostgreSQL database as a target for AWS Database Migration Service](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.PostgreSQL.html) + + +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](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html). + +AWS DMS version 3.6.1 includes the following resolved issues: + +Issues resolved in the DMS 3.6.1 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. +