How cms-enterprise/ztmf works
Main Components
A. Client Layer:
• React SPA (in separate repository)
• CloudFront Distribution (primary entry point)
B. Security Layer:
• AWS Verified Access
• Okta IDM Integration
• Authentication/Authorization Components
C. Backend Services:
• REST API (Go-based)
• ETL Process (Go-based)
• ECS Fargate Containers
D. Data Layer:
• Aurora Serverless PostgreSQL (RDS)
• S3 Bucket (for static assets)
┌─ Client Tier ─────┐ ┌─ Security Tier ──┐ ┌─ Application Tier ─┐ ┌─ Data Tier ────┐
• React SPA │ │ - CloudFront │ │ - ECS Fargate │ │ - Aurora RDS │
• >│ - Verified Access │───>│ - REST API │───>│ - S3 Bucket │
• Okta IDM │ │ - ETL Process │ │ │
• ┘ └─────────────────┘ └──────────────────┘ └───────────────┘
Key Elements to Highlight
a. API Structure (from backend/cmd/api):
• Auth Module
• Controllers
• Models
• Router
• Migrations
b. Infrastructure Components (from infrastructure/):
• Load Balancers (ALB)
• VPC Configuration
• ECS/ECR Setup
• RDS Configuration
Important Flows
a. Authentication Flow:
User -> CloudFront -> Verified Access -> Okta IDM -> API
b. Data Flow:
API -> RDS (for data operations)
ETL -> RDS (for data loading)
Additional Details
Architectural elements:
• GitHub Actions workflows for CI/CD
• Internal ALB vs Public ALB
• VPC networking zones
• Security group relationships
Specific Implementation Notes
• The microservices architecture (API and ETL as separate services)
• The security-first approach (Zero Trust implementation)
• The cloud-native AWS infrastructure
• The separation of concerns between components