# GCP landing zone

A step of the [Cloud application](https://gradus.kazet.blog/tree/cloud-application) tree on Gradus, in the Build & ship area: Config, lint, releases, IaC.

Page: https://gradus.kazet.blog/tree/cloud-application/step/gcp-landing-zone

Commit to Google Cloud: a project per environment, Artifact Registry, Cloud Run and a remote Terraform state bucket, with Workload Identity Federation so CI deploys without long-lived keys. Pick this or the AWS landing zone, not both.

One option of Cloud provider: Google Cloud. The others: AWS.

Usually comes after: [Infrastructure as code](https://gradus.kazet.blog/tree/cloud-application/step/infrastructure-as-code).

## Prompt for your AI assistant

```
Set up a Google Cloud landing zone for this project in the existing infrastructure code: one project per environment with billing and the required APIs enabled, an Artifact Registry repository for the container image, a Cloud Run service for it, a GCS bucket as the remote Terraform state backend and Workload Identity Federation so the CI workflow deploys with a short-lived token instead of a service account key. Point the first deploy at this service.
```

Every step of the tree: https://gradus.kazet.blog/tree/cloud-application/llms.txt