gcp-cloud-architect

name: gcp-cloud-architectdescription: >  Design, review, and validate Google Cloud (GCP) architectures. Use when choosing GCP  compute, storage, networking, or identity services, or applying the Google Cloud  Architecture Framework (reliability, security, cost, performance).license: MIT + Commons Clausemetadata:   version: 1.1.0  author: borghei  category: engineering  domain: engineering  updated: 2026-06-17  tags: [gcp, google-cloud, cloud-architecture-framework, gke, cloud-run, bigquery, iam, cost-optimization]

GCP Cloud Architect

End-to-end GCP-specific architecture: service selection, Google Cloud Architecture Framework assessment, identity and networking patterns, cost optimization, operational defaults. Provider-specific complement to our generic senior-cloud-architect skill — that one covers cross-cloud patterns; this one knows when to pick Spanner over Cloud SQL, how Workload Identity Federation differs from Service Account keys, and the right Cloud Run vs GKE call.

Core Capabilities

• Compute selection — decision tree across GKE (Autopilot/Standard), Cloud Run, Cloud Functions, Cloud Run Jobs, Batch, Compute Engine, and Vertex AI.
• Data store selection — decision tree across Cloud SQL, Spanner, Firestore, Bigtable, Memorystore, Cloud Storage, and BigQuery.
• Networking — VPC, Private Service Connect, Interconnect/VPN, load-balancer choices, Shared VPC, peering, Cloud Armor, hub-and-spoke.
• Identity — IAM, Service Accounts, Workload Identity (GKE) and Workload Identity Federation, ADC, and least-privilege role/scope binding.
• CAF assessment — score workloads against the five Cloud Architecture Framework pillars.
• Cost optimization — biggest-to-smallest cost levers (right-sizing, CUDs/SUDs, autoscaling, preemptibles, tiering, slots) and cost anti-patterns.
• Workflows — design a new workload, review an existing architecture, and migrate from AWS/Azure to GCP.

When to Use

Clarify First

Before designing or assessing, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

• Task: design from scratch, review an existing architecture, validate IaC, or estimate cost (selects gcp_architecture_validator.py vs gcp_cost_estimator.py vs gcp_caf_scorer.py).
• Workload spec: the YAML workload config, or the Terraform files (the input the scripts parse). Deployment Manager templates are not read; for those, describe the workload in the YAML spec instead.
• Priority pillar: reliability, security, cost, operational excellence, or performance (weights the CAF assessment and which recommendations lead).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

Tools

Scope & Limitations

In Scope:

• GCP service selection through decision trees for compute and data stores, plus networking and identity patterns including Workload Identity Federation
• Cloud Architecture Framework scoring with gcp_caf_scorer.py: five pillars, ten checks each, read from a YAML workload spec
• Anti-pattern checks with gcp_architecture_validator.py on a YAML workload spec or Terraform files: public IPs on managed services, service account keys, single-zone tier-1, basic roles at project level, public buckets, default VPC, missing org policy, Cloud SQL without HA and on-demand BigQuery at high volume
• Rough monthly cost estimates with gcp_cost_estimator.py, with optimization suggestions, plus design, review and migration workflows

Out of Scope:

• Cross-cloud patterns and the AWS and Azure equivalents (see engineering/senior-cloud-architect/, engineering/aws-solution-architect/ and engineering/azure-cloud-architect/)
• Writing or reviewing Terraform modules (see engineering/terraform-patterns/)
• Security posture audits of an exported cloud inventory and IAM (see engineering/cloud-security/)
• Kubernetes operator design for GKE workloads (see engineering/kubernetes-operator/)
• Compliance evidence and control mapping (see ra-qm-team/soc2-compliance-expert/ and ra-qm-team/information-security-manager-iso27001/)

Important Caveats:

• The scripts never call GCP. They read files the user provides, and the CAF score reflects what the YAML spec declares, not what is deployed.
• The validator scans Terraform text with pattern rules and does not evaluate plans, modules or variables. It does not read Deployment Manager templates.
• Cost figures come from a built-in table of approximate US-region list prices from early 2026, with no sustained-use or committed-use discounts. They are for relative comparison, not a quote; check the Google Cloud Pricing Calculator before budgeting.
• Service tiers, SLAs, limits and prices in the references change often and should be confirmed against current Google Cloud documentation.

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

• references/decision-trees.md — the full compute decision tree and the data store decision tree. Read when selecting compute or storage.
• references/networking-and-identity.md — VPC/PSC/Interconnect building blocks, the load-balancer matrix, common networking patterns, and the IAM / Service Account / Workload Identity (Federation) patterns with least-privilege guidance. Read when designing networking or identity.
• references/caf-cost-and-workflows.md — the five CAF pillars, the cost-lever and cost-anti-pattern catalog, all three end-to-end workflows (design/review/migrate), the GCP-specific anti-patterns, and the script tooling-output table. Read when assessing, optimizing, or running a workflow.
• references/gcp-services-reference.md — per-service depth: tiers, SLAs, limits, when to upgrade. Read when sizing a specific service.
• references/gcp-well-architected.md — the 5-pillar CAF assessment with a 10-question checklist per pillar, common findings, and remediation patterns. Read during a CAF review.
• references/gcp-cost-optimization.md — the full cost-lever catalog, anti-patterns, and detection heuristics. Read when driving down spend.

Related skills

• engineering/senior-cloud-architect — generic multi-cloud architecture patterns
• engineering/aws-solution-architect — AWS counterpart
• engineering/azure-cloud-architect — Azure counterpart
• engineering/kubernetes-operator — for GKE operator-pattern workloads
• ra-qm-team/information-security-manager-iso27001 — compliance-mapped controls (GCP has Security Command Center)
• ra-qm-team/soc2-compliance-expert — GCP-specific SOC 2 evidence collection