AWS odb documentation change
Summary
Removed mention of users lacking console/CLI/API task permissions by default and simplified default permission explanation
Security assessment
The change simplifies the description of default permissions but doesn't address a specific security vulnerability or weakness. It maintains existing security guidance about IAM policies without introducing new security-related content or fixes.
Diff
diff --git a/odb/latest/UserGuide/security_iam_id-based-policy-examples.md b/odb/latest/UserGuide/security_iam_id-based-policy-examples.md index 5cea1ec93..9a105dcb9 100644 --- a//odb/latest/UserGuide/security_iam_id-based-policy-examples.md +++ b//odb/latest/UserGuide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to provision Oracle Database@A -By default, users and roles don't have permission to create or modify Oracle Database@AWS resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify Oracle Database@AWS resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.