Overview

Development Environment

Deployed on: ap-south-1

→ Deployed Admin Dashboard

The development architecture of AngelX consists of several key components operating within AWS:

Resource Naming Convention

All AWS resources follow a consistent naming pattern:

• Base name: angel-saas-{service-name}
• Development suffix: -dev

Examples:

• Repository: angel-saas-ai-engine-api
• Lambda function: angel-saas-ai-engine-api-dev
• API Gateway: angel-saas-ai-engine-api-dev
• RDS instance: angel-saas-dev

Frontend Layer

• Admin Dashboard powered by AWS Amplify
• Bot Frontend interface for user interactions
• WebRTC integration for call connections (connected through Ultravox SDK)

Security & Authentication

• Cognito for user authentication
• Bedrock for AI capabilities
• Secrets Manager for sensitive data
• SES for email communications

API Layer

• Multiple API Gateways handling:
  • Admin operations
  • AI Engine interactions
  • Post-session processing
• Lambda functions for serverless processing

Infrastructure

• Public subnet configuration for external access
• ECR (docker) for containerized deployments
• RDS for database operations
• CodePipeline for CI/CD
• Stripe integration for payment processing

 

Production Environment

Deployed on: us-east-1

→ Deployed Admin Dashboard

The production architecture of AngelX maintains the same core components as development but with enhanced security, scalability, and redundancy:

Resource Naming Convention

All AWS resources follow a consistent naming pattern:

• Base name: angel-saas-{service-name}
• Production suffix: -prod

Examples:

• Repository: angel-saas-ai-engine-api
• Lambda function: angel-saas-ai-engine-api-prod
• API Gateway: angel-saas-ai-engine-api-prod
• RDS instance: angel-saas-prod

Frontend Layer

• Production Admin Dashboard with AWS Amplify
• Optimized Bot Frontend with CDN distribution
• Enterprise-grade WebRTC implementation through Ultravox SDK
• Multi-region asset distribution

Security & Authentication

• Enhanced Cognito security policies
• Encrypted Secrets Manager configuration
• SES with dedicated IP and enhanced deliverability
• WAF protection for all public endpoints

API Layer

• Redundant API Gateways across availability zones
• Auto-scaling Lambda configurations
• Enhanced request throttling and quota management
• Cross-zone load balancing (serverless managed by AWS)

Infrastructure

• Multi-AZ deployment across us-east-1
• Private subnet configuration with NAT gateways
• ECR with image scanning and versioning
• RDS with Multi-AZ failover and read replicas (when required.)
• Enhanced monitoring and alerting
• Disaster recovery configuration