Tools and Accounts

Before cloning the event-driven-serverless-platform-demo, confirm your local toolchain and AWS AWS
Amazon Web Services — cloud platform for ingest, processing, storage, API, and portal hosting in this walkthrough. account access. All Terraform Terraform
HashiCorp Terraform — provisions all platform infrastructure through five modules in `terraform/`. commands in this walkthrough run from the demo repository root with -chdir=terraform.

Required tools

Tool	Minimum version	Verify command	Walkthrough usage
AWS CLI	v2	aws —version	Deploy verification, SQS/S3/Lambda checks, SNS subscribe
Terraform Terraform HashiCorp Terraform — provisions all platform infrastructure through five modules in `terraform/`.	1.6+	terraform —version	Full infrastructure provisioning
Node.js	20+	node —version	Portal build, Amplify Amplify AWS Amplify — hosts the Vite portal SPA. This walkthrough deploys via manual zip upload (no Git connection required). deploy, unit tests
npm	bundled with Node	npm —version	Portal dependencies and build
Python	3.14+	python3 —version	Lambda Lambda AWS Lambda — serverless compute for ingest-sync, query-api, reprocess-api, and the processor container image. service development and local testing
Docker	with buildx	docker buildx version	Mirror processor image to ECR ECR Amazon Elastic Container Registry — stores the mirrored processor Lambda container image at deploy time. via sync-processor-image.sh
curl	any recent	curl —version	REST API verification
zip	any recent	zip —version	Amplify manual deploy packaging

Verify your toolchain

Run this block from any directory to confirm all tools are available:

aws --version
terraform --version
node --version
npm --version
python3 --version
docker buildx version
curl --version
zip --version

AWS account permissions

Your AWS credentials need permission to create and manage resources in the target region (default ap-southeast-2):

• S3 — Data lake bucket, object read/write, notifications
• Lambda — Functions, event source mappings, container images
• IAM — Roles and policies for Lambdas, Scheduler, API Gateway
• SQS — Standard queues and dead-letter queues
• DynamoDB — Jobs table
• API Gateway — REST API and stage deployment
• Amplify — App hosting and branch deploy
• EventBridge Scheduler — Schedule and execution role
• CloudWatch — Alarms, dashboard, logs
• ECR — Repository for processor container image
• SNS — Alarm notification topic

Caution

Use a dedicated sandbox account or scoped IAM role for first-time deploys. The full apply creates billable resources including Lambda, S3, and Amplify hosting.

Terraform working directory

All Terraform commands in this walkthrough use the demo repo root as the working directory:

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

# Example — init from repo root, not from terraform/
terraform -chdir=terraform init

Tip

Export a default region if your AWS CLI profile does not set one: export AWS_DEFAULT_REGION=ap-southeast-2

Next step

Continue to System Overview or start deploying with Terraform Init.