Deployment Guide
This guide walks you through deploying B4M on your own AWS account. Your deployment runs entirely in your AWS infrastructure - no traffic flows through Bike4Mind's systems.
Deployment Paths
| Path | Best For | CI/CD |
|---|---|---|
| GitHub Actions (Recommended) | Most customers | GitHub Actions |
| Seed | Legacy/existing Seed users | Seed CI/CD |
Quick Start Checklist
- Prerequisites - AWS account, VPC, Route53, database
- Secrets Configuration - SST secrets setup
- CI/CD Setup - GitHub Actions or Seed
- Initial Deployment - First deploy
- Custom Domain - OAuth, DNS, SSL configuration
Architecture Overview
Your fork deployment includes:
| Component | Purpose |
|---|---|
| CloudFront | CDN and routing (only public entry point) |
| Lambda | Serverless compute (~15 functions) |
| S3 | File storage (6 buckets) |
| SQS | Message queues (11 queues + DLQs) |
| VPC | Network isolation |
| Bedrock | AI/ML models |
See Architecture for complete AWS services inventory, security architecture, VPC configuration, cost estimates, and compliance information.
Key Concepts
Environment-Driven Configuration
All configuration is environment-variable driven through SST. No code changes required for domain migration or deployment.
Domain Pattern
B4M uses the app.${SERVER_DOMAIN} pattern:
| SERVER_DOMAIN | Resulting URL |
|---|---|
example.com | https://app.example.com |
staging.example.com | https://app.staging.example.com |
Security Model
- All Lambda functions run in private VPC subnets
- Database has NO public internet access
- S3 buckets blocked from direct access (CloudFront-only)
- All secrets stored in AWS Secrets Manager
Documentation Map
| Document | Purpose |
|---|---|
| Prerequisites | AWS account setup, VPC, Route53 |
| Secrets Reference | All SST secrets with explanations |
| Domain Migration | Custom domain and OAuth setup |
| Architecture | Complete infrastructure reference |
| CI/CD Setup | GitHub Actions or Seed configuration |
| Email Setup | SES configuration for platform email |
| Troubleshooting | Common issues and solutions |
Support
For deployment issues:
- Check Troubleshooting for common problems
- Review CloudWatch logs for detailed error messages
- Use the Admin > System Health panel to verify configuration
- Contact Bike4Mind support for complex issues