AWS secretsmanager documentation change
Summary
Added JSON formatting markers in policy examples
Security assessment
Structural markup changes without modifying security content
Diff
diff --git a/secretsmanager/latest/userguide/auth-and-access_resource-policies.md b/secretsmanager/latest/userguide/auth-and-access_resource-policies.md index e3363eca2..c3f3b06ab 100644 --- a//secretsmanager/latest/userguide/auth-and-access_resource-policies.md +++ b//secretsmanager/latest/userguide/auth-and-access_resource-policies.md @@ -79,0 +80,6 @@ Contents of `mypolicy.json`: +JSON + + +**** + + @@ -127,0 +135,6 @@ You can grant access to a secret by attaching the following policy to the secret +JSON + + +**** + + @@ -152,0 +167,6 @@ The following policy allows a user to perform Secrets Manager operations only wh +JSON + + +**** + + @@ -176,0 +198,6 @@ The following policy allows commands to create and manage secrets only when they +JSON + + +**** + + @@ -230,0 +259,6 @@ Service principals are not typically used as principals in a policy attached to +JSON + + +**** + +