AWS dms documentation change
Summary
Updated wording from contractions ('doesn't' to 'does not') and fixed typo in DATETIME conversion note. No functional changes to documentation content.
Security assessment
Changes are grammatical corrections and typo fixes. No security-related content was added or modified. The documentation updates clarify existing limitations but do not address vulnerabilities or security controls.
Diff
diff --git a/dms/latest/userguide/CHAP_Target.Redshift.md b/dms/latest/userguide/CHAP_Target.Redshift.md index f80aa0f17..b7eebd697 100644 --- a//dms/latest/userguide/CHAP_Target.Redshift.md +++ b//dms/latest/userguide/CHAP_Target.Redshift.md @@ -77 +77 @@ The following list describes the prerequisites necessary for working with Amazon - * AWS DMS converts BLOBs, CLOBs, and NCLOBs to a VARCHAR on the target Amazon Redshift instance. Amazon Redshift doesn't support VARCHAR data types larger than 64 KB, so you can't store traditional LOBs on Amazon Redshift. + * AWS DMS converts BLOBs, CLOBs, and NCLOBs to a VARCHAR on the target Amazon Redshift instance. Amazon Redshift does not support VARCHAR data types larger than 64 KB, so you can't store traditional LOBs on Amazon Redshift. @@ -148 +148 @@ The following limitations apply when using an Amazon Redshift database as a targ - * Amazon Redshift doesn't support VARCHARs larger than 64 KB. LOBs from traditional databases can't be stored in Amazon Redshift. + * Amazon Redshift does not support VARCHARs larger than 64 KB. LOBs from traditional databases can't be stored in Amazon Redshift. @@ -156 +156 @@ The following limitations apply when using an Amazon Redshift database as a targ - * DMS doesn't support custom DNS names when configuring an endpoint for a Redshift cluster, and you need to use the Amazon provided DNS name. Since the Amazon Redshift cluster must be in the same AWS account and Region as the replication instance, validation fails if you use a custom DNS endpoint. + * DMS does not support custom DNS names when configuring an endpoint for a Redshift cluster, and you need to use the Amazon provided DNS name. Since the Amazon Redshift cluster must be in the same AWS account and Region as the replication instance, validation fails if you use a custom DNS endpoint. @@ -552 +552 @@ TIME | VARCHAR(20) -DATETIME | If the scale is => 0 and =< 6, depending on Redshift target column type, then one of the following: TIMESTAMP (s) TIMESTAMPTZ (s) — If source timestamp contains a zone offset (such as in SQL Server or Oracle) it converts to UTC on insert/update. If it doesn't contain an offset, then time is considered in UTC already. If the scale is => 7 and =< 9, then: VARCHAR (37) +DATETIME | If the scale is => 0 and =< 6, depending on Redshift target column type, then one of the following: TIMESTAMP (s) TIMESTAMPTZ (s) — If source timestamp contains a zone offset (such as in SQL Server or Oracle) it converts to UTC on insert/update. If it does not contain an offset, then time is considered in UTC already. If the scale is => 7 and =< 9, then: VARCHAR (37) @@ -566,3 +566,3 @@ WSTRING | If the length is 1–65,535, then use NVARCHAR (length in bytes) If -BLOB | VARCHAR (maximum LOB size *2) The maximum LOB size cannot exceed 31 KB. Amazon Redshift doesn't support VARCHARs larger than 64 KB. -NCLOB | NVARCHAR (maximum LOB size) The maximum LOB size cannot exceed 63 KB. Amazon Redshift doesn't support VARCHARs larger than 64 KB. -CLOB | VARCHAR (maximum LOB size) The maximum LOB size cannot exceed 63 KB. Amazon Redshift doesn't support VARCHARs larger than 64 KB. +BLOB | VARCHAR (maximum LOB size *2) The maximum LOB size cannot exceed 31 KB. Amazon Redshift does not support VARCHARs larger than 64 KB. +NCLOB | NVARCHAR (maximum LOB size) The maximum LOB size cannot exceed 63 KB. Amazon Redshift does not support VARCHARs larger than 64 KB. +CLOB | VARCHAR (maximum LOB size) The maximum LOB size cannot exceed 63 KB. Amazon Redshift does not support VARCHARs larger than 64 KB.