Part 5 — Technical & System Architecture

The reference architecture places browser access, session brokering, Windows execution, policy enforcement and persistence inside explicit AWS trust boundaries.

Request and session flow

  1. The user resolves the service endpoint and connects over HTTPS/WSS.
  2. An edge or load-balancing layer forwards the request to the WebStream gateway.
  3. Identity is validated and policy context is resolved.
  4. The gateway selects or starts an eligible Windows session host.
  5. The target application runs in an isolated user session.
  6. Window updates stream to the browser and user input returns over the secured channel.

Core components

The gateway manages external connections and session routing. Session hosts run the target executable and streamer. Interception components mediate supported Windows interactions. Persistence services hold identity, policy, activity and application data according to the deployed edition and topology.

Single-server evaluation

A Core evaluation can place components on one Windows EC2 instance to reduce setup time. Treat this as a compatibility and workflow environment, not a production resilience pattern. Restrict network access, replace evaluation certificates and avoid sensitive production data.

Scaled deployment

A production design separates ingress/gateway capacity from session hosts, uses private subnets where practical, centralises durable state and adds monitoring, backup and multi-AZ controls. Host selection and scaling should use measured session density rather than generic instance assumptions.

Data dependencies

Keep database latency appropriate for the application. Use S3 or approved managed storage for artefacts where supported, and private connectivity for retained on-premises services. Map every outbound dependency, including licence servers, EDI, SMTP, file shares and third-party APIs.

Authoritative implementation detail

Use the current ACP architecture manual for supported services and deployment details. This playbook explains the decision model and must not override current product documentation.