Architectural overview of Oxy deployment options using AWS infrastructure including EC2 and ECS patterns
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.
Oxy supports two primary AWS deployment patterns, each optimized for different use cases:
Direct virtual machine deployment offering simplicity and full control.
Container-based deployment with automatic scaling and high availability.
Feature | EC2 Deployment | ECS Deployment |
---|---|---|
Complexity | Low | Medium |
Scalability | Manual | Automatic |
Availability | Single AZ | Multi-AZ |
Storage | EBS (10GB) | EFS (Shared) |
Cost | Fixed instance cost | Pay per use |
Maintenance | Manual updates | Managed by AWS |
Debugging | SSH access | CloudWatch logs |
Ideal for | Development, Small teams | Production, Large teams |
Choose your deployment architecture and authentication method:
Recommendation: Start with built-in authentication for faster setup, then migrate to Cognito for enterprise requirements.