AWS config documentation change

Service: config · 2025-07-04 · Documentation low

File: config/latest/developerguide/security_iam_id-based-policy-examples.md

Summary

Added JSON formatting markers in policy examples

Security assessment

Formatting improvements without altering security policies

Diff

diff --git a/config/latest/developerguide/security_iam_id-based-policy-examples.md b/config/latest/developerguide/security_iam_id-based-policy-examples.md
index cab3c4996..c40f29393 100644
--- a//config/latest/developerguide/security_iam_id-based-policy-examples.md
+++ b//config/latest/developerguide/security_iam_id-based-policy-examples.md
@@ -198,0 +199,6 @@ The following example shows an AWS managed policy, `AWSConfigUserAccess` that gr
+JSON
+    
+
+****
+    
+    
@@ -250,0 +258,6 @@ This policy grants broad permissions. Before granting full access, consider star
+JSON
+    
+
+****
+    
+    
@@ -380,0 +395,6 @@ In the first policy, you allow the AWS Config rule read actions such as `Describ
+JSON
+    
+
+****
+    
+    
@@ -403,0 +425,6 @@ In the second policy, you deny the AWS Config rule write actions on the specific
+JSON
+    
+
+****
+    
+    
@@ -461,0 +490,6 @@ In this policy, you allow access to the supported aggregator actions for the AWS
+JSON
+    
+
+****
+    
+    
@@ -492,0 +528,6 @@ In this policy, you deny access to the supported aggregator actions for the AWS
+JSON
+    
+
+****
+    
+    
@@ -574,0 +617,6 @@ Attach the following IAM policy to deny access to `InAccessibleAggregator`, or t
+JSON
+    
+
+****
+    
+