Infrastructure as Code First
infrastructure-as-code-first · always_apply: yes
Content
Every AWS resource this playbook creates — S3 buckets, Lambda functions, Glue database/crawlers, the Athena workgroup, IAM roles/policies, ECS Fargate Streamlit mart, GitHub OIDC deploy role — is defined in the CDK app (four stacks: Deploy, Ingestion, Catalog, Eda), not clicked into existence in the console. Deploy that app exclusively through CI (GitHub Actions or GitLab CI, matching wherever the repo lives) via cdk deploy; a laptop only ever runs cdk bootstrap plus one sandbox mint of the OIDC DeployStack, never a shared environment after that.
Details
- Slug:
infrastructure-as-code-first- Always apply:
- Yes
- Created:
- Aug 31, 2026
- Updated:
- Sep 15, 2026
Playbook
Activities 9
- Stand Up Serverless Ingestion from Scoped Sources Build the Operational Data Lake Pipeline
- Backfill Historical GitHub Events Build the Operational Data Lake Pipeline
- Store Compressed and Partitioned in S3 Build the Operational Data Lake Pipeline
- Catalog with AWS Glue Build the Operational Data Lake Pipeline
- Present the Catalog via Athena Build the Operational Data Lake Pipeline
- Scope Sources, Org, and Environment Model and Deploy Infrastructure as Code
- Model the Data Lake as CDK Stacks Model and Deploy Infrastructure as Code
- Deploy via GitHub Actions Model and Deploy Infrastructure as Code
- Deploy via GitLab CI Model and Deploy Infrastructure as Code