AWS appsync documentation change

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

File: appsync/latest/devguide/attaching-a-data-source.md

Summary

Added JSON section markers/placeholders in IAM policy documentation examples

Security assessment

Changes appear to be formatting updates (adding JSON section markers and spacing) without modifying security content or introducing new security concepts. No evidence of security vulnerability fixes or new security feature documentation.

Diff

diff --git a/appsync/latest/devguide/attaching-a-data-source.md b/appsync/latest/devguide/attaching-a-data-source.md
index 28fd80c0b..2e8d1aaaf 100644
--- a//appsync/latest/devguide/attaching-a-data-source.md
+++ b//appsync/latest/devguide/attaching-a-data-source.md
@@ -245,0 +246,6 @@ If you’re using an existing IAM role for your data source, you need to grant t
+JSON
+    
+
+****
+    
+    
@@ -261,0 +269,6 @@ You can also add conditions to your trust policy to limit access to the data sou
+JSON
+    
+
+****
+    
+    
@@ -282,0 +297,6 @@ Alternatively, you can limit access to a data source to a specific API, such as
+JSON
+    
+
+****
+    
+    
@@ -303,0 +325,6 @@ You can limit access to all AWS AppSync APIs from a specific region, such as `us
+JSON
+    
+
+****
+    
+