AWS documentdb documentation change
Summary
Simplified language about default permissions, removing references to console/CLI/API access restrictions
Security assessment
The change removes redundant phrasing about access methods but maintains the core security concept of default deny. No specific security vulnerability is introduced or addressed.
Diff
diff --git a/documentdb/latest/developerguide/security_iam_id-based-policy-examples.md b/documentdb/latest/developerguide/security_iam_id-based-policy-examples.md index 5ed3082d4..22f6e7026 100644 --- a//documentdb/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//documentdb/latest/developerguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify Amazon DocumentDB 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 Amazon DocumentDB resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.