AWS emr documentation change
Summary
Simplified explanation of default permissions by removing references to specific AWS interfaces (Console, CLI, API)
Security assessment
The edit removes redundant details about default deny across AWS interfaces but maintains the core security principle of least privilege. No evidence of a security vulnerability being addressed.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/security-iam-id-based-policy-examples.md b/emr/latest/EMR-Serverless-UserGuide/security-iam-id-based-policy-examples.md index e62e5e39d..9ef8bf0e0 100644 --- a//emr/latest/EMR-Serverless-UserGuide/security-iam-id-based-policy-examples.md +++ b//emr/latest/EMR-Serverless-UserGuide/security-iam-id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesAllow users to access their own permissions -By default, users and roles don't have permission to create or modify Amazon EMR Serverless 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 EMR Serverless resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.