AWS Security ChangesHomeSearch

AWS appsync documentation change

Service: appsync · 2026-05-04 · Documentation low

File: appsync/latest/devguide/configuration-limits.md

Summary

Updated image references and alt texts for introspection and query limit sections.

Security assessment

The changes are visual updates (image paths/alt text) illustrating existing security features like query depth limits. No new security documentation or vulnerability fixes.

Diff

diff --git a/appsync/latest/devguide/configuration-limits.md b/appsync/latest/devguide/configuration-limits.md
index 8b4c02390..bb70e6fbe 100644
--- a//appsync/latest/devguide/configuration-limits.md
+++ b//appsync/latest/devguide/configuration-limits.md
@@ -44 +44 @@ When introspection is enabled (the default behavior), using the introspection sy
-![GraphQL schema explorer showing query structure with types and name fields.](/images/appsync/latest/devguide/images/introspection-enabled.png)
+![GraphQL query editor showing MyQuery with schema introspection returning Query, String, Int, Schema, Type, and TypeKind types.](/images/appsync/latest/devguide/images/introspection-enabled.png)
@@ -48 +48 @@ When disabling this feature, a validation error will appear in the response inst
-![GraphQL query editor showing a validation error for undefined 'types' field in '_Schema'.](/images/appsync/latest/devguide/images/introspection-disabled.png)
+![GraphQL query editor showing validation error for undefined types field in schema.](/images/appsync/latest/devguide/images/introspection-disabled.png)
@@ -90 +90 @@ When a limit is set, going past its upper bound will result in a `QueryDepthLimi
-![Query structure with nested layers L1, L2, L3, and L4, showing depth limit exceeded.](/images/appsync/latest/devguide/images/query-depth-limit.jpg)
+![Query depth limit error showing nested query structure exceeding the configured limit of 2.](/images/appsync/latest/devguide/images/query-depth-limit.jpg)
@@ -130 +130 @@ Like the query depth limit, exceeding the configured resolver limit causes the q
-![Query with three resolvers, showing error on third resolver due to execution limit reached.](/images/appsync/latest/devguide/images/resolver-count-limit.jpg)
+![GraphQL query with three resolvers showing error when resolver count limit of two is exceeded.](/images/appsync/latest/devguide/images/resolver-count-limit.jpg)