Currently, resolver functions are invoked only with the GraphQL arguments or the resolved field. The identity field or any other (possibly user-defined) field of the $context object is dropped.
This makes it impossible to perform resource-based authorization based on $context.indentity.username or $context.identity.cognitoIdentityId (see AWS AppSync Developer Guide) in Lambda resolvers.
Currently, resolver functions are invoked only with the GraphQL arguments or the resolved field. The
identity
field or any other (possibly user-defined) field of the$context
object is dropped.https://github.com/sbstjn/appsync-resolvers/blob/08cb572f11cd9cf4088e0af5f1e005c2bf3d58ed/repository.go#L27
This makes it impossible to perform resource-based authorization based on
$context.indentity.username
or$context.identity.cognitoIdentityId
(see AWS AppSync Developer Guide) in Lambda resolvers.