AWS dms documentation change
Summary
Updated Redshift settings documentation with type clarification and added CaseSensitiveNames parameter for identifier handling
Security assessment
Changes clarify parameter types and add support for case-sensitive identifiers in Redshift migrations. While important for data integrity, these are functional improvements rather than security fixes or security feature documentation.
Diff
diff --git a/dms/latest/userguide/CHAP_Target.Redshift.md b/dms/latest/userguide/CHAP_Target.Redshift.md index 2758bca4e..f80aa0f17 100644 --- a//dms/latest/userguide/CHAP_Target.Redshift.md +++ b//dms/latest/userguide/CHAP_Target.Redshift.md @@ -386 +386 @@ Name | Description -`Acceptanydate` | Specifies if any date format is accepted, including invalid dates formats such as 0000-00-00. Boolean value. Default value: false Valid values: true | false Example: `--redshift-settings '{"Acceptanydate": true}'` +`Acceptanydate` | Specifies if any date format is accepted, including invalid dates formats such as 0000-00-00. Boolean value. Default value: false Valid values: true | false (Boolean) Example: `--redshift-settings '{"Acceptanydate": true}'` @@ -400,0 +401 @@ You can also use the CLI `modify-endpoint` command to change the value of the `E +`CaseSensitiveNames` | Specifies whether to enable case-sensitive handling of identifiers (such as table and column names) when working with Redshift target endpoints. This setting is particularly important when working with Zero-ETL Redshift databases, where the parameter `enable_case_sensitive_identifier` is set to `true` by default. When `CaseSensitiveNames` is set to true, DMS preserves the case sensitivity of identifiers during migration. Default value: false Valid values: true | false (Boolean) Example: `--redshift-settings '{"CaseSensitiveNames": true}'`