​

DynamoDB to Supabase Streaming - Deployment Guide

​

Overview

​

Prerequisites

• AWS CLI configured with appropriate permissions
• CDK installed (npm install -g aws-cdk)
• Supabase project with scenarios table created
• Environment variables configured

​

Environment Setup

1. Create .env file in aws/ai/ directory:

ANTHROPIC_API_KEY=your_anthropic_key_here
SUPABASE_PASSWORD=your_supabase_password_here

2. Create scenarios table in Supabase:

CREATE TABLE scenarios (
    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    user_id TEXT NOT NULL,
    consultation_id TEXT,
    scenario_data JSONB NOT NULL,
    created_at TIMESTAMPTZ DEFAULT NOW(),
    updated_at TIMESTAMPTZ DEFAULT NOW(),
    dynamo_sequence_number TEXT UNIQUE NOT NULL,
    dynamo_event_name TEXT NOT NULL
);

CREATE INDEX idx_scenarios_user_id ON scenarios (user_id);
CREATE INDEX idx_scenarios_consultation_id ON scenarios (consultation_id);

​

Deployment Commands

​

Dev Environment (Safe - Won’t Affect Production)

cd aws
cdk deploy -c env=dev

​

Production Environment (Uses Existing Stack)

cd aws
cdk deploy

​

Post-Deployment Steps

1. Get NAT Gateway IP from CDK output
2. Add IP to Supabase network restrictions:
   • Go to Supabase Dashboard → Settings → Database
   • Add the NAT Gateway IP to allowed connections

​

Verification

1. Check Lambda functions are deployed
2. Verify DynamoDB streams are enabled
3. Test by creating a consultation - data should appear in Supabase scenarios table
4. Monitor CloudWatch logs for any errors

​

Architecture

DynamoDB → DynamoDB Streams → Lambda → VPC NAT Gateway → Supabase