AWS IAM documentation change

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

File: IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.md

Summary

Added JSON formatting markers in monitoring policy examples

Security assessment

Improved formatting of existing security monitoring documentation without introducing new security content

Diff

diff --git a/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.md b/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.md
index ed508ce60..fa5d18352 100644
--- a//IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.md
+++ b//IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.md
@@ -110,0 +111,6 @@ As the account administrator, imagine that you want to allow the IAM user `DevUs
+JSON
+    
+
+****
+    
+    
@@ -138,0 +146,6 @@ To enforce the acceptable source identity values, you can configure the followin
+JSON
+    
+
+****
+    
+    
@@ -251,0 +266,6 @@ Imagine that you want to require your developers to set a source identity to ass
+JSON
+    
+
+****
+    
+    
@@ -297,0 +319,6 @@ Alternatively, if you use an OIDC provider for federation and users are authenti
+JSON
+    
+
+****
+    
+    
@@ -331,0 +360,6 @@ Imagine that you want to allow users who have assumed `CriticalRole` to assume a
+JSON
+    
+
+****
+    
+    
@@ -351,0 +387,6 @@ To secure setting source identity across the account boundary, the following rol
+JSON
+    
+
+****
+    
+