AWS resilience-hub documentation change
Summary
Removed mention of specific access methods (console/CLI/API) from default permissions explanation
Security assessment
The change simplifies the description of default permissions but does not address any specific security vulnerability or weakness. It maintains existing security documentation about IAM policies without adding new security features or mitigations.
Diff
diff --git a/resilience-hub/latest/userguide/security_iam_id-based-policy-examples.md b/resilience-hub/latest/userguide/security_iam_id-based-policy-examples.md index 6b9246327..1beeb080d 100644 --- a//resilience-hub/latest/userguide/security_iam_id-based-policy-examples.md +++ b//resilience-hub/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsL -By default, users and roles don't have permission to create or modify AWS Resilience Hub 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 AWS Resilience Hub resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.