AWS emr documentation change
Summary
Removed mention of default inability to perform tasks via AWS Console/CLI/API from introductory paragraph about IAM permissions
Security assessment
The change simplifies the description of default permissions but doesn't address any specific vulnerability or security incident. It maintains the core security concept of least privilege by default, but removes technical details about access methods rather than modifying security guidance.
Diff
diff --git a/emr/latest/EMR-on-EKS-DevelopmentGuide/security_iam_id-based-policy-examples.md b/emr/latest/EMR-on-EKS-DevelopmentGuide/security_iam_id-based-policy-examples.md index 0307b1a29..1a3fa91f9 100644 --- a//emr/latest/EMR-on-EKS-DevelopmentGuide/security_iam_id-based-policy-examples.md +++ b//emr/latest/EMR-on-EKS-DevelopmentGuide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify Amazon EMR on EKS 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 on EKS resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.