AWS Security ChangesHomeSearch

AWS dms documentation change

Service: dms · 2025-06-04 · Documentation low

File: dms/latest/userguide/CHAP_Target.Oracle.md

Summary

Clarified permissions requirement by replacing 'dms_user' with a general reference to the user account in the target endpoint

Security assessment

Improves clarity about security configuration but does not address a specific security issue or introduce new security documentation.

Diff

diff --git a/dms/latest/userguide/CHAP_Target.Oracle.md b/dms/latest/userguide/CHAP_Target.Oracle.md
index 486398cbf..dac35a598 100644
--- a//dms/latest/userguide/CHAP_Target.Oracle.md
+++ b//dms/latest/userguide/CHAP_Target.Oracle.md
@@ -203 +203 @@ If any of the required privileges cannot be granted to V$xxx, then grant them to
-To use the premigration assessments listed in [Oracle assessments](./CHAP_Tasks.AssessmentReport.Oracle.html) with Oracle as a Target, you must add the following permissions to the `dms_user` database user on the target database:
+To use the premigration assessments listed in [Oracle assessments](./CHAP_Tasks.AssessmentReport.Oracle.html) with Oracle as a Target, you must add the following permissions to the user account specified in the Oracle database target endpoint: