AWS IAM documentation change

Service: IAM · 2025-07-10 · Documentation low

File: IAM/latest/UserGuide/reference_policies_variables.md

Summary

Added JSON formatting blocks and section separators (****) in multiple variable examples

Security assessment

Structural formatting changes without modifying security-related content or introducing new security concepts

Diff

diff --git a/IAM/latest/UserGuide/reference_policies_variables.md b/IAM/latest/UserGuide/reference_policies_variables.md
index d50420e18..6a17c396f 100644
--- a//IAM/latest/UserGuide/reference_policies_variables.md
+++ b//IAM/latest/UserGuide/reference_policies_variables.md
@@ -39,0 +40,6 @@ In IAM policies, many actions allow you to provide a name for the specific resou
+JSON
+    
+
+****
+    
+    
@@ -83,0 +91,6 @@ The following example shows a policy for an IAM role or user that replaces a spe
+JSON
+    
+
+****
+    
+    
@@ -116,0 +131,6 @@ A policy that allows a principal to get objects from the /David path of an S3 bu
+JSON
+    
+
+****
+    
+    
@@ -130,0 +152,6 @@ By using a policy variable, you can create policies that can be reused. The foll
+JSON
+    
+
+****
+    
+    
@@ -181,0 +210,6 @@ Many AWS resources use ARNs that contain a user-created name. The following IAM
+JSON
+    
+
+****
+    
+    
@@ -205,0 +241,6 @@ For example, the following policy example allows full access to users, but only
+JSON
+    
+
+****
+    
+    
@@ -243,0 +286,6 @@ In the following example, `aws:principaltag/Team` must be equal to `s3:ExistingO
+JSON
+    
+
+****
+    
+