AWS dms medium security documentation change
Summary
Added documentation about CDC duplicate records prevention and SSL mode limitations for Redshift Serverless
Security assessment
The SSL mode limitation documentation ('verify-full' not supported) directly addresses secure connection requirements and guides users to alternative encryption methods. This impacts security configurations for database connections.
Diff
diff --git a/dms/latest/userguide/CHAP_Target.Redshift.md b/dms/latest/userguide/CHAP_Target.Redshift.md index 86bb3cd44..090ed3621 100644 --- a//dms/latest/userguide/CHAP_Target.Redshift.md +++ b//dms/latest/userguide/CHAP_Target.Redshift.md @@ -163,0 +164,2 @@ The following limitations apply when using an Amazon Redshift database as a targ + * Duplicate records might appear in target tables because Amazon Redshift does not enforce primary keys and AWS DMS may replay CDC when a task is resumed. To prevent duplicates, use the `ApplyErrorInsertPolicy=INSERT_RECORD` setting. For more information, see [Error handling task settings](./CHAP_Tasks.CustomizingTasks.TaskSettings.ErrorHandling.html). Alternatively, you can implement application-level duplicate detection and post-migration cleanup procedures. + @@ -601,0 +604,4 @@ Using Redshift Serverless as a target has the following limitations: + * AWS DMS does not support Enhanced Throughput for Amazon Redshift Serverless as a target. For more information, see [Enhanced Throughput for Full-Load Oracle to Amazon Redshift and Amazon S3 Migrations](./CHAP_Serverless.Components.html#CHAP_Serverless.Throughput). + + * AWS DMS does not support connections to Amazon Redshift Redshift Serverless when the SSL mode is set to `verify-full`. For connections requiring SSL verification to Amazon Redshift Serverless targets, use alternative SSL modes such as `require` or `verify-ca`. +