AWS bedrock-agentcore documentation change
Summary
Removed specific mention of AWS Management Console, AWS CLI, and AWS API from default permissions explanation. Simplified statement about granting permissions through IAM policies.
Security assessment
The change simplifies the description of default permissions but does not address any specific security vulnerability or weakness. It maintains existing security guidance about IAM policy management without introducing new security features or mitigations.
Diff
diff --git a/bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md b/bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md index 0cf54203b..81dc22472 100644 --- a//bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md +++ b//bedrock-agentcore/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 AgentCore 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 AgentCore resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.