AWS dms documentation change
Summary
Added a limitation note about potential duplicate records in Amazon Redshift targets due to CDC replay and lack of primary key enforcement, with mitigation recommendations.
Security assessment
The change addresses data integrity concerns (duplicate records) during migration operations, not a security vulnerability or weakness. No evidence of security exploit or vulnerability mitigation.
Diff
diff --git a/dms/latest/userguide/CHAP_Target.Redshift.md b/dms/latest/userguide/CHAP_Target.Redshift.md index 1020ea183..0125fb455 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. +