AWS sagemaker documentation change

Service: sagemaker · 2025-06-25 · Documentation low

File: sagemaker/latest/dg/sms-custom-templates-step3-lambda-permissions.md

Summary

Added JSON section markers and formatting elements in multiple locations

Security assessment

Changes add structural markers for JSON policy examples but do not address specific vulnerabilities. The documentation relates to Lambda permissions configuration which is security-related.

Diff

diff --git a/sagemaker/latest/dg/sms-custom-templates-step3-lambda-permissions.md b/sagemaker/latest/dg/sms-custom-templates-step3-lambda-permissions.md
index 4d69e5d82..a5a78f44f 100644
--- a//sagemaker/latest/dg/sms-custom-templates-step3-lambda-permissions.md
+++ b//sagemaker/latest/dg/sms-custom-templates-step3-lambda-permissions.md
@@ -44,0 +45,6 @@ Additionally, if you want the user to be able to access and deploy the Ground Tr
+JSON
+    
+
+****
+    
+    
@@ -77,0 +85,6 @@ If the pre-annotation or post-annotation Lambda function names do not include on
+JSON
+    
+
+****
+    
+    
@@ -114,0 +129,6 @@ To allow a Lambda function to assume a SageMaker AI execution role, you must att
+JSON
+    
+
+****
+    
+    
@@ -125,0 +147,6 @@ To allow a Lambda function to assume a SageMaker AI execution role, you must att
+JSON
+    
+
+****
+    
+    
@@ -145,0 +174,6 @@ You can add a policy similar to the following to the post-annotation Lambda func
+JSON
+    
+
+****
+    
+