AWS emr documentation change
Summary
Added JSON formatting to multiple IAM policy examples
Security assessment
Improved structure of access control policies without security fixes
Diff
diff --git a/emr/latest/ManagementGuide/emr-studio-manage-users.md b/emr/latest/ManagementGuide/emr-studio-manage-users.md index 5139b1c04..e97f58f8f 100644 --- a//emr/latest/ManagementGuide/emr-studio-manage-users.md +++ b//emr/latest/ManagementGuide/emr-studio-manage-users.md @@ -32,0 +33,8 @@ The following example policy gives a user access to a particular EMR Studio by a +JSON + +JSON + + +**** + + @@ -58,0 +68,8 @@ The following example permissions policy allows the `CreateStudioPresignedUrl` a +JSON + +JSON + + +**** + + @@ -88,0 +107,8 @@ The following example policy allows the `CreateStudioPresignedUrl` action and gi +JSON + +JSON + + +**** + + @@ -226,0 +254,8 @@ In the following example policy, assume that you have an EMR Studio with the tag +JSON + +JSON + + +**** + +