AWS Infrastructure Map

An auto-generated map of the Playroll AWS estate, produced directly from the Terraform in playroll-infra — no AWS API calls, no state refresh, no secrets. Overview → Runtime event flow (what triggers what) → Dependency map (what must exist before what) → Automations (the separate Terraform root owning the hub and transcribe GPU).

1· Overview

What the infrastructure map is, how it is generated from Terraform without touching the AWS account, the two different graphs it produces, and why AWS Config, Neptune, and Workload Discovery were rejected.

2· Runtime event flow

What triggers what at runtime — S3 notifications, API Gateway routes, Lambda-to-Lambda invokes, and the handoff to Prefect. Includes the boundaries this diagram deliberately refuses to guess at.

3· Dependency map

The Terraform dependency graph grouped into subsystems — Upload Pipeline, CDN & Certificates, IAM, Compute, Secrets & Encryption, Observability. An arrow means "A must exist before B".

4· Automations (separate root)

The automations department — a separate Terraform root with its own state key and CI lane. The always-on hub wakes and dispatches jobs to the transcribe GPU via ec2:StartInstances and ssm:SendCommand.