AWS lambda documentation change

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

File: lambda/latest/dg/attribute-based-access-control-example.md

Summary

Added JSON section markers with formatting elements

Security assessment

Changes add formatting elements (JSON markers and horizontal rules) but no actual security-related content. The modifications appear to be documentation structure improvements rather than security fixes or security feature additions.

Diff

diff --git a/lambda/latest/dg/attribute-based-access-control-example.md b/lambda/latest/dg/attribute-based-access-control-example.md
index 929b48110..76ec2ce37 100644
--- a//lambda/latest/dg/attribute-based-access-control-example.md
+++ b//lambda/latest/dg/attribute-based-access-control-example.md
@@ -45,0 +46,6 @@ When using ABAC with Lambda, it's a best practice to require that all functions
+JSON
+    
+
+****
+    
+    
@@ -73,0 +81,6 @@ Create a second IAM policy using the [aws:ResourceTag/tag-key](https://docs.aws.
+JSON
+    
+
+****
+    
+    
@@ -99,0 +114,6 @@ Create a policy that allows the principal to list Lambda functions and IAM roles
+JSON
+    
+
+****
+    
+    
@@ -126,0 +148,6 @@ Do not use the `ResourceTag` condition key in a policy with the `iam:PassRole` a
+JSON
+    
+
+****
+    
+    
@@ -160,0 +189,6 @@ It's a best practice to [use roles to delegate permissions](https://docs.aws.ama
+JSON
+    
+
+****
+    
+