GCP Cloud Architect

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, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• 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/Deployment Manager files (the input the scripts parse)
• Priority pillar — reliability, security, cost, operational excellence, or performance (weights the CAF assessment and which recommendations lead)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

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