AWS emr documentation change
Summary
Added JSON section markers with formatting separators in multiple policy examples
Security assessment
Changes only add JSON formatting markers without modifying security-related content. No evidence of addressing vulnerabilities or security features.
Diff
diff --git a/emr/latest/ManagementGuide/emr-studio-user-permissions.md b/emr/latest/ManagementGuide/emr-studio-user-permissions.md index 0bf680dde..23f1a8dd1 100644 --- a//emr/latest/ManagementGuide/emr-studio-user-permissions.md +++ b//emr/latest/ManagementGuide/emr-studio-user-permissions.md @@ -24,0 +25,6 @@ When you create the role, use the following trust relationship policy. +JSON + + +**** + + @@ -216,0 +224,6 @@ The example policy includes `Condition` elements to enforce tag-based access con +JSON + + +**** + + @@ -347,0 +362,6 @@ The example policy includes `Condition` elements to enforce tag-based access con +JSON + + +**** + + @@ -553,0 +575,6 @@ The example policy includes `Condition` elements to enforce tag-based access con +JSON + + +**** + + @@ -844,0 +873,6 @@ In this example policy that has user permissions for EMR Serverless interactive +JSON + + +**** + + @@ -1089,0 +1125,6 @@ Describe network objects. | Yes | Yes | Yes | +JSON + + +**** + + @@ -1109,0 +1152,6 @@ List IAM roles. | Yes | Yes | Yes | +JSON + + +**** + +