SETUP_GUIDE.md

AutiSense — Setup Guide

Quick Start

git clone https://github.com/Partha-dev01/AutiSense.git
cd AutiSense
npm install
cp .env.local.example .env.local
# Fill in .env.local with your values
npm run dev

Environment Variables

See .env.local.example for the full list of required variables.

The app works without AWS credentials — all API routes have template/fallback responses.

Local Development

For local AWS access, configure the AWS CLI profile or set these in .env.local:

AWS_REGION=ap-south-1
AWS_ACCESS_KEY_ID=<your-key>
AWS_SECRET_ACCESS_KEY=<your-secret>

Production (AWS Amplify)

Environment variables are configured in the Amplify Console:

• App-level: AWS credentials (APP_* prefix — Amplify blocks AWS_*)
• Branch-level: Google OAuth, DynamoDB table names, Bedrock/Polly regions

Warning: aws amplify update-app --environment-variables REPLACES the entire map. Always pass ALL vars when using the CLI. Use the Amplify Console UI for safer edits.

CRITICAL: next.config.ts env: Block

Amplify WEB_COMPUTE does NOT inject env vars into the Lambda runtime at request time. Every env var needed by API routes MUST be listed in the next.config.ts env: block to be baked at build time. This includes secrets (APP_ACCESS_KEY_ID, APP_SECRET_ACCESS_KEY, GOOGLE_CLIENT_SECRET).

Never remove ANY variable from the env: block without verifying the Lambda can still read it. Removing credentials broke DynamoDB, Bedrock, Polly, and auth — twice (2026-04-05).

Testing

npm run test:unit      # Vitest unit tests (68 tests, also runs in Amplify preBuild)
npx playwright test    # Playwright E2E tests (~71 tests)
npm run lint           # ESLint
npm run type-check     # TypeScript

Deployment

Pushes to main auto-deploy via GitHub webhook to AWS Amplify.

# Manual redeploy
aws amplify start-job --app-id <APP_ID> --branch-name main --job-type RELEASE --region ap-south-1

Architecture

See DOCS.md for the full architecture reference, and Amazon_usage.md for AWS service details.