AWS amazonq documentation change
Summary
Removed mention of default inability to use AWS console/CLI/API from policy explanation
Security assessment
This change simplifies the description of default permissions but doesn't address any specific security vulnerability. It maintains security documentation about IAM policies without introducing new security content or fixing a disclosed issue.
Diff
diff --git a/amazonq/latest/qbusiness-ug/security_iam_id-based-policy-examples.md b/amazonq/latest/qbusiness-ug/security_iam_id-based-policy-examples.md index 179b94c1c..c5cdf70e6 100644 --- a//amazonq/latest/qbusiness-ug/security_iam_id-based-policy-examples.md +++ b//amazonq/latest/qbusiness-ug/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsA -By default, users and roles don't have permission to create or modify Amazon Q 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 Q resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.