AWS Security ChangesHomeSearch

AWS lambda documentation change

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

File: lambda/latest/dg/urls-auth.md

Summary

Added multiple JSON section markers with formatting elements

Security assessment

Formatting changes to function URL authentication documentation without modifying security controls or adding new security features.

Diff

diff --git a/lambda/latest/dg/urls-auth.md b/lambda/latest/dg/urls-auth.md
index e5f233d2f..2e0c9610c 100644
--- a//lambda/latest/dg/urls-auth.md
+++ b//lambda/latest/dg/urls-auth.md
@@ -51,0 +52,6 @@ For an example cross-account interaction, the following resource-based policy al
+JSON
+    
+
+****
+    
+    
@@ -119,0 +127,6 @@ If you choose the `NONE` auth type, Lambda doesn't use IAM to authenticate reque
+JSON
+    
+
+****
+    
+    
@@ -174,0 +189,6 @@ To allow or deny function URL access to other AWS entities, include these action
+JSON
+    
+
+****
+    
+    
@@ -197,0 +219,6 @@ You can use this condition key in policies associated with your function. For ex
+JSON
+    
+
+****
+    
+    
@@ -221,0 +250,6 @@ To grant the `example` role in AWS account `444455556666` permissions to make `C
+JSON
+    
+
+****
+    
+    
@@ -248,0 +284,6 @@ You can also use this condition key in a [service control policy](https://docs.a
+JSON
+    
+
+****
+    
+