AWS IAM documentation change

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

File: IAM/latest/UserGuide/id_roles_create_policy-examples.md

Summary

Removed a JSON policy example and added multiple JSON formatting blocks with separators

Security assessment

Changes appear to be documentation formatting improvements rather than security-related content updates. No security vulnerabilities or specific security features are addressed.

Diff

diff --git a/IAM/latest/UserGuide/id_roles_create_policy-examples.md b/IAM/latest/UserGuide/id_roles_create_policy-examples.md
index ca20824d7..91f52fa03 100644
--- a//IAM/latest/UserGuide/id_roles_create_policy-examples.md
+++ b//IAM/latest/UserGuide/id_roles_create_policy-examples.md
@@ -39,16 +38,0 @@ The following example shows a policy that can be attached to a role. The policy
-    {
-      "Version": "2012-10-17",
-      "Statement": [
-        {
-          "Effect": "Allow",
-          "Principal": {
-            "Service": [
-              "elasticmapreduce.amazonaws.com",
-              "datapipeline.amazonaws.com"
-            ]
-          },
-          "Action": "sts:AssumeRole"
-        }
-      ]
-    }
-
@@ -60,0 +45,6 @@ The S3 bucket policy in account A might look like the following policy. In this
+JSON
+    
+
+****
+    
+    
@@ -81,0 +73,6 @@ To implement this policy account B uses IAM to attach it to the appropriate user
+JSON
+    
+
+****
+    
+    
@@ -100,0 +99,6 @@ The following example queue policy gives account B permission to perform the `Se
+JSON
+    
+
+****
+    
+    
@@ -120,0 +126,6 @@ Account B's policy for delegating access to a group in account B might look like
+JSON
+    
+
+****
+    
+    
@@ -140,0 +153,6 @@ Account A's bucket policy might look like the following policy. In this example,
+JSON
+    
+
+****
+    
+