CUDs Plan
1. Existing - Machine Type Usage [Grouped Instance Family-Wise]
E2 Family
- Standard
- e2-standard-2 (2 vCPUs, 8 GB memory) × 5
- e2-standard-4 (4 vCPUs, 16 GB memory) × 1
- Custom
- e2-custom-4-10240 (4 vCPUs, 10 GB memory) × 2
- Shared-core
- e2-medium (2 vCPUs, 4 GB memory) × 4
- e2-micro (2 vCPUs, 1 GB memory) × 1
C2 Family
- Standard
- c2-standard-4 (4 vCPUs, 16 GB memory) × 8
So in total:
- E2 family → 13 instances
- C2 family → 8 instances
Type | What you Commit | What Services / Resources it Covers | Scope / Restrictions |
|---|---|---|---|
Resource-based CUDs | Amounts of specific resources (vCPUs, memory, Local SSDs, GPUs, etc.), by machine family, region, project. | Compute Engine resources (vCPUs, memory, GPUs, local SSD etc.) for specific machine types; there are different “machine series” with different eligible resources. | Must specify region, project; applies to particular machine families; discount highest when usage is stable & predictable. |
Spend-based CUDs | A minimum hourly spend amount (in dollars) for eligible services. You commit to spending $X per hour (for 1 or 3 years). | Several services: Compute Engine / GKE / Cloud Run (flexible compute spend), plus service-specific spend CUDs for things like AlloyDB, Cloud SQL, Bigtable, Spanner, Memorystore, etc. | Scope is at billing account level (so can apply to all projects under that account). Covers eligible usage for those services. Overages (spend beyond committed) are charged at regular rates. |