AWS emr documentation change
Summary
Added JSON section markers and separators in IAM policy examples
Security assessment
Changes only add formatting markers for JSON policy examples but do not modify security content or address vulnerabilities
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md b/emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md index a88071f85..8b6908079 100644 --- a//emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md +++ b//emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md @@ -16,0 +17,6 @@ The following is a sample policy that allows power users to create and modify EM +JSON + + +**** + + @@ -47,0 +55,6 @@ We strongly recommend setting this policy to ensure that users cannot create EC2 +JSON + + +**** + + @@ -106,0 +121,6 @@ This following is a sample policy that allows users read-only permissions on EMR +JSON + + +**** + + @@ -131,0 +153,6 @@ You can use tag conditions for fine-grained access control. For example, you can +JSON + + +**** + +