AWS dms documentation change
Summary
Removed two limitations: one about potential duplicate records in Redshift targets due to CDC replay, and another about lack of Enhanced Throughput support for Redshift Serverless.
Security assessment
The removed content described functional limitations and workarounds (like INSERT_RECORD policy) without indicating any security vulnerability, weakness, or incident. No security implications are mentioned in the removed text.
Diff
diff --git a/dms/latest/userguide/CHAP_Target.Redshift.md b/dms/latest/userguide/CHAP_Target.Redshift.md index 0125fb455..86bb3cd44 100644 --- a//dms/latest/userguide/CHAP_Target.Redshift.md +++ b//dms/latest/userguide/CHAP_Target.Redshift.md @@ -164,2 +163,0 @@ 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. - @@ -604,2 +601,0 @@ 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). -