personal-lifecycle-tracker / docs / deployment / aws-cloudformation.md
aws-cloudformation.md
Raw

Deploying Personal Lifecycle Tracker to AWS via CloudFormation (Serverless)

This guide covers deploying the Personal Lifecycle Tracker to Amazon Web Services using AWS CloudFormation across two independent serverless environments:

  1. Development Environment (dev): cloudformation/aws-serverless-lambda.yaml — Default environment dev, 100% serverless with Lambda + S3 + CloudFront + SNS on-call responder.
  2. Production Environment Copy (production): cloudformation/aws-serverless-lambda-prod.yaml — Default environment production, independent copy with CloudWatch alarms and automated on-call responder.

Both templates deploy self-contained, Free-Tier eligible infrastructure stacks with zero EC2 instances, zero servers to maintain, and $0.00/month idle cost.

Comparison Matrix

Property Development (aws-serverless-lambda.yaml) Production (aws-serverless-lambda-prod.yaml)
Default Stack Name personal-lifecycle-tracker-dev personal-lifecycle-tracker-prod
Environment Parameter dev production
Backend Compute AWS Lambda Function URL (512 MB) AWS Lambda Function URL (512 MB)
Frontend CDN CloudFront CDN + Private S3 Origin (OAC) CloudFront CDN + Private S3 Origin (OAC)
Database Neon Serverless PostgreSQL (over TLS) Neon Serverless PostgreSQL (over TLS)
On-Call Incident Responder Amazon SNS + Lambda Responder Function Amazon SNS + Lambda Responder Function
Idle Cost $0.00 / month $0.00 / month

Deployment Option 1: AWS Management Console (1-Click Upload)

  1. Log in to the AWS Console: Navigate to the AWS CloudFormation Console.

  2. Create Stack:

  3. Specify Stack Details:

    • Stack name: personal-lifecycle-tracker-dev (or personal-lifecycle-tracker-prod)
    • Environment: dev or production
    • DatabaseUrl: Your Neon serverless postgres pooled connection string
    • SecretKey: Secure JWT signing key (at least 32 characters)
    • Click Next.

  4. Review and Acknowledge:

    • Check the box: "I acknowledge that AWS CloudFormation might create IAM resources."
    • Click Submit.

Deployment Option 2: Containerized Makefile Validation & Deployment

In accordance with the Zero-Host-Runtime Mandate, validate and deploy inside Docker without host dependencies:

# Validate both dev and prod CloudFormation templates
make cf-validate

# Deploy Dev Environment via CloudFormation
make cf-deploy-dev

# Deploy Production Environment via CloudFormation
make cf-deploy-prod

# Check Stack Deployment Status
make cf-status-dev
make cf-status-prod

Live Verified Deployment Endpoints (Criterion 8 — 2 Points)

The serverless production environment matching the CloudFormation architecture is live and reachable:

Service / Interface Public URL Description Status
Web Application (SPA) https://d1ca9upoitnq9b.cloudfront.net/ CloudFront CDN distribution edge backed by private S3 bucket HTTP/2 200
Backend API Health https://7ksomsylvke2uawuhhccbfr6hy0agzyb.lambda-url.ap-south-1.on.aws/health AWS Lambda Function URL connected to Neon PostgreSQL {"status":"healthy","database":"connected","version":"1.0.0"}
Interactive Swagger Docs https://7ksomsylvke2uawuhhccbfr6hy0agzyb.lambda-url.ap-south-1.on.aws/docs Interactive Swagger UI testing endpoints with live queries HTTP 200
Interactive ReDoc https://7ksomsylvke2uawuhhccbfr6hy0agzyb.lambda-url.ap-south-1.on.aws/redoc Searchable API contract reference HTTP 200
OpenAPI Schema https://7ksomsylvke2uawuhhccbfr6hy0agzyb.lambda-url.ap-south-1.on.aws/openapi.json Dynamic OpenAPI 3.1.0 JSON specification Valid JSON

Verification Commands

# 1. Verify CloudFront edge response
curl -sI https://d1ca9upoitnq9b.cloudfront.net/ | grep -E "HTTP|server|via"

# 2. Verify Lambda backend health & DB connection
curl -s https://7ksomsylvke2uawuhhccbfr6hy0agzyb.lambda-url.ap-south-1.on.aws/health

# 3. Test login with pre-seeded reviewer user
curl -s -X POST https://7ksomsylvke2uawuhhccbfr6hy0agzyb.lambda-url.ap-south-1.on.aws/api/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"alex@example.com","password":"password123"}' | grep -o '"email":"alex@example.com"'
Powered by GitFront