dsql-cdc-eventbridge-fanout-cdk: DSQL CDC to EventBridge fan-out#3227
Open
NithinChandranR-AWS wants to merge 2 commits into
Conversation
Event-driven microservices pattern using Amazon Aurora DSQL CDC (GA July 2026) as a change event source. CDC events flow through Amazon Kinesis to AWS Lambda, which classifies operations and publishes typed events to Amazon EventBridge. Three independent consumers demonstrate content-based routing: Amazon SQS (audit), AWS Step Functions (validation), Amazon SNS (alerting). 7 AWS services, 29 CFN resources. Fundamentally different from existing apigw-lambda-dsql (basic CRUD) and sample-aurora-dsql-cdc-demo (RAG/semantic search). This pattern shows DSQL as an event source for microservices fan-out via EventBridge.
…e boto3 DSQL CDC uses Debezium-style format: op='c'/'u'/'d' with before/after fields. Map op codes to human-readable types for EventBridge routing. Bundle boto3>=1.43.36 via CDK Docker bundling (Lambda runtime ships older version without dsql.create_stream support). Deployed and tested end-to-end: - 3 records processed, 3 events published, 0 failures - Amazon SQS audit: receives all 3 event types (INSERT, UPDATE, DELETE) - AWS Step Functions: 1 INSERT validation SUCCEEDED - Amazon SNS: DELETE event routed to alerting topic
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Stream real-time database changes from Amazon Aurora DSQL via CDC to Amazon EventBridge for content-based routing to multiple consumers.
Architecture
Amazon Aurora DSQL (CDC) → Amazon Kinesis Data Streams → AWS Lambda (CDC processor) → Amazon EventBridge (custom bus) → 3 consumers:
What makes this different
This pattern is fundamentally different from:
apigw-lambda-dsql(existing, basic CRUD) — that treats DSQL as a target. This uses DSQL as an event source.sample-aurora-dsql-cdc-demo(separate repo) — that builds a RAG/chatbot with CDC → embeddings → S3 Vectors. This demonstrates event-driven microservices fan-out with content-based routing.7 AWS services composed. Removing any one breaks the architecture.
Implementation Notes
create_streamAPI (GA July 8, 2026)op='c'/'u'/'d'withbefore/afterpayloadDeployed and Tested
Stack deploys in us-east-1. All 3 fan-out targets verified: