AWS IAM documentation change

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

File: IAM/latest/UserGuide/access_controlling.md

Summary

Added multiple empty JSON code blocks and section dividers throughout document

Security assessment

Structural formatting changes without substantive security content. No policy examples or security guidance added/modified.

Diff

diff --git a/IAM/latest/UserGuide/access_controlling.md b/IAM/latest/UserGuide/access_controlling.md
index a729818a8..529410fc5 100644
--- a//IAM/latest/UserGuide/access_controlling.md
+++ b//IAM/latest/UserGuide/access_controlling.md
@@ -47,0 +48,6 @@ You can use a permissions boundary on Zhang to make sure that he is never given
+JSON
+    
+
+****
+    
+    
@@ -218,0 +226,6 @@ Consider the following example policy. It allows a user to create, update (that
+JSON
+    
+
+****
+    
+    
@@ -246,0 +261,6 @@ For more information about using paths in the names of customer managed policies
+JSON
+    
+
+****
+    
+    
@@ -286,0 +308,6 @@ The following example policy allows a user to attach managed policies to only th
+JSON
+    
+
+****
+    
+    
@@ -306,0 +335,6 @@ In the following example, the condition ensures that the `AttachGroupPolicy` and
+JSON
+    
+
+****
+    
+