AWS config documentation change
Summary
Removed mention of specific interfaces (AWS Management Console, AWS CLI, AWS API) from default permissions explanation and simplified policy assignment flow
Security assessment
The change simplifies existing security documentation about IAM permissions but doesn't address any specific vulnerability or weakness. It removes redundant references to access methods while maintaining the core security concept of least privilege. No evidence of patching a security issue or introducing new security controls.
Diff
diff --git a/config/latest/developerguide/security_iam_id-based-policy-examples.md b/config/latest/developerguide/security_iam_id-based-policy-examples.md index ce041238d..c060085d8 100644 --- a//config/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//config/latest/developerguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesSign up for an AWS accountCreate a user with administrative -By default, users and roles don't have permission to create or modify AWS Config 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 Config resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.