AWS Deployment Patterns

WebStream scales from a single instance to a high-availability, multi-AZ deployment. Choose the pattern that fits your stage; you can move up the ladder without re-architecting.

1. Single-server PoC

A single EC2 instance runs all components. Fast to deploy and ideal for evaluation. TLS is terminated on the instance or via a reverse proxy. The trade-off is a single point of failure.

2. Single server with ALB and ACM

Place an Application Load Balancer with an ACM certificate in front of one instance. The load balancer handles HTTPS and WebSocket upgrades reliably, giving a PoC that behaves like production. Recommended for any PoC you intend to show to stakeholders.

3. Scaled app tier with auto scaling

Separate the stateless gateway from the session hosts and let an auto-scaling group add and remove hosts on demand. Use a managed PostgreSQL database (RDS) for multi-instance consistency. This is the first genuinely production-shaped topology.

The gateway stays stateless while session hosts scale out behind it.

4. High availability, multi-AZ

Distribute gateways and session hosts across multiple Availability Zones behind the load balancer, with the database configured for high availability. This pattern targets resilience and larger user populations.

Choosing a pattern

Stage	Pattern
Evaluation / demo	Single-server PoC
Stakeholder PoC	Single server with ALB + ACM
Early production	Scaled app tier with auto scaling
Production at scale	High availability, multi-AZ

Note

Interactive versions of these diagrams are on the documentation hub. Host and gateway counts are governed by your edition — see Licence.