AWS appsync high security documentation change
Summary
Clarified Lambda authorization caching behavior for wildcard channels
Security assessment
Added explicit documentation about security-critical caching behavior when using wildcards in channel names, preventing potential authorization bypass through cache key handling
Diff
diff --git a/appsync/latest/eventapi/configure-event-api-auth.md b/appsync/latest/eventapi/configure-event-api-auth.md index 3b86d3e19..cefa64f0c 100644 --- a//appsync/latest/eventapi/configure-event-api-auth.md +++ b//appsync/latest/eventapi/configure-event-api-auth.md @@ -103 +103,5 @@ For example, if your authorization token is `'ABC123'`, you can publish via curl -Lambda functions are called before connection, publish, and subscription attempts. The return value can be cached based on the API ID and the authentication token. By default, caching is not turned on, but this can be enabled at the API level or by setting the `ttlOverride` value in a function's return value. +Lambda functions are called before connection, publish, and subscription attempts. When caching is turned on, the return value of the function will be cached based on API ID, channel, operation and the authentication token as applicable. + +###### Note + +For the connect operation (EVENT_CONNECT), caching is based on API ID, operation, and the authentication token because the channel name will not be available during the connect operation. Subscribe operation (EVENT_SUBSCRIBE) allows wildcards for channel names, in which case the channel name is used as a literal string along with API ID, operation, and the authentication token to cache Lambda function’s return value.