AWS organizations documentation change

Service: organizations · 2025-07-18 · Documentation low

File: organizations/latest/userguide/orgs_tagging_abac.md

Summary

Added JSON code block markers and section dividers (****) to policy examples

Security assessment

The changes improve formatting of ABAC policy examples but do not address specific security vulnerabilities. ABAC is a security feature, so documentation updates help clarify proper implementation.

Diff

diff --git a/organizations/latest/userguide/orgs_tagging_abac.md b/organizations/latest/userguide/orgs_tagging_abac.md
index e3ac428ae..bb96dfd46 100644
--- a//organizations/latest/userguide/orgs_tagging_abac.md
+++ b//organizations/latest/userguide/orgs_tagging_abac.md
@@ -33,0 +34,6 @@ For example, the following sample policy allows the user or role to perform any
+JSON
+    
+
+****
+    
+    
@@ -64,0 +72,6 @@ The following example shows how to allow an action only when the specified tag (
+JSON
+    
+
+****
+    
+    
@@ -92,0 +107,6 @@ You can use [`ForAllValues:`](https://docs.aws.amazon.com/IAM/latest/UserGuide/r
+JSON
+    
+
+****
+    
+    
@@ -113,0 +135,6 @@ Alternatively, you can use [`ForAnyValue:`](https://docs.aws.amazon.com/IAM/late
+JSON
+    
+
+****
+    
+    
@@ -136,0 +165,6 @@ For example, the following sample policy denies any request by the user or role
+JSON
+    
+
+****
+    
+