AWS dms documentation change
Summary
Updated enhanced data validation documentation with performance details, removed pgcrypto note, and clarified Oracle DBMS_CRYPTO requirements
Security assessment
Primarily feature updates and clarifications. The DBMS_CRYPTO mention relates to existing cryptographic requirements but does not introduce new security documentation.
Diff
diff --git a/dms/latest/userguide/CHAP_Validating.md b/dms/latest/userguide/CHAP_Validating.md index bdc0df344..9c417f94f 100644 --- a//dms/latest/userguide/CHAP_Validating.md +++ b//dms/latest/userguide/CHAP_Validating.md @@ -433 +433 @@ You may see additional load on your Amazon Redshift cluster due to validation qu -Enhanced data validation is now available in version 3.5.4 of the replication engine for both full load and full load with CDC migration tasks. Currently, this enhancement supports migration paths from Oracle to PostgreSQL, SQL Server to PostgreSQL, Oracle to Oracle, and SQL Server to SQL Server. +AWS Database Migration Service has enhanced data validation performance for database migrations, enabling customers to validate large datasets with significantly faster processing times. This enhanced data validation is now available in version 3.5.4 of the replication engine for both full load and full load with CDC migration tasks. Currently, this enhancement supports migration paths from Oracle to PostgreSQL, SQL Server to PostgreSQL, Oracle to Oracle, and SQL Server to SQL Server, with additional migration paths planned for future releases. @@ -443,4 +442,0 @@ Enhanced data validation is now available in version 3.5.4 of the replication en -###### Note - -For Amazon RDS for PostgreSQLinstances, the `pgcrypto` extension is already enabled. - @@ -470 +466 @@ For self-managed PostgreSQL instances, you need to install the `contrib` module -### Limitations +### Enhanced data validation limitations @@ -514 +510 @@ This enhanced data validation feature has the following limitations: - * For a source or target Oracle endpoint, AWS DMS uses DBMS_CRYPTO to validate LOBs. If your Oracle endpoint uses LOBs, then you must grant the execute permission on dbms_crypto to the user account used to access the Oracle endpoint. You can do this by running the following statement: + * For a source or target Oracle endpoint, AWS DMS uses `DBMS_CRYPTO`. If you use data validation on Oracle endpoint you must grant the execute permission on `dbms_crypto` to the user account used to access the Oracle endpoint. You can do this by running the following statement