Ed Lima

Could you please confirm if the documented solution works out for you? https://docs.aws.amazon.com/appsync/latest/devguide/resolver-mapping-template-reference-lambda.html#lambda-mapping-template-bypass-errors

Thank you for providing the fix, @DmitryZamura . Would you mind creating a pull request?

The idea is that all the utilities currently provided by VTL ($util) are available for JavaScript Resolvers unless there’s a related utility already available natively on JavaScript (i.e. JSON.stringify, JSON.parse)....

@thisisxvr we're evaluating different options. Thanks for sharing.

Indeed Enhance Filtering only supports top level objects/types for now however we are planning to support nested types in the future. Would you mind sharing your use case, if possible...

Give it a try with our new WebSockets implementation, it should return an error: https://aws.amazon.com/blogs/mobile/appsync-realtime/

If you want to use the new pure WebSockets support your client must connect to the appsync-realtime-api endpoint. If you're using the AppSync SDK or Amplify clients they will automatically...

Hi Erik, Unfortunately indeed AppSync does not support IAM resource-based policies yet. However while I cannot share ETAs this in our backlog, stay tuned! Ed

+1 I've used parts of this code (which is great, BTW) for CUP authentication to API Gateway in a web app where I'm using Observables to communicate to my API...

We just released a sample today that takes advantage of AWS Amplify, Cognito and Angular: https://github.com/aws-samples/aws-mobile-appsync-chat-starter-angular