Brice Pellé

see here to learn more about the `info` object: https://aws.amazon.com/blogs/mobile/appsync-and-the-graphql-info-object/ If you use a Direct Lambda Resolver, the `info` object is sent automatically to your Lambda function

Hey, to filter, you should look at using subscription arguments in your query. see here for examples: https://docs.aws.amazon.com/appsync/latest/devguide/aws-appsync-real-time-data.html#using-subscription-arguments

you need to provide a path. try doing this instead: ```vtl { "version": "2018-05-29", "operation": "UpdateItem", "key": { "topicId": $util.dynamodb.toDynamoDBJson($ctx.stash.topicId) }, "update" : { "expression" : "SET userStatus = if_not_exists(userStatus.#idx,...

looks like the issue is that your main type expects the following fields: id: ID! title: String! content: String! the `!` at the end of the type means that these...

I recommend opening a ticket on Amplify DataStore since you are using a `@model` and the resolver functionality is generated using the amplify cli.

Hi, this is currently not supported in AppSync. However, I recommend looking at [Amplify DataStore](https://docs.amplify.aws/lib/datastore/getting-started/q/platform/js/) which can help you syncrhonize data to your device/application.

That's correct, when AppSync logs the `context` object, sensitive information is removed from the log message. However, we do not edit/redact any information that is logged via `console.log` functions. The...

AWS AppSync supports CORS, but does not support cookies as an authorization method

posted a proposal here https://github.com/aws/aws-appsync-community/issues/147 please comment.

We now support early return to skip data source request in a function or resolver. See details: https://docs.aws.amazon.com/appsync/latest/devguide/runtime-utils-js.html