Skip to content

architecture.md

Latest commit

 

History

History
25 lines (19 loc) · 1.25 KB

architecture.md

File metadata and controls

25 lines (19 loc) · 1.25 KB
Raw

Infrastructure architecture

sst.config.ts is the provider/app entrypoint. It dynamically imports the stack/deployStack() facade because SST initializes providers before it evaluates the resource graph.

The intended declaration order is stable:

  1. foundation: VPC, database, Redis, storage, cluster, and shared IAM setup
  2. observability: OpenTelemetry into ClickHouse
  3. mail: the verified SES sender the API's invitations go out through
  4. API: the control-plane API and its artifact selection
  5. edge: Proxy, CDN, DNS, and routing
  6. runners: protected EC2 Runner instances, registration, and in-place binary updates

Operational code is grouped separately:

  • deployment/: guarded SST execution, scope, config, and post-deploy verification
  • artifacts/: API and Runner artifact identity, publication, and preflight
  • runner/: inventory, state baselines, registration, and rolling updates
  • bootstrap/: AWS/GitHub/Auth0 provisioning and login
  • shared/: dependency-free utilities shared across domains
  • policies/runner/: mandatory Pulumi Runner safety policy

Factories use ordinary functions and pass typed resource interfaces between layers. They do not introduce Pulumi ComponentResource parents, so existing parent hierarchies and URNs remain stable.