Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppSync EventAPI - Add DataSource - Lambda, EventBridge buses #2262

Open
luiscarlosjayk opened this issue Feb 16, 2025 · 0 comments
Open

AppSync EventAPI - Add DataSource - Lambda, EventBridge buses #2262

luiscarlosjayk opened this issue Feb 16, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@luiscarlosjayk
Copy link

luiscarlosjayk commented Feb 16, 2025

Name of the resource

AWS::AppSync::DataSource

Resource name

AWS::AppSync::Api

Description

Describe the feature

Same fashion that we can add DataSources like Lambda functions, EventBridge buses, and more, to AppSync GraphqlAPIs; think it would be really good if we could also attach data sources to AppSync EventAPIs.

And also attach an EventBridge bus as a publisher to a AppSync EventAPI, therefore we could send events from multiple services to clients via a bus.

Use Case

Feels like current AppSync EventAPI is missing a way to systems behind the client apps to react to subscriptions, connections and message publishes because they lack the capability to have datasources like a Lambda function or EventBridge bus.

Right now, we can:

  1. Allow connected and subscribed clients to talk among them by publishing messages to namespaces and channels.
  2. Fan out messages to connected and subscribed clients through EventBridge with ApiDestinations and Connections

But, it would be awesome if for example, we could add AWS Bedrock in the middle, triggering some AI work, and then spawning all subscribed clients with the result once it's ready.

Extra Request

Would be nice if incoming events apart of bringing the event detail itself, could say which connection id sent it, and to which namespace/channel. That would empower so many other use cases.

References

aws/aws-cdk#33458 (comment)

Thank you,
LuisK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant