Use Case
EventCatalog currently supports AWS API Gateway, which works well for REST‑based and HTTP‑driven event sources.
However, teams building event‑driven architectures on AWS increasingly use AWS AppSync for:
GraphQL APIs
Real‑time subscriptions
Event‑backed resolvers (e.g. via EventBridge, Lambda, or other AWS services)
At the moment, there is no native way to represent AppSync APIs and their associated events in EventCatalog, which creates a gap for teams that standardise on GraphQL and AppSync rather than REST.
Proposed Solution
Introduce an AWS AppSync integration that aligns with the existing AWS API Gateway support.
At a high level, the integration could:
Discover AppSync APIs within an AWS account
Map AppSync operations (queries, mutations, subscriptions) to EventCatalog concepts
Allow teams to document the events produced and consumed by AppSync‑backed systems
Fit naturally into the existing EventCatalog generator/integration patterns
The goal would be conceptual parity with the AWS API Gateway integration, rather than introducing a completely new mental model.
Implementation Notes
Example use cases
Documenting GraphQL subscription events as first‑class events in EventCatalog
Visualising which services publish or consume events via AppSync
Keeping event documentation in sync as AppSync schemas evolve
Supporting organisations that use GraphQL as their primary integration layer
Why this is valuable
AppSync is a core AWS service for modern, event‑driven and real‑time architectures
Many teams do not use API Gateway at all for GraphQL workloads
Native AppSync support would broaden EventCatalog’s usefulness across AWS‑centric platforms
Aligns well with EventCatalog’s mission of improving event discovery and ownership
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.
- If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.
Use Case
EventCatalog currently supports AWS API Gateway, which works well for REST‑based and HTTP‑driven event sources.
However, teams building event‑driven architectures on AWS increasingly use AWS AppSync for:
GraphQL APIs
Real‑time subscriptions
Event‑backed resolvers (e.g. via EventBridge, Lambda, or other AWS services)
At the moment, there is no native way to represent AppSync APIs and their associated events in EventCatalog, which creates a gap for teams that standardise on GraphQL and AppSync rather than REST.
Proposed Solution
Introduce an AWS AppSync integration that aligns with the existing AWS API Gateway support.
At a high level, the integration could:
Discover AppSync APIs within an AWS account
Map AppSync operations (queries, mutations, subscriptions) to EventCatalog concepts
Allow teams to document the events produced and consumed by AppSync‑backed systems
Fit naturally into the existing EventCatalog generator/integration patterns
The goal would be conceptual parity with the AWS API Gateway integration, rather than introducing a completely new mental model.
Implementation Notes
Example use cases
Documenting GraphQL subscription events as first‑class events in EventCatalog
Visualising which services publish or consume events via AppSync
Keeping event documentation in sync as AppSync schemas evolve
Supporting organisations that use GraphQL as their primary integration layer
Why this is valuable
AppSync is a core AWS service for modern, event‑driven and real‑time architectures
Many teams do not use API Gateway at all for GraphQL workloads
Native AppSync support would broaden EventCatalog’s usefulness across AWS‑centric platforms
Aligns well with EventCatalog’s mission of improving event discovery and ownership
Community Notes