AWS dms documentation change
Summary
Clarified validation failure delay logic and added documentation about CDC latency precedence
Security assessment
Improves documentation around validation timing mechanisms but does not address security vulnerabilities or introduce security features
Diff
diff --git a/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md b/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md index 17a9359fe..9c199e3ba 100644 --- a//dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md +++ b//dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md @@ -25 +25,3 @@ Irrespective of the setting, AWS DMS validates all rows configured via table val - * `RecordFailureDelayLimitInMinutes` – Specifies the delay before reporting any validation failure details. Normally, AWS DMS uses the task latency to recognize actual delay for changes to make it to the target in order to prevent false positives. This setting overrides the actual delay value and enables you to set a higher delay before reporting any validation metrics. The default value is 0. +If overall DMS Task CDC latency is greater than the value of `RecordFailureDelayInMinutesthen` it takes the precedence, for example, if `RecordFailureDelayInMinutes` is 5, and CDC Latency is 7 mins then DMS waits 7 minutes to report the validation failure details. + + * `RecordFailureDelayLimitInMinutes` – Specifies the delay before reporting any validation failure details. AWS DMS uses the task latency to recognize actual delay for changes to make it to the target in order to prevent false positives. This setting overrides the actual delay and DMS task CDC Latency value and enables you to set a greater delay before reporting any validation metrics. The default value is 0.