What problem does it solve?
Stand up a secure, empty BigQuery data lake in your own GCP project, with layered datasets, least-privilege service accounts, Workload Identity (no downloadable keys), read-only authorized views, audit logging, and a budget alert. You connect your own data sources afterward — on purpose.
Core Features & Use Cases
- Layered datasets: raw, clean, marts, archive, with a one-way data flow to ensure raw data stays isolated.
- Three least-privilege service accounts: lake-ingest, lake-transform, lake-agent, each with scoped permissions to write, transform, and read as designed.
- Workload Identity Federation enabling keyless CI/CD so no secrets are downloaded.
- Authorized views provide read-only access to marts via views that query raw/clean on the agent's behalf.
- Audit logging and a billing budget guardrail to monitor activity and costs.
- Secrets Manager integration planned as part of the hardening standard.
- Terraform-based Path B for reproducible deployment, if desired.
Quick Start
Ask your agent to run the data-lake-starter skill to build the lake in your project.