← Quench

How Quench runs on AWS

One CloudFront address serves the site and the API. Everything below runs in ap-south-1 (Mumbai) and is deployed with one SAM template.

Quench architecture Phones reach CloudFront. CloudFront serves the site from S3 and forwards /api to API Gateway and the API Lambda. Taps go through SQS to a consumer Lambda that writes to DynamoDB. EventBridge Scheduler runs the projector Lambda every 2 minutes, which starts Step Functions dispatch executions. All functions log to CloudWatch. Phones Volunteer: taps Runner: jobs Organiser: plan, board, summary CloudFront https, one address / → site, /api → API S3 website (private) API Gateway + Lambda (API) events, taps, runners SQS tap queue + dead-letter queue Lambda writes each tap once DynamoDB one table EventBridge Scheduler → Lambda every 2 min: when will each station run dry? silent stations? Step Functions (dispatch) assign runner → wait "On my way" (reassign) → wait "Delivered" CloudWatch Logs: every function, every scheduler run /api taps read / write start job "Last jar", runner taps

Why each service