AWS dms documentation change

Service: dms · 2026-03-07 · Documentation low

File: dms/latest/userguide/zero-etl.md

Summary

Added source database configuration requirements section with engine-specific details and PostgreSQL CaptureDdls setting requirement

Security assessment

The changes add operational configuration guidance but do not reference security vulnerabilities or security-specific controls. The PostgreSQL CaptureDdls setting prevents task failures rather than addressing security risks.

Diff

diff --git a/dms/latest/userguide/zero-etl.md b/dms/latest/userguide/zero-etl.md
index 30adb7e91..10f4767cd 100644
--- a//dms/latest/userguide/zero-etl.md
+++ b//dms/latest/userguide/zero-etl.md
@@ -5 +5 @@
-How zero-ETL integration works for self-managed database sourcesSetting up IAM permissions and encryption for zero-ETL integration
+How zero-ETL integration works for self-managed database sourcesSource database configuration before creating integrationSetting up IAM permissions and encryption for zero-ETL integration
@@ -46,0 +47,48 @@ You can create an Amazon Redshift event notification subscriptions to be automat
+## Source database configuration before creating integration
+
+Before configuring zero-ETL integrations, you must properly configure your source database according to the requirements for your database engine. Each engine has specific configuration requirements and limitations. 
+
+SQL Server
+
+  * For configuration requirements, see [Using a Microsoft SQL Server database as a source for AWS DMS](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.SQLServer.html). 
+
+  * For change data capture (CDC) requirements, see [Capturing data changes for ongoing replication from SQL Server](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.SQLServer.CDC.html). 
+
+
+
+
+###### Note
+
+RDS SQL Server and Azure SQL Server cannot be used as sources for self-managed zero-ETL integrations.
+
+Oracle
+
+  * For configuration requirements and limitations, see [Using an Oracle database as a source for AWS DMS](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.Oracle.html). 
+
+
+
+
+MySQL
+
+  * For configuration requirements and limitations, see [Using a MySQL-compatible database as a source for AWS DMS](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MySQL.html). 
+
+
+
+
+PostgreSQL
+
+  * For configuration requirements and limitations, see [Using a PostgreSQL database as an AWS DMS source](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html). 
+
+  * When using a self-managed PostgreSQL database as a source, the following limitation applies:
+
+    * For self-managed PostgreSQL sources, you must set `CaptureDdls` to `false` in the PostgreSQL endpoint settings when creating the source endpoint. To set this parameter, use the following when creating your source endpoint: 
+        
+                --postgre-sql-settings '{"CaptureDdls": false}'
+
+If you do not set CaptureDdls to false, the task may fail to start successfully. 
+
+    * When `CaptureDdls` is set to `false`, DDL operations (such as CREATE TABLE, ALTER TABLE, and DROP TABLE) performed on the source database during replication will not be captured or replicated to the target. 
+
+
+
+
@@ -57 +105 @@ Before creating a zero-ETL integration, ensure you have the following:
-  * Existing AWS DMS source endpoints for your self-managed databases
+  * Configure AWS DMS source endpoints for your self-managed databases. For more information, see Source database configuration before creating integration.