AWS amazondynamodb documentation change
Summary
Simplified explanation of default permissions by removing explicit mention of AWS Management Console, CLI, and API access limitations
Security assessment
The change removes specific examples of access methods (Console/CLI/API) but maintains the core security concept of least privilege. This is a documentation clarification rather than addressing a specific vulnerability or adding new security controls.
Diff
diff --git a/amazondynamodb/latest/developerguide/security_iam_id-based-policy-examples.md b/amazondynamodb/latest/developerguide/security_iam_id-based-policy-examples.md index 6a8a62cea..efddf7243 100644 --- a//amazondynamodb/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//amazondynamodb/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 DynamoDB 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 DynamoDB resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.