Local Setup

Local development targets the event-driven-serverless-platform-demo monorepo. Terraform Terraform
HashiCorp Terraform — provisions all platform infrastructure through five modules in `terraform/`. provisions AWS AWS
Amazon Web Services — cloud platform for ingest, processing, storage, API, and portal hosting in this walkthrough. resources; services and the portal can be developed and tested locally.

Clone the demo repo

git clone https://github.com/jajera/event-driven-serverless-platform-demo.git
cd event-driven-serverless-platform-demo

Confirm Tools and Accounts are installed.

Lambda services

Python 3.14 services live under services/:

Service	Path	Runtime
Ingest-sync	services/ingest-sync/	Python 3.14 zip Lambda Lambda AWS Lambda — serverless compute for ingest-sync, query-api, reprocess-api, and the processor container image.
Query API	services/query-api/	Python 3.14 zip Lambda
Reprocess API	services/reprocess-api/	Python 3.14 zip Lambda
Processor	Container image (external)	Python 3.13 in ghcr.io/platformfuzz/tec-processor-image

Run service unit tests

Each service includes tests under tests/:

cd services/ingest-sync && python3 -m pytest
cd services/query-api && python3 -m pytest
cd services/reprocess-api && python3 -m pytest

Rebuild Lambda packages

Terraform packages zip Lambdas during apply. To rebuild manually:

./scripts/build-lambda-packages.sh

Portal (web/)

cd web
npm install
npm test
npm run build

Build output lands in web/dist/.

Caution

npm run dev against the live API Gateway API Gateway
Amazon API Gateway — REST API exposing `/catalog`, `/query`, and `/reprocess`. Browser CORS is locked to the Amplify hostname; CLI clients call the API Gateway URL directly. URL will fail in the browser due to CORS. Use curl for API testing during local UI development, or deploy to Amplify Amplify
AWS Amplify — hosts the Vite portal SPA. This walkthrough deploys via manual zip upload (no Git connection required). and complete CORS Lockdown.

Deploy UI changes to Amplify

After local changes, ship to the hosted portal:

export WEB_SOURCE_DIR="$(pwd)/web"
export AMPLIFY_APP_ID="$(terraform -chdir=terraform output -raw amplify_app_id)"
export VITE_API_URL="$(terraform -chdir=terraform output -raw api_url)"
./scripts/deploy-amplify.sh

Requires a prior Terraform apply with the presentation layer enabled.

Processor image development

The processor processor
Processor Lambda container — runs PyTECGg calibration per SQS message; adopted when a Batch on Fargate parallel-execution quota increase was rejected. Image from `ghcr.io/platformfuzz/tec-processor-image` mirrored to ECR. runs as an external container image. This repo mirrors it to ECR ECR
Amazon Elastic Container Registry — stores the mirrored processor Lambda container image at deploy time. — it does not maintain processor source code locally. To deploy a different tag:

./scripts/sync-processor-image.sh <tag>
terraform -chdir=terraform apply -var="processor_image_tag=<tag>"

Related pages

• Environment Variables — Lambda env var reference
• Amplify Portal