Home Phase 4 GUI
Phase 4 of 6 🖱️ GUI Method

Data & Cache Layer

Configure Supabase and ElastiCache Redis using web interfaces

1-2 days
Intermediate Level
100% GUI
🚀 2025 Performance!
Redis 7.2 with Enhanced I/O provides 72% better throughput. All configurable through AWS Console!

Prerequisites

Step 1: Supabase Production Setup

What is Supabase?
Supabase is an open-source Firebase alternative providing PostgreSQL database, authentication, storage, and real-time subscriptions.
1.1

Upgrade to Production Plan

  • 1
    Log in to Supabase Dashboard
  • 2
    Select your project
  • 3
    Click "Settings" (gear icon) in left sidebar
  • 4
    Click "Billing"
  • 5
    Click "Upgrade to Pro"
    Pro plan: $25/month - includes daily backups, high availability
  • 6
    Enter payment information
  • 7
    Click "Confirm upgrade"
1.2

Enable Connection Pooling

  • 1
    Click "Settings" → "Database"
  • 2
    Scroll to "Connection pooling" section
  • 3
    Mode: Select Transaction
    Best for most applications
  • 4
    Copy the "Connection string"
    Note: Use port 6543 for pooled connections
Why Connection Pooling?
Connection pooling reuses database connections, reducing overhead and improving performance by up to 10x for high-traffic applications.
1.3

Configure Automated Backups

  • 1
    Click "Database" in left sidebar
  • 2
    Click "Backups" tab
  • 3
    Verify "Daily backups" is enabled
    Enabled by default on Pro plan
  • 4
    Retention: 7 days
  • 5
    Click "Create backup now" to test

Step 2: Create ElastiCache Redis Cluster

⚠️ 2025 Update!
Use Redis 7.2+ with Enhanced I/O for 72% better throughput. Select instance types with 4+ vCPUs (r7g.large or larger).
2.1

Navigate to ElastiCache

AWS Console Navigation
AWS Console → Search "ElastiCache" → Click "ElastiCache"
2.2

Create Redis Cluster

  • 1
    Click "Get started" or "Create"
  • 2
    Choose cluster creation method: Easy create
    Easier for beginners, or choose "Cluster cache" for more control
  • 3
    Cluster mode: Enabled
    Better for horizontal scaling
  • 4
    Cluster info:
Setting Value
Name helium-production-redis
Description Production Redis cache for Helium
Engine Redis
Engine version 7.2 (latest)
Port 6379 (default)
Parameter group default.redis7.cluster.on
Node type cache.r7g.large (Graviton3, 4+ vCPUs)
Number of shards 2
Replicas per shard 1 (for Multi-AZ)
  • 5
    Scroll to "Subnet group settings"
  • 6
    Click "Create new subnet group"
  • 7
    Name: helium-redis-subnet-group
  • 8
    VPC: Select helium-production-vpc
  • 9
    Subnets: Select your isolated subnets (10.0.20.0/24, 10.0.21.0/24)
  • 10
    Click "Create"
2.3

Configure Security Settings

  • 1
    Scroll to "Security" section
  • 2
    Security groups: Select helium-elasticache-sg
  • 3
    Encryption at rest: Enabled
  • 4
    Encryption in transit: Enabled
  • 5
    Auth token: Leave empty (or set if needed)
2.4

Configure Backup Settings

  • 1
    Scroll to "Backup" section
  • 2
    Enable automatic backups: Yes
  • 3
    Backup retention period: 7 days
  • 4
    Backup window: 03:00-05:00 UTC
    Choose low-traffic hours
2.5

Add Tags and Create

  • 1
    Scroll to "Tags" section
  • 2
    Add tags:
Key Value
Project helium
Environment production
ManagedBy console
  • 3
    Review all settings
  • 4
    Click "Create"
    ⏳ Cluster creation takes 10-15 minutes
☕ Take a Break!
While the cluster is being created, you can grab a coffee. AWS will show a progress indicator.
2.6

Get Redis Endpoint

  • 1
    Wait for cluster status to show Available
  • 2
    Click on your cluster name
  • 3
    Copy the "Configuration endpoint"
    Example: helium-production-redis.abc123.clustercfg.use1.cache.amazonaws.com:6379
  • 4
    Save this endpoint - you'll need it for backend configuration

Step 3: Update Backend with Redis Endpoint

3.1

Update Secrets Manager

AWS Console Navigation
AWS Console → Search "Secrets Manager" → Click "Secrets Manager"
  • 1
    Find your secret: helium/backend/production
  • 2
    Click on the secret name
  • 3
    Click "Retrieve secret value"
  • 4
    Click "Edit"
  • 5
    Update REDIS_HOST with your ElastiCache endpoint
  • 6
    Click "Save"
3.2

Force New ECS Deployment

AWS Console Navigation
AWS Console → Search "ECS" → Clusters → helium-production-cluster
  • 1
    Click on helium-backend-service
  • 2
    Click "Update service"
  • 3
    Check "Force new deployment"
  • 4
    Click "Update"
    This will restart tasks with new Redis configuration
✅ Redis Connected! Your backend will now use ElastiCache for caching and session management.

Phase 4 Verification Checklist

✅ Phase 4 Complete! Your data and cache layers are configured. Ready for Phase 5!
Back to Phase 3 Next: Phase 5 - Agent Execution