AWS AmazonS3 documentation change
Summary
Removed mention of specific AWS interfaces (Management Console, CLI, API) from default permission explanation while maintaining core IAM policy creation guidance.
Security assessment
The change simplifies the explanation of default permissions but does not address any specific security vulnerability or weakness. It removes redundant details about access methods without altering security guidance about IAM policy creation.
Diff
diff --git a/AmazonS3/latest/userguide/security_iam_id-based-policy-examples.md b/AmazonS3/latest/userguide/security_iam_id-based-policy-examples.md index 6ea1ccf9a..cdedd7064 100644 --- a//AmazonS3/latest/userguide/security_iam_id-based-policy-examples.md +++ b//AmazonS3/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practices -By default, users and roles don't have permission to create or modify Amazon S3 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 S3 resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.