Deployment Manager
Google Cloud's native IaC service — and why most teams now reach for Terraform.
Deployment Manager is GCP’s native IaC service: you describe resources in YAML (with Jinja/Python templating) and deploy them as a managed deployment. It’s the Google equivalent of AWS CloudFormation or Azure ARM.
In practice, Google now steers teams toward Infrastructure Manager (a managed Terraform service) or plain Terraform, because Terraform is multi-cloud, has a huge module ecosystem, and a better developer experience. Know Deployment Manager exists and what it does, but expect Terraform for new work.
# config.yaml — a Deployment Manager bucket
resources:
- name: my-bucket
type: storage.v1.bucket
properties:
location: EUgcloud deployment-manager deployments create demo --config config.yaml
gcloud deployment-manager deployments describe demo- Identify Deployment Manager’s equivalents in AWS and Azure.
- Write a one-resource Deployment Manager YAML for a bucket.
- List two reasons teams pick Terraform over native IaC tools.
- Explain what a “deployment” represents in Deployment Manager.
Cheat Sheet▾
| Concept | Detail |
|---|---|
| Deployment Manager | GCP native IaC (YAML) |
| Templating | Jinja2 / Python |
| Deployment | Managed unit of resources |
| Infra Manager | Managed Terraform on GCP |
| Equivalent (AWS) | CloudFormation |
| Equivalent (Azure) | ARM / Bicep |
Common Interview Questions▾
What is Deployment Manager?
Google Cloud’s native infrastructure-as-code service, using YAML with Jinja/Python templates to deploy resources as a managed deployment — analogous to CloudFormation or ARM.
Why do many GCP teams use Terraform instead?
Terraform is multi-cloud, has a large module/provider ecosystem and strong tooling, and avoids lock-in — so it’s preferred for portability and developer experience, even on GCP.