AWS memorydb documentation change
Summary
Simplified explanation of default permissions and IAM policy creation process by removing redundant details about access methods (console/CLI/API).
Security assessment
The change removes explicit mention of users being unable to perform tasks via AWS interfaces, but this is implied by the broader statement about lacking permissions. No specific security vulnerability or new security feature is introduced - this is a documentation simplification.
Diff
diff --git a/memorydb/latest/devguide/security_iam_id-based-policy-examples.md b/memorydb/latest/devguide/security_iam_id-based-policy-examples.md index d935340a5..b967e035d 100644 --- a//memorydb/latest/devguide/security_iam_id-based-policy-examples.md +++ b//memorydb/latest/devguide/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 MemoryDB 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 MemoryDB resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.