AWS lambda documentation change

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

File: lambda/latest/dg/lambda-api-permissions-ref.md

Summary

Added multiple JSON section markers with formatting elements

Security assessment

Structural documentation changes without modifying security-related IAM policy examples or recommendations. Existing permission guidance remains intact.

Diff

diff --git a/lambda/latest/dg/lambda-api-permissions-ref.md b/lambda/latest/dg/lambda-api-permissions-ref.md
index 40b10282c..fef6e5a44 100644
--- a//lambda/latest/dg/lambda-api-permissions-ref.md
+++ b//lambda/latest/dg/lambda-api-permissions-ref.md
@@ -52,0 +53,6 @@ For example, the following policy allows a user in AWS account `123456789012` to
+JSON
+    
+
+****
+    
+    
@@ -88,0 +96,6 @@ For example, the `lambda:Principal` condition lets you restrict the service or a
+JSON
+    
+
+****
+    
+    
@@ -127,0 +142,6 @@ You can't use a wildcard character (*) to match the account ID. For more informa
+JSON
+    
+
+****
+    
+    
@@ -143,0 +165,6 @@ If your policy references a specific qualified ARN, Lambda accepts requests that
+JSON
+    
+
+****
+    
+    
@@ -159,0 +188,6 @@ If your policy references any qualified ARN using `:*`, Lambda accepts any quali
+JSON
+    
+
+****
+    
+    
@@ -175,0 +211,6 @@ If your policy references any ARN using `*`, Lambda accepts any qualified or unq
+JSON
+    
+
+****
+    
+