Optimizing Amazon EventBridge Pipes with Apache Kafka
summary
Confluent Kafka connects to AWS using EventBridge Pipes to route, filter and enrich Kafka records and keep consumer logic serverless; large records get uploaded to S3 and replaced with an S3 pointer using the claim-check pattern, preserving order and batches. EventBridge enforces a 256 KB limit (Kafka allows ~10 MB), so Pipes plus two small Lambdas handle S3 writes and lookups. API Destinations hit a hard 3,000 rps throttle. The pattern reduces custom consumers and works in production.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:44The challenge
- 3:57Why Kafka?
- 9:12EventBridge with Kafka
- 11:18EventBridge with Kafka alternative
- 17:05How we did this
- 23:26Implemented solution
- 29:51AWS wishes
- 34:49Summary
- 36:25Outro
related talks
38mEvent-driven Architecture
47mServerless Kafka Patterns.
42mBuilding real-time serverless data applications
38mServerless Data Streaming on AWS
28mBuilding Event Streaming Applications with Serverless Kafka
44mAdvanced Event-driven Architectures at
56mDesigning Event-Driven Applications to Improve Scalability
12mServerless Stream Processing with Confluent Cloud, Kafka and AWS Lambda
