AWS ses documentation change

Service: ses · 2025-06-28 · Documentation low

File: ses/latest/dg/sending-authorization-policy-examples.md

Summary

Added JSON section markers and formatting dividers (****) in multiple policy examples

Security assessment

Structural formatting improvements to existing authorization policy examples without security content changes

Diff

diff --git a/ses/latest/dg/sending-authorization-policy-examples.md b/ses/latest/dg/sending-authorization-policy-examples.md
index dc8cef10d..6df3ef360 100644
--- a//ses/latest/dg/sending-authorization-policy-examples.md
+++ b//ses/latest/dg/sending-authorization-policy-examples.md
@@ -70,0 +71,6 @@ The following example shows a simple policy that allows AWS ID _123456789012_ to
+JSON
+    
+
+****
+    
+    
@@ -99,0 +107,6 @@ The following example policy grants permission to two IAM users to send from ide
+JSON
+    
+
+****
+    
+    
@@ -124,0 +139,6 @@ The following example policy grants permission to Amazon Cognito to send from id
+JSON
+    
+
+****
+    
+    
@@ -154,0 +176,6 @@ The following example policy grants permission to all accounts within an AWS Org
+JSON
+    
+
+****
+    
+    
@@ -181,0 +210,6 @@ If you use a verified domain, you may want to create a policy that allows only t
+JSON
+    
+
+****
+    
+    
@@ -212,0 +248,6 @@ You can also configure your sender authorization policy so that a delegate sende
+JSON
+    
+
+****
+    
+    
@@ -252,0 +295,6 @@ If your use case is such that you want to restrict the action, you can do so by
+JSON
+    
+
+****
+    
+    
@@ -277,0 +327,6 @@ Some email clients display the "friendly" name of the email sender (if the email
+JSON
+    
+
+****
+    
+    
@@ -308,0 +365,6 @@ Your sending authorization policy can include multiple statements. The following
+JSON
+    
+
+****
+    
+