AWS bedrock documentation change
Summary
Removed mention of specific interfaces (AWS Management Console, AWS CLI, AWS API) where permissions are denied by default
Security assessment
The change removes explicit references to denied access methods but maintains the core security concept of default deny. This appears to be a documentation simplification rather than addressing a specific vulnerability or security incident.
Diff
diff --git a/bedrock/latest/userguide/security_iam_id-based-policy-examples.md b/bedrock/latest/userguide/security_iam_id-based-policy-examples.md index 9419003f4..b230aca82 100644 --- a//bedrock/latest/userguide/security_iam_id-based-policy-examples.md +++ b//bedrock/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUse the consoleAllow users to view their own permissionsDen -By default, users and roles don't have permission to create or modify Amazon Bedrock 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 Bedrock resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.