AWS secretsmanager documentation change

Service: secretsmanager · 2025-06-28 · Documentation low

File: secretsmanager/latest/userguide/auth-and-access_iam-policies.md

Summary

Added JSON formatting markers in multiple policy examples

Security assessment

Formatting changes to policy examples without altering security guidance

Diff

diff --git a/secretsmanager/latest/userguide/auth-and-access_iam-policies.md b/secretsmanager/latest/userguide/auth-and-access_iam-policies.md
index 7c8f74f4c..61387e0f8 100644
--- a//secretsmanager/latest/userguide/auth-and-access_iam-policies.md
+++ b//secretsmanager/latest/userguide/auth-and-access_iam-policies.md
@@ -52,0 +53,6 @@ If a secret is encrypted using a customer managed key, you can grant access to r
+JSON
+    
+
+****
+    
+    
@@ -75,0 +83,6 @@ You can grant access to a secret by attaching the following policy to an identit
+JSON
+    
+
+****
+    
+    
@@ -96,0 +111,6 @@ You can grant access to retrieve a group of secrets in a batch API call by attac
+JSON
+    
+
+****
+    
+    
@@ -130,0 +152,6 @@ The following policy grants access to retrieve all secrets with a name beginning
+JSON
+    
+
+****
+    
+    
@@ -144,0 +173,6 @@ The following policy grants `DescribeSecret` and permissions beginning with `Lis
+JSON
+    
+
+****
+    
+    
@@ -165,0 +201,6 @@ Because you can predict all of the parts of the ARN of a secret except the 6 ran
+JSON
+    
+
+****
+    
+    
@@ -188,0 +231,6 @@ The following policy grants permission to create secrets and view a list of secr
+JSON
+    
+
+****
+    
+    
@@ -220,0 +270,6 @@ The following policy denies the use of the AWS managed key `aws/secretsmanager`
+JSON
+    
+
+****
+    
+