This document provides an architectural overview of the Oxy deployment options using AWS infrastructure. We support two primary deployment patterns: EC2-based and ECS-based deployments.

High-Level Architecture

With AWS Cognito Authentication

With Built-in Authentication (Simplified)

Deployment Architecture Options

Oxy supports two primary AWS deployment patterns, each optimized for different use cases:

EC2 Deployment

Direct virtual machine deployment offering simplicity and full control.

  • Best for: Development, small teams, direct server control
  • Key benefits: Simple setup, SSH access, cost-effective for steady workloads
  • Architecture: Single instance with EBS storage

ECS Deployment

Container-based deployment with automatic scaling and high availability.

  • Best for: Production environments, scalable applications, enterprise deployments
  • Key benefits: Auto-scaling, multi-AZ availability, managed infrastructure
  • Architecture: Fargate containers with EFS shared storage

Common Components

Authentication Flow

AWS Cognito Authentication Flow

Built-in Authentication Flow

Data Flow

Deployment Comparison

FeatureEC2 DeploymentECS Deployment
ComplexityLowMedium
ScalabilityManualAutomatic
AvailabilitySingle AZMulti-AZ
StorageEBS (10GB)EFS (Shared)
CostFixed instance costPay per use
MaintenanceManual updatesManaged by AWS
DebuggingSSH accessCloudWatch logs
Ideal forDevelopment, Small teamsProduction, Large teams

Next Steps

Choose your deployment architecture and authentication method:

EC2 Deployment

ECS Deployment

Recommendation: Start with built-in authentication for faster setup, then migrate to Cognito for enterprise requirements.