ARCHLEXOSS

AWS · Data & Analytics

Event-Driven Data Ingestion Pipeline

High-throughput event streaming with API Gateway, EventBridge, SNS, SQS, Lambda workers, DynamoDB, and S3 Data Lake. This diagram is written in ArchLex and passes AWS provider checks.

Edit in the playgroundAWS diagrams as code
Event-Driven Data Ingestion Pipeline: High-throughput event streaming with API Gateway, EventBridge, SNS, SQS, Lambda workers, DynamoDB, and S3 Data LakeEvent-Driven Data Ingestion Pipeline: High-throughput event streaming with API Gateway, EventBridge, SNS, SQS, Lambda workers, DynamoDB, and S3 Data Lake
provider aws
direction LR
validation normal

ingress_api: api-gateway
ingest_fn: lambda
events_bus: eventbridge
notification_topic: sns
buffer_queue: sqs
processor_fn: lambda
lake: s3
nosql_store: dynamodb

ingress_api -[invokes]-> ingest_fn
ingest_fn -[publishes]-> notification_topic
notification_topic -[publishes]->|forwards| buffer_queue
events_bus -[triggers]-> buffer_queue
buffer_queue -[invokes]->|batch| processor_fn
processor_fn -[writes]-> nosql_store
processor_fn -[archives]-> lake

What is in this diagram.

Resources

Relationships

Render it yourself.

Save the source as event-data-pipeline.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.

npx @archlex/cli render event-data-pipeline.arch --output event-data-pipeline.svg

All examples