🍔 DaBurgger - Architecture 🍔

Context

This project is my first take at building something using AWS. It is a support site for my @daburgger Instagram page. The end goal is a platform where anyone can add their own burgers.

Architecture Overview

DaBurgger is a lightweight, serverless web application. The static frontend lives in Amazon S3 and is served worldwide via Amazon CloudFront. Dynamic requests go through Amazon API Gateway, which triggers AWS Lambda functions to handle business logic and interact with Amazon DynamoDB for burger information storage. Amazon Cognito handles sign-in for the admin (so far just me). POST/DELETE API are private while GET remains public. IAM manages secure permissions between services, and AWS Cost Explorer keeps budgets in check. This architecture is built for global reach, low cost, and zero server maintenance.

AWS Services

• Amazon S3 — Hosts the static frontend (HTML, CSS, JS) for main site and admin.
• Amazon CloudFront — CDN delivering the site globally and proxying API requests.
• Amazon Route 53 — Custom domain daburgger.com with DNS routing to CloudFront.
• Amazon API Gateway — Handles HTTP API requests; JWT authorizer (Cognito) protects POST /burgers and DELETE /burgers/{id}; GET /burgers stays public.
• AWS Lambda — Backend logic for listing, adding, and deleting burgers.
• Amazon DynamoDB — NoSQL database storing burger entries and metadata.
• Amazon Cognito — Manages user pool for admin access to POST and DELETE APIs.
• AWS IAM — Role-based permissions for Lambda and other services.
• AWS Cost Explorer — Budgets and cost tracking to manage spending.

Non-AWS Services

• GitHub — Repo link here — Source control & version tracking
• VS Code — Development environment, connected to GitHub and AWS S3 through yaml
• Postman — API testing
• Draw.io / Lucidchart — Architecture diagram creation
• Instagram — @daburgger community & content source
• ChatGPT — Development guidance, code generation, and troubleshooting

Architecture Diagram

• Static Content — HTML, CSS, and JS are cached in CloudFront and served from S3.
• API Requests — Frontend calls to /burgers are routed via CloudFront to API Gateway.
• Business Logic — API Gateway invokes Lambda functions (getAllBurgersPython, addBurgerPython, deleteBurgerPython).
• Data Storage — Lambda reads/writes items in DynamoDB using IAM-secured access.
• Authentication — The browser sends a login token with the request. API Gateway checks that token for POST and DELETE, but not for GET..