Nicholas DeJaco

A workaround for supporting federation using Apollo Gateway to federate across multiple AppSync GraphQL Apis is provided here: https://github.com/apollographql/apollo-federation-subgraph-compatibility/tree/main/implementations/appsync

Hi, could you please share your request and response mapping templates?

> Whilst I appreciate that this solves a complex problem, without addressing the description issue (#38) combining multiple schemas together is going to cause a lot of confusion. Thanks for...

> It would be great if the Merged API's and Resolvers could be orchestrated through StepFunctions (both Express & Standard Modes) using pure ASL code. This would allow the process...

Hi Vicary thanks for your request :) Are you using VTL with your lambda resolvers or just direct lambda? What kind of cache keys would you like to use with...

The team is hard at work to launch this feature. We can share that we have decided to not support the @key directive at launch. We hope to be able...

We are happy to announce that Merged APIs has been released today for AWS AppSync. Launch blog: https://aws.amazon.com/blogs/mobile/introducing-merged-apis-on-aws-appsync/ Docs: https://docs.aws.amazon.com/appsync/latest/devguide/merged-api.html Whats new: https://aws.amazon.com/about-aws/whats-new/2023/05/aws-appsync-merged-apis-graphql-federation/

> Hey! Merged APIs works great! > > However I have a question about subscriptions. I've noticed, that subscriptions doesn't work for case, where subscriber listens for changes on merged...

Apologies for the late reply on this. Yes, these directives apply to the Merged API schema prior to execution. At execution time, a best practice would be for the resolvers...

This is intended behavior. You will need to have your EventBridge send a mutation to the Merged API rather than the source API if you want to trigger updates through...