Resource-based committed use discounts

---

Compute Engine provides resource-based committed use discounts (CUDs) for your predictable workloads to help you cut costs on resources that you need. You can purchase and renew resource-based committed use contracts or commitments in return for heavily discounted prices for VM usage.

This document describes information about Compute Engine's resource-based commitments, how to purchase them and the resulting CUDs. To learn about Compute Engine flexible CUDs, see Flexible CUDs.

Resource-based commitments are ideal for predictable and steady state usage. Compute Engine lets you purchase the following categories of resource-based commitments:

• Hardware commitments. You can purchase hardware commitments for resources like vCPUs, memory, GPUs, Local SSDs, and sole tenant nodes. For more information, see Purchase commitments without attached reservations and Purchase commitments with attached reservations.
• Software license commitments. You can purchase license commitments for applicable premium operating system (OS) licenses. For more information, see Purchase commitments for licenses.

Commitments for hardware resources are separate from commitments for licenses. You can purchase both categories of commitments for a VM instance, but you cannot purchase a single commitment that covers both hardware resources and licenses.

When you purchase a committed use contract, you purchase Compute Engine resources—such as vCPUs, memory, GPUs, Local SSDs, and sole-tenant nodes—at a discounted price in return for committing to paying for those resources for 1 year or 3 years. The discount is up to 57% for most resources like machine types or GPUs. The discount is up to 70% for memory-optimized machine types. For committed use prices for different machine types, see VM instances pricing.

Your purchased commitments become active on the following day at 12 AM US and Canadian Pacific Time (UTC-8, or UTC-7 during daylight saving time). You can't cancel a commitment once you've purchased it.

Committed use discount recommendations give you opportunities to optimize your compute costs by analyzing your VM spending trends with and without a committed use discount contract. By comparing these numbers, you can see how much you can save each month with a committed use contract. To learn more about how commitment recommendations work, you can also review Understand commitment recommendations.

You can purchase a committed use contract for a single project, or purchase multiple contracts which you can share across many projects by enabling shared discounts.

Committed use discounts work on most Compute Engine machine types, including predefined and custom machine types. Committed use discounts are simple and flexible, and require no upfront costs. Discounts apply to the aggregate number of vCPUs, memory, GPUs, and Local SSDs within a region, so they are not affected by changes to your instance's machine setup.

For machine types that support per VM Tier_1 networking performance, the 50, 75, and 100 Gbps higher bandwidth SKUs are excluded from discounts.

F1-micro and g1-small shared-core machines are not eligible for committed use discounts.

Note: Purchasing a committed use discount does not affect your VM configurations in any way.

Before you begin

• If you want to use the command-line examples in this guide, do the following:
  1. Install or update to the latest version of the Google Cloud CLI.
  2. Set a default region and zone.
• If you want to use the API examples in this guide, set up API access.

How committed use discounts work

If you have just a few projects, you can purchase commitments just for the specific resources you plan to use.

For example, if you purchase a commitment for 8 cores, and you run 24 cores during the month, you will receive committed use discounts for 8 cores. The other 16 cores will be billed at standard, non-committed use rates. Keep in mind that after you purchase a set amount of commitments, you're billed for those commitments monthly, even if you don't use them. For example, if you purchase commitments for 8 cores, you're billed the committed use rates for those 8 cores for the whole month, even if you might have only run these cores for a part of the month. It is to your advantage to purchase commitments only in increments you know you will use.

Any resources that do not qualify for committed use discounts automatically qualify for sustained use discounts. You can't combine committed use discounts and sustained use discounts for the same resources.

Committed use discounts apply to both vCPUs and memory. You can buy a committed use discount for vCPUs or memory independently of one another.

Commitments can't be stacked for burst scenarios. For example, if you purchased 10 cores for the month and then ran 20 cores for half the month, commitments would not apply for the full 20 cores just because the usage was half the month.

Resources that are not covered by committed use discounts automatically qualify for sustained use discounts on a machine type family basis.

For example:

You run an n2-standard-2 for a portion of the month and run an n2-standard-8 for another portion of the same month, Compute Engine combines the two and applies sustained use discounts for the portion not covered by committed use discounts because both machine types belong to the n2-standard family.

By default, committed use discounts apply at the project level. After you purchase your commitment for a project, you receive the applicable committed use discounts only for that project. If you move the project for which you purchased your commitments to a different Cloud Billing account, then you continue to receive the applicable committed use discounts for that project under the new Cloud Billing account.

You can also enable discount sharing from your Cloud Billing account to share discounts across multiple projects.

Share committed use discounts across projects

Sharing your committed use discounts across all your projects reduces the overhead of managing discounts on a per-project basis, and maximizes your savings by pooling all your discounts across your projects' resource usage.

If you have multiple projects that share the same Cloud Billing account, you can enable committed use discount sharing so all of your projects within that Cloud Billing account share all of your committed use discount contracts. Your sustained use discounts are also pooled at the same time. That is, sustained use discounts are calculated using the total resources across these projects, rather than just the resources within a single project.

For example, you purchase two commitments for 80 cores each (a total of 160 cores) and you run 200 cores during the month across different projects in your Cloud Billing account. If you've enabled committed use discount sharing for your Cloud Billing account, then you receive the applicable committed use discounts for 160 of those 200 cores that are used across the projects in that Cloud Billing account. The additional 40 cores are billed at on-demand, non-committed use rates. After you purchase your commitments, you're billed for your committed resources monthly, throughout the commitment time period, even if you don't use the resources. See Understand discount sharing for cost-saving utilization recommendations.

Note: Committed use discounts do not differentiate between custom machine types and predefined machine types. The discount will be spread proportionally across all projects under the same Cloud Billing account. See Attribution when using custom machine type SKUs for additional information.

Committed use discounts are subject to Google Cloud commitment-based pricing and billing. By purchasing a committed use discount, you agree to these terms.

Use attribution to allocate discounts

Attribution refers to how your committed use discounts are allocated across your projects. These allocations are reflected in Cloud Billing cost management interfaces, such as the usage cost export or the Google Cloud console.

Attribution applies only when discount sharing is enabled. You can choose the type of attribution you want to use before you turn on discount sharing, and then activate the attribution configuration when you enable discount sharing.

Compute Engine commitments use proportional attribution by default. Proportional attribution commitments are applied to the projects according to the amount of the total eligible usage consumed by each project. For example, if project A consumed $75 worth of usage and project B consumed $25, project A would be covered by up to 75% of available credit and project B would be covered by up to 25%.

Alternatively, you can choose prioritized attribution for your Compute Engine commitments based on the usage you specify. Any remaining unprioritized commitments are applied proportionally to the eligible usage in your remaining projects. The total amount of the allotments cannot exceed the commitment amount purchased.

To choose proportional or prioritized attribution for your Compute Engine commitments, see choose attribution for resource-based commitments.

Specifications

• You can only purchase resource-based commitments for resources in a specific region if you have quota available in that region for both of the following:

  • Commitments
  • Committed resources (with the exception of memory)

  For more information, see Quotas for commitments and committed resources.

• Commitments must be purchased on a per-region basis.

• To use the gcloud CLI to manage commitments, you must be running gcloud version 147.0.0 or later. To update the gcloud CLI to the latest version:

  gcloud components update
  

  To check the version of the gcloud CLI you are running:

  gcloud version
  

Restrictions

• Projects that are in the free tier period with free tier credit and projects that do not have any payment history do not qualify for committed use discounts.
• You can purchase commitments only on a per-region basis.

• You can't change the project for which you purchase a commitment. If you want to share the discount with multiple projects, enable discount sharing.

  Note: If you move the project for which you purchased your commitments to a different Cloud Billing account, then you continue to receive the applicable committed use discounts for that project under the new Cloud Billing account. Learn about changing the Cloud Billing account for projects.

• For commitments shared across projects under one Cloud Billing account: If any part of the commitment is unutilized, the remaining commitment charge remains in the project that purchased that portion of the commitment.

• Committed use discounts do not apply to preemptible VM instances, N1 shared-core machine types, or extended memory.

• For committed use discounted pricing for GPUs and Local SSDs, you must create and attach a reservation when purchasing the commitment.

• Committed use discount prices are independent of on-demand pricing. Any fluctuation in on-demand pricing would not necessarily be reflected in committed use discounts.

• If a reservation is attached to a committed use discount, the reservation can't be deleted for the duration of the commitment.

• You can only buy a 1-year commitment on K80 GPUs.

Pricing

You're billed monthly for your commitment and must pay your monthly commitment fee even if you don't use all of your committed resources. Your commitment fee is the sum of the discounted prices of all your committed resources. Compute Engine calculates the discounted price of each resource by using its prevailing on-demand price on the day your commitment becomes active. Your monthly commitment fee and the discounted prices for your resources stay the same until the end of your commitment term, even if the on-demand prices change.

Note: If you merge or split your commitments, then the discounted prices for your committed resources might change on the day your merged or split commitments become active.

The discounted pricing (also referred to as CUD pricing) for VM instances, with or without GPUs and/or Local SSDs, differs depending on the region. For current rates, see VM instance pricing.

Commitment types

You can purchase commitments for the following resources.

Commitment types	Resources for which you can purchase discounts	Applicable to the following resource types
General purpose E2 commitments	vCPUs Memory	All E2 machine types
General purpose N2 commitments	vCPUs Memory Local SSD	All N2 machine types All N2 sole-tenant node types
General purpose N2D commitments	vCPUs Memory Local SSD	All N2D machine types All N2D sole-tenant node types
General purpose C3 commitments	vCPUs Memory Local SSD	All C3 machine types All C3 sole-tenant node types
General purpose Tau T2D commitments	vCPUs Memory	Standard Tau T2D machine types
General purpose N1 commitments	vCPUs Memory GPUs Local SSD	All N1 machine types, excluding shared-core. All N1 sole-tenant node types GPUs: NVIDIA T4 NVIDIA V100 NVIDIA P100 NVIDIA P4 NVIDIA K80
Compute-optimized C2 commitments	vCPUs Memory Local SSD	All C2 machine types All C2 sole-tenant node types
Compute-optimized C2D commitments	vCPUs Memory Local SSD	All C2D machine types
Memory-optimized M1/M2 commitments	vCPUs Memory Local SSD	All M1 and M2 machine types All M1 and M2 sole-tenant node types
Memory-optimized M3 commitments	vCPUs Memory Local SSD	All M3 machine types
Accelerator-optimized A2 commitments	vCPUs Memory GPUs Local SSD	All A2 machine types GPUs: NVIDIA A100
Accelerator-optimized G2 commitments	vCPUs Memory GPUs Local SSD	All G2 machine types All G2 sole-tenant node types GPUs: NVIDIA L4

You can't purchase commitments for f1-micro, or g1-small machine types or for the sole-tenant premium charge.

Commitments for machine types

Purchase the appropriate commitment type for the machine types you are using. Discounts for general-purpose commitments are applied to resources in the following order:

1. E2, N2, N2D, or N1 custom machine types, depending on which commitment you purchase
2. Sole-tenant nodes
3. Either the E2, N2, N2D, Tau T2D, or N1 predefined machine types, depending on which commitment you purchase

When you purchase general-purpose commitments, you pick which generation the commitment applies to. For example, if you purchase general-purpose E2 commitments, they only apply to E2 machine types. Similarly, if you purchase general-purpose N2, N2D, Tau T2D, or N1 commitments, the commitments never overlap.

For example, assume you have a region with the following mix:

• 10 N2 custom machine type vCPUs
• 30 GB of custom machine type memory
• 2 n2-standard-4 predefined machine types

You purchase N2 commitments for 15 vCPUs and 13.5 GB of memory for committed use. The committed use discounts would be applied first to the N2 custom machine types, and any remaining discounts would be applied to the N2 predefined machine types. In this case, all 10 vCPUs of the N2 custom machine types would be charged at committed use prices, and 13.5 GB of custom machine type memory would be charged at committed use prices.

Finally, the remaining 5 vCPUs of committed use would apply to 5 random vCPUs across the two n2-standard-4 machine types. Any resources that aren't covered by committed use discounts would qualify for sustained use discounts.

Note: Commitments are aggregated by machine family. If you are unsure of how many commitments to purchase, you might want to purchase a smaller number of commitments, then add more as you need them. For example, you can purchase multiple contracts for 10 vCPUs and zero memory, then purchase separate contracts for additional memory.

To purchase a commitment for general-purpose machine types, see Purchase commitments without attached reservations.

Memory-optimized commitments

Memory-optimized committed use discounts are available at two levels. One level applies to both M1 and M2 machine types. The other level applies to only M3 machine types. You cannot use the same committed use discount for all memory-optimized machine types. Quota for these committed use discounts is separate. If you want to use a committed use discount for an M1 machine type, you must have quota for an M1 machine. The same is true for M2 and M3–you must have quota for the committed use discount.

If you intend to use memory-optimized machine types, purchase memory-optimized commitments. To purchase a commitment for memory-optimized machine types, see Purchase commitments without attached reservations.

Compute-optimized commitments

If you intend to use compute-optimized machine types, purchase compute-optimized commitments. To purchase a commitment for compute-optimized machine types, see Purchase commitments without attached reservations.

Accelerator-optimized commitments

If you intend to use accelerator-optimized machine types, purchase a commitment for A2 or G2 machine types. To purchase a commitment for A2 or G2 machine types see Purchase commitments with attached reservations.

Commitments for GPUs and Local SSD

To purchase commitments for GPUs or Local SSDs, you must also reserve the resources when purchasing the commitment. Reserving these resources is required to ensure that the resources are always available for you (whether you use them or not). There are no additional charges for reserving the resources.

You must purchase commitments by specific GPU types. For example, you can purchase GPUs for either NVIDIA P100s or NVIDIA V100s, but you can't purchase commitments for NVIDIA P100 GPUs and apply them to other GPU types.

To purchase a commitment for GPUs and Local SSDs, see Purchase commitments with attached reservations in this document.

To learn more about commitments with attached reservations, see Attach reservations to commitments.

Quotas for commitments and committed resources

You can only purchase resource-based commitments for resources in a specific region if you have quota available in that region for both of the following:

• Commitments
• Committed resources (with the exception of memory)

Specifically, if you want to purchase commitments for any vCPUs, GPUs, or Local SSDs, then you need to have quota available both for commitments and for those specific committed SKUs in the region where you want to purchase the commitment. There is no quota on memory, so you don't need to have separate quota for committed memory to purchase a commitments for memory.

For example, to purchase 5 commitments that cover 32 vCPUs of general-purpose N1 machine type, 16 GB memory, 4 NVIDIA P4 GPUs, and 2 Local SSDs in us-central1 region, you must have quota for each of the following:

• 5 commitments in us-central1
• 32 committed N1 vCPUs in us-central1
• 4 committed NVIDIA P4 GPUs in us-central1
• 750 GB (or 2 Local SSDs) of committed Local SSD disk space in us-central1

Note: If your project is still in the free tier period with free tier credit remaining, or if your project does not have payment history, it does not qualify for committed use discounts. This means that the project is not granted quota to create commitments.

Quota limits

By default, Compute Engine offers a specific amount of commitment quota for each type of committed resource. These quota limits determine the number of commitments you can purchase and the amount of resources you can commit to. To learn how to view the current quota limits and quota usage values for your commitments and committed resources, see View quotas in the Google Cloud console.

If you consistently pay for a very high amount of committed vCPUs for your projects across different regions, then you might be eligible for unlimited quota on your committed vCPUs for all machine types (except for memory-optimized machine types) in all regions.

If you use up all your commitment quota, you won't be able to purchase new commitments. Likewise, if you exhaust your committed resource quota, then you won't be able to purchase a new commitment for that resource even if you have commitment quota available. For example, if you used up all of your commitment quota, then the server returns the following error when you make a commitment purchase request:

"Quota 'COMMITMENTS' exceeded. Limit: 0.0"

Increase quota limits

If you do not have enough quota for your commitments or your committed resources, you can always request for a quota increase from the Quotas page. You can request for quota increases at any time. To learn how to submit a request to increase quota limits for your resources, see Request a higher quota limit.

For example, consider a scenario where you currently meet your quota limits and have 2 commitments for a total of 4 NVIDIA V100 GPUs in us-central1 region. Suppose you want to purchase 2 new commitments for 2 NVIDIA V100 GPUs each, in the same region, you must do the following:

1. Submit a new quota request to increase your Committed NVIDIA V100 GPUs quota in us-central1 to the new maximum number (8) that you want.

2. Submit a new quota request to increase your Commitments quota in us-central1 to match the new maximum number (4) that you want.

   Wait for your requests to be approved and closed. After your requests are approved, your commitment and committed GPU quotas in us-central1 increase to match your new needs. You can then purchase your new commitments.

If you place a request for an increase in quota limit for a resource that already has unlimited quota by default, then the quota value for that resource remains unlimited and you are notified that your requested limit is below the approved limit.

Set a cap for quota limits

You can set a cap on the quota value for your committed resources by creating a consumer quota override. For resources that have unlimited quota by default, creating a consumer quota override decreases the quota value. To return the default quota to its unlimited value, you must remove the consumer override that was set for your committed SKUs. For more information, see Creating a consumer quota override and Deleting a consumer quota override.

To learn more about how to manage quotas for your resources, see View and manage quotas.

Purchase commitments without attached reservations

You can purchase commitments for vCPUs and/or memory without attaching any reservations for those resources. You can purchase these commitments using the Google Cloud console, the gcloud CLI, or the API.

To learn more about commitments with attached reservations, see Attach reservations to commitments

To purchase commitments for GPUs or Local SSDs, see Purchase commitments with attached reservations.

By default, project owners have permission to purchase committed use discount contracts. However, it's possible for owners to create custom roles that include or exclude certain users. Read about access control to ensure you have permission to purchase a committed use discount contract.

After purchasing a commitment, the commitment is effective starting at midnight the following day. For example, a commitment purchased on Monday afternoon at 3 PM US and Canadian Pacific Time (UTC-8, or UTC-7 during daylight saving time) becomes effective on Tuesday at 12 AM US and Canadian Pacific Time (UTC-8 or UTC-7). The discounts are automatically applied to applicable instances in the region you specified, and to the projects in which those discounts are purchased.

Important: After you purchase a commitment, you can't cancel it. If you change the Cloud Billing account for the project associated with the commitment, the scope of your attribution and discount sharing settings changes to projects in the new Cloud Billing account. If you had discount sharing enabled in the old Cloud Billing account, the projects in the old Cloud Billing account are no longer in the scope of the discount sharing settings.

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.commitments.create to create a commitment for a VM.
• compute.commitments.list to view a list of commitments on a project.

Console

Before you purchase a commitment using the Google Cloud console, select the project that you want to use to purchase the commitment. If discount sharing is enabled for a Cloud Billing account, you can purchase the commitment using any project from that Cloud Billing account. After you select the project, perform the following steps:

1. In the Google Cloud console, go to the Committed use discounts page.

   Go to Committed use discounts

2. To purchase a new commitment, click Purchase commitment.

3. Name your commitment.

4. Choose the region where you want it to apply.

5. Choose the Commitment type:

   • General-Purpose E2 for E2 machine type resources
   • General-Purpose N2 for N2 machine type resources
   • General-Purpose N2D for N2D machine type resources
   • General-Purpose C3 for C3 machine type resources
   • General-Purpose T2D for Tau T2D machine type resources
   • General-Purpose N1 for N1 machine type resources
   • Compute-optimized C2 for C2 machine type resources
   • Compute-optimized C2D for C2D machine type resources
   • Memory-optimized M1/M2 for M1 and M2 machine type resources
   • Memory-optimized M3 for M3 machine type resources
   • Accelerator-optimized A2 for A2 machine type resources
   • Graphics-optimized G2 for G2 machine type resources

6. Choose a commitment Duration of 1 or 3 years.

7. Enter the quantity of Cores or Memory that you want to purchase. There is no lower limit, the number can be zero. The quantity for cores must be entered as a whole number equal to or greater than zero. Memory can be purchased in increments of 0.25 GB.

8. Read the terms of purchase.

9. Click the Purchase button to purchase the commitment.

gcloud

Using the gcloud CLI, run the gcloud compute commitments create command:

gcloud compute commitments create COMMITMENT_NAME \
    --region REGION \
    --project PROJECT_ID \
    --resources vcpu=NUMBER_VCPUS,memory=MEMORY \
    --plan DURATION \
    --type COMMITMENT_TYPE

Replace the following:

• COMMITMENT_NAME: the name you want to identify this commitment with.
• REGION: the region this commitment applies to. Each region has different commitment prices. For current prices, see the price sheet.
• PROJECT_ID: the project ID of the project for which you want to create the commitment.
• NUMBER_VCPUS: the number of vCPUs you are willing to purchase commitments for. The number of vCPUs must be an integer of 0 or more and can be even or odd.
• MEMORY: the amount, in MB or GB, of memory you are willing to purchase commitments for. For example, 1000MB. If the units are not specified, the default unit used is GB. Memory can be purchased in increments of 0.25 GB.
• DURATION: the term of the commitment, either 12-month or 36-month.

• COMMITMENT_TYPE: one of:

  • general-purpose-e2 for E2 machine type resources
  • general-purpose-n2 for N2 machine type resources
  • general-purpose-n2d for N2D machine type resources
  • general-purpose-c3 for C3 machine type resources
  • general-purpose-t2d for Tau T2D machine type resources
  • general-purpose for N1 machine type resources
  • compute-optimized for C2 machine type resources
  • compute-optimized-c2d for C2D machine type resources
  • memory-optimized for M1 or M2 machine type resources
  • memory-optimized-m3 for M3 machine type resources
  • accelerator-optimized for A2 machine type resources

  • graphics-optimized for G2 machine type resources

    If you do not specify the --type flag, the default value used is general-purpose.

Examples

• To create a general-purpose commitment for N1 machine types, you might use the following example:

  gcloud compute commitments create example-commitment --region us-central1 \
    --resources vcpu=5,memory=33280MB --plan 12-month \
    --project=myproject
  

• To create a compute-optimized commitment, use the gcloud compute commitments create command, which purchases a 1 year commitment for a compute-optimized machine type:

  gcloud compute commitments create example-compute-optimized-commitment \
    --region us-central1 --resources vcpu=2,memory=3814GB --plan 12-month \
    --type compute-optimized --project=myproject
  

• To create a memory-optimized commitment:

  gcloud compute commitments create example-memory-optimized-commitment \
    --region us-central1 --resources vcpu=96,memory=1434MB \
    --plan 12-month --type memory-optimized \
    --project=myproject
  

• To create an accelerator-optimized commitment, you must purchase your commitment with a supporting attached reservation by using the gcloud compute commitments create command. You must also specify the total number of resources (including GPUs) that you need.

  When creating GPU commitments, you need to specify the --accelerator and --resources-accelerator flags. The --accelerator flag specifies the number of GPUs that are attached to each VM. The --resources-accelerator flag specifies the total number of GPUs in the commitment.

  For example, the following commitment includes 96 vCPUs, 680 GB memory, 8 GPUs, and a reservation for those GPUs to be used in 2 VMs in us-central1-a.

  gcloud compute commitments create example-accelerator-optimized-commitment \
    --region=us-central1 \
    --project=myproject \
    --resources=vcpu=96,memory=680GB \
    --resources-accelerator=count=8,type=nvidia-tesla-a100 \
    --plan 12-month \
    --type accelerator-optimized \
  
    --reservation=reservation-01 \
    --reservation-zone=us-central1-a \
    --machine-type=a2-highgpu-4g \
    --accelerator=count=4,type=nvidia-tesla-a100 \
    --vm-count=2
  
  

• To create a GPU or Local SSD commitment, you must purchase your commitment with a supporting attached reservation by using the gcloud compute commitments create command.

  When creating GPU commitments, you need to specify the --accelerator and --resources-accelerator flags. The --accelerator flag specifies the number of GPUs that are attached to each VM. The --resources-accelerator flag specifies the total number of GPUs in the commitment.

  For example, the following commitment includes 4 GPUs and a reservation for those GPUs to be used in 2 instances in us-central1-a.

  gcloud compute commitments create example-reservation-commitment \
    --region=us-central1 \
    --project=myproject \
    --resources=vcpu=96,memory=624GB \
    --resources-accelerator=type=nvidia-tesla-v100,count=4 \
    --plan 12-month \
    
    --reservation=reservation-01 \
    --reservation-zone=us-central1-a \
    --machine-type=n1-standard-32
    --accelerator=type=nvidia-tesla-v100,count=2 \
    --vm-count=2
    
  

API

In the API, make a POST request to the regionCommitments.insert method, with a request body that contains information about the commitment:

https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments?requestId=OPTIONAL_UNIQUE_ID

Note: requestId is an optional query parameter, but we recommend providing it to help prevent unintended duplicate requests.

The resource body should contain the following:

• name for the name of the commitment
• plan for the term of the commitment, either TWELVE_MONTH or THIRTY_SIX_MONTH
• resources to specify the amount of memory and vCPU. Memory must be be specified in MB. You must specify both VCPU and MEMORY in the resources section.

• type of commitment, one of the following:

  • GENERAL_PURPOSE_N2 for N2 machine type resources
  • GENERAL_PURPOSE_E2 for E2 machine type resources
  • GENERAL_PURPOSE_N2D for N2D machine type resources
  • GENERAL_PURPOSE_C3 for C3 machine type resources
  • GENERAL_PURPOSE_T2D for Tau T2D machine type resources
  • GENERAL_PURPOSE for N1 machine type resources
  • COMPUTE_OPTIMIZED for C2 machine type resources
  • COMPUTE_OPTIMIZED_C2D for C2D machine type resources
  • MEMORY_OPTIMIZED for M1 or M2 machine type resources
  • MEMORY_OPTIMIZED_M3 for M3 machine type resources
  • ACCELERATOR_OPTIMIZED for A2 machine type resources
  • GRAPHICS_OPTIMIZED for G2 machine type resources

For example, the following creates a commitment for 1 year with 5 vCPUs and 18.75 GB of memory:

{
  "name": "example-commitment",
  "plan": "TWELVE_MONTH",
  "type": "GENERAL_PURPOSE",
  "resources": [
    {
    "amount": "5",
    "type": "VCPU"
    },
    {
    "amount": "19200",
    "type": "MEMORY"
    }
  ]
}

To create a memory-optimized commitment, include the type property. The following example shows a purchase of a 1 year commitment for an m1-megamem-96 machine type:

{
  "name": "example-memory-optimized-commitment",
  "plan": "TWELVE_MONTH",
  "type": "MEMORY_OPTIMIZED",
  "resources": [
    {
    "amount": "96",
    "type": "VCPU"
    },
    {
    "amount": "1434",
    "type": "MEMORY"
    }
  ]
}

To create a compute-optimized commitment, include the type property. The following example, purchases a 1 year commitment for a c2-standard-16 machine type:

{
  "name": "example-compute-optimized-commitment",
  "plan": "TWELVE_MONTH",
  "type": "COMPUTE_OPTIMIZED",
  "resources": [
    {
    "amount": "16",
    "type": "VCPU"
    },
    {
    "amount": "1434",
    "type": "MEMORY"
    }
  ]
}

Purchase commitments with attached reservations

When you purchase a commitment with attached reservations, make sure that your commitment and reservations meet the following criteria:

• The commitment and its attached reservations must be in the same region.
• The reservation must be for the same machine series as the commitment.
• If your commitment has GPUs, then the GPU type in the reservation and the commitment must match.
• For GPUs and local SSDs, the number of reserved resources of each resource type must exactly match with the number of committed resources for that resource type. For example, if you want to purchase a commitment for 4 V100 GPUs, then your commitment's attached reservations must have a total of 4 V100 GPUs. However, the amount of vCPU and memory that you reserve can be more or less than what you commit to.
• For GPUs, purchase commitments for the specific GPU types that you intend to use. For example, you can purchase commitments for either NVIDIA P100s or NVIDIA V100s, but you cannot use a commitment that was purchased for NVIDIA P100 GPUs to cover NVIDIA V100 GPUs.
• If a reservation attached to a commitment is consumed by a project that is not included in the commitment, then you don't get the discounted price. If your attached reservations are shared reservations, share those reservations only with projects that are included in the commitment to ensure you receive the committed use discounts.

You can purchase a commitment with an attached reservation using the Google Cloud console, the gcloud CLI, or the API.

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.commitments.create to create a commitment for a VM.
• compute.commitments.list to view a list of commitments on a project.
• compute.commitments.updateReservations to create a reservation for GPUs or SSDs.

Console

Before you purchase a commitment using the Google Cloud console, select the project that you want to use to purchase the commitment. If discount sharing is enabled for a billing account, you can purchase the commitment using any project from that billing account. After you select the project, perform the following steps:

1. In the Google Cloud console, go to the Committed use discounts page.

   Go to Committed use discounts

2. To purchase a new commitment, click Purchase commitment.

3. Name your commitment, and choose the Region where you want it to apply.

4. Choose the Commitment type. The following commitment types provide GPU and/or local SSD options:

   • General-Purpose N2 for N2 machine type resources
   • General-Purpose N2D for N2D machine type resources
   • General-Purpose N1 for N1 machine type resources
   • Compute-optimized C2 for C2 machine type resources
   • Compute-optimized C2D for C2D machine type resources
   • Memory-optimized M1/M2 for M1 and M2 machine type resources
   • Memory-optimized M3 for M3 machine type resources
   • Accelerator-optimized A2 for A2 machine type resources
   • Graphics-optimized G2 for G2 machine type resources

5. Choose a commitment Duration of 1 or 3 years.

6. Enter the quantity of Cores and Memory that you want to purchase. If you only want to commit to and reserve GPUs or local SSDs without committing to vCPUs and memory, specify 0 for the vCPUs and memory commitment quantities.

7. Click Add GPUs and select the GPU type and Number of GPUs that you want to commit to.

8. Click Add local SSD and specify the number of disks that you want to commit to.

9. To create a reservation and attach it to the commitment, click Add a Reservation.

   1. In the Name field, enter a name for your reservation.
   2. Choose the Region and Zone where you want to reserve resources.
   3. Choose your preferred Share type:
      • To create a reservation for a single project, select Local.
      • To create a shared reservation among multiple projects, select Shared. To share this reservation with other projects, click Add projects and select the desired projects from the current project's organization.

   4. In the Use with VM instance field, select one of the following options:

      • To use this reservation's resources only when creating matching VMs that specifically target this reservation by name, select Select specific reservation.
      • To allow matching VM instances to automatically use this reservation, select Use reservation automatically.

   5. In the Number of VM instances field, enter the number of VM instances that you want to reserve.

   6. Specify the resources that you want to reserve for each VM instance:

      • If you want to reserve VMs that match an existing instance template, select Use instance template and select an instance template from the list.
      • Otherwise, select Specify machine type and specify the following:
        1. In the Machine family, Series, and Machine type fields, select a machine family, series, and machine type.
        2. Optional: Specify a minimum CPU platform and/or GPUs:
           1. Click CPU Platform and GPU to expand the section.
           2. Optional: To specify a minimum CPU platform, in the CPU Plaform list, select an option.
           3. Optional: To add GPUs, click Add GPU. Then, in the GPU type and Number of GPUs fields, select the type and number of GPUs for each VM.
        3. Optional: Add local SSDs:
           1. In the Number of disks field, select the number of local SSDs for each VM.
           2. In the Interface type field, select the interface for the local SSDs.

   7. To finish specifying the properties for this reservation, click Done.

   Note: The amount of GPUs and local SSDs that you reserve must be equal to the amount that you commit to.

10. Click the Purchase button to purchase the commitment.

11. Read the terms of purchase and click Purchase when you are ready to purchase the commitment.

gcloud

Use the gcloud compute commmitments create command to purchase a commitment, and include flags to create an attached reservation.

For example, the following commitment includes 4 GPUs and a new reservation for those 4 GPUs to be used across 2 n1-standard-32 instances in us-central1-a.

gcloud compute commitments create commitment-01 \
    --region=us-central1 \
    --project=myproject \
    --resources=vcpu=96,memory=624GB \
    --resources-accelerator=type=nvidia-tesla-v100,count=4 \
    --plan 12-month \
    --reservation=reservation-01 \
    --reservation-zone=us-central1-a \
    --machine-type=n1-standard-32 \
    --accelerator=type=nvidia-tesla-v100,count=2 \
    --vm-count=2

If you want to commit to and reserve GPUs or local SSDs without committing to vCPUs and memory, specify 0 for the vCPU and memory commitment quantities.

gcloud compute commitments create commitment-01 \
    --region=us-west2 \
    --project=myproject \
    --resources=vcpu=0,memory=0 \
    --resources-accelerator=type=nvidia-tesla-p4,count=1 \
    --plan 12-month \
    --reservation=reservation-01 \
    --reservation-zone=us-west2-b \
    --machine-type=n1-standard-2 \
    --accelerator=type=nvidia-tesla-p4,count=1 \
    --vm-count=1

To create multiple reservations when purchasing a commitment, use a YAML file that contains the reservation properties. For example:

gcloud compute commitments create commitment-01 \
    --region=us-central1 \
    --project=myproject \
    --resources=vcpu=96,memory=624,local-ssd=750 \
    --resources-accelerator=type=nvidia-tesla-v100,count=1 \
    --plan 12-month \
    --reservations-from-file=YAML_FILE

For example, the following YAML file contains 2 reservations. The first reservation, res-01, contains 1 n1-standard-2 instance with 1 GPU, and it is a targeted reservation, which means that you must specifically target that reservation by name to use its reserved instances. The second reservation, res-02, contains 1 n1-standard-2 VM instance with 2 types of attached local SSDs.

- reservation: res-01
  reservation_zone: us-central1-a
  require_specific_reservation: true
  vm_count: 1
  machine_type: n1-standard-2
  accelerator:
  - count: 1
    type: nvidia-tesla-v100
- reservation: res-02
  reservation_zone: us-central1-a
  vm_count: 1
  machine_type: n1-standard-2
  local_ssd:
  - interface: scsi
    size: 375
  - interface: nvme
    size: 375

API

Use the regionCommitments.insert method and include the reservations field to define the reservation's properties. For example, the following commitment includes 4 GPUs and a reservation for those 4 GPUs to be used across 2 instances in us-central1-a.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments

{
  "name": "commitment-01",
  "plan": "TWELVE_MONTH",
  "resources":
  [
    {
      "amount": "96",
      "type": "VCPU"
    },
    {
      "amount": "638976",
      "type": "MEMORY"
    },
    {
      "acceleratorType": "nvidia-tesla-v100",
      "amount": "4",
      "type": "ACCELERATOR"
    }
  ],
  "reservations":
  [
    {
      "name": "reservation-01",
      "specificReservation":
      {
        "count": "2",
        "instanceProperties":
        {
          "guestAccelerators":
          [
            {
              "acceleratorCount": 2,
              "acceleratorType": "nvidia-tesla-v100"
            }
          ],
          "machineType": "n1-standard-8"
        }
      },
      "specificReservationRequired": false,
      "zone": "us-central1-a"
    }
  ]
}

If you only want to commit to and reserve GPUs or local SSDs without committing to vCPUs and memory, specify 0 for the vCPU and memory commitment quantities. For example:

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments

{
  "name": "commitment-01",
  "plan": "TWELVE_MONTH",
  "resources":
  [
    {
      "amount": "0",
      "type": "VCPU"
    },
    {
      "amount": "0",
      "type": "MEMORY"
    },
    {
      "acceleratorType": "nvidia-tesla-v100",
      "amount": "4",
      "type": "ACCELERATOR"
    }
  ],
  "reservations":
  [
    {
      "name": "reservation-01",
      "specificReservation":
      {
        "count": "2",
        "instanceProperties":
        {
          "guestAccelerators":
          [
            {
              "acceleratorCount": 2,
              "acceleratorType": "nvidia-tesla-v100"
            }
          ],
          "machineType": "n1-standard-8"
        }
      },
      "specificReservationRequired": false,
      "zone": "us-central1-a"
    }
  ]
}

The commitment with the attached reservations is successfully created only if there are enough resources of the specified machine type in the target zone, and sufficient quota, at the time of the request.

When you create a commitment with an attached reservation, you cannot delete the reservation for the duration of the commitment. When your commitment expires, Compute Engine automatically deletes any attached reservations. The deletion of reservations has no effect on any running instances that were tied to those reservations. The running instances continue to run and you are still charged for those instances.

If you need to modify the properties of your committed reservations, see Replace reservations that are attached to commitments.

Purchase commitments for licenses

You can purchase commitments for your licenses if you run your workloads on VMs that use the following operating system (OS) images:

• SUSE Linux Enterprise Server (SLES) images
• SLES for SAP images
• Red Hat Enterprise Linux (RHEL) images
• RHEL for SAP images

The following table shows the CUDs that you receive for your software license commitments depending on the OS image and the number of vCPUs that your VM uses:

OS Image	Number of vCPUs	1-year CUD percentage	3-year CUD percentage
SLES	1-2	77%	79%
SLES	3-4	54%	59%
SLES	5+	45%	50%
SLES for SAP	any	59%	63%
RHEL	any	20%	24%
RHEL for SAP	any	20%	24%

When you purchase a commitment for licenses, the commitment forms a "pool" of licenses that automatically apply to any running VM instances within a selected project in a specified region. The licenses in the commitment are not tied to any one particular VM. When a VM starts, it takes a committed license from the pool, and when the VM stops it returns the license to the pool, where the license can be used by another VM. As long as there are available committed licenses in the pool, you continue to receive discounts for the premium OS usage.

For example, if you need to run 10 VMs in two regions (5 VMs in us-central1 and 5 VMs in us-west1) and under the same project ID, you must purchase 5 licenses in each region to cover those running VMs. For each commitment, your committed licenses can apply to any 5 concurrently running VMs at any time during the year in the respective region. You are billed monthly for the commitments regardless of your usage.

You can't cancel a license commitment after you purchase it. When your license commitments expire, your running VMs continue to run and you are charged for the licenses at on-demand image prices.

Important: Always verify that committed use discount contracts or commitments for your licenses are in the correct project ID and regions to avoid being double charged. You must purchase your license commitment in the same project and region as the machine using the license. For example, if you purchase your license commitment in Project A, but the running VMs that require the OS images are in Project B, you are charged for the license commitment in Project A and the on-demand image price for the VMs running in Project B.

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.commitments.create to create a license for committed use discounts.

Purchase a license commitment using the Google Cloud console, the Google Cloud CLI, or the Compute Engine API.

Console

Before you purchase a commitment using the Google Cloud console, select the project that you want to use to purchase the commitment. If discount sharing is enabled for a billing account, you can purchase the commitment using any project from that billing account. After you select the project, perform the following steps:

1. In the Google Cloud console, go to the Committed Use Discounts page.

   Go to the Committed Use Discounts page

2. Click Purchase commitment to purchase a new commitment.
3. Click New license committed use discount to purchase a new license commitment.
4. Name your commitment and choose the region where you want it to apply.
5. Choose a duration amount of the commitment, either 1 or 3 years.
6. Choose a License family.
7. Choose the License type and quantity.
8. Choose the Number of licenses.
9. Click Purchase.

gcloud

Using the gcloud CLI, run the gcloud compute commitments create-license command to purchase a license commitment.

gcloud compute commitments create-license COMMITMENT_NAME \
    --license `LICENSE_URI`
    --amount NUMBER_OF_LICENSES \
    --cores-per-license CORES_PER_LICENSE \
    --plan PLAN \
    --region REGION \

Replace the following:

• COMMITMENT_NAME: the name for your commitment.
• LICENSE_URI: the license URI. For example: https://www.googleapis.com/compute/v1/projects/myproject/global/licenses/sles-sap-12
• NUMBER_OF_LICENSES: the number of licenses you plan to purchase.
• CORES_PER_LICENSE: the number of cores per license. Enter 1-2 3-4, or 5+.
• PLAN: enter the plan length: 12-month or 36-month.
• REGION: the region where this commitment applies.

For example, the following commitment is for 4 SAP licenses with 3-4 cores per license for 36 months in the us-central1 region:

gcloud compute commitments create-license commitment-1
    --license https://www.googleapis.com/compute/v1/projects/myproject/global/licenses/sles-12
    --amount=4
    --cores-per-license=3-4
    --plan=36-month
    --region=us-central1

For example, the following commitment is for 2 SLES for SAP licenses with 1-2 cores per license for 12 months in the us-central1 region:

gcloud compute commitments create-license commitment-2
    --license https://www.googleapis.com/compute/v1/projects/myproject/global/licenses/sles-sap-12
    --amount=2
    --cores-per-license=1-2
    --plan=12-month
    --region=us-central1

API

Use the regionCommitments.insert method and include the licenseResource field to define the license commitment's properties.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments?requestId=OPTIONAL_UNIQUE_ID

{
    "name": COMMITMENT_NAME,
    "plan": PLAN,
    "category": "LICENSE",
    "licenseResource": {
      "coresPerLicense": CORES_PER_LICENSE,
      "amount": NUMBER_OF_LICENSES,
      "license": `LICENSE_URI`
      }
}

Replace the following:

• COMMITMENT_NAME: the name for your commitment.
• LICENSE_URI: the license URI. For example: https://www.googleapis.com/compute/v1/projects/myproject/global/licenses/sles-sap-12
• NUMBER_OF_LICENSES: the number of licenses you plan to purchase.
• CORES_PER_LICENSE: the number of cores per license. Enter 1-2 3-4, or 5+.
• PLAN: enter the plan length: 12-month or 36-month.
• REGION: the region where this commitment applies.

For example, the following commitment is for 4 SLES for SAP licenses with 3-4 cores per license for 36 months in the us-central1 region.

POST https://compute.googleapis.com/compute/v1/projects/myproject/regions/us-central1/commitments

{
    "name": "commitment-3",
    "plan": "THIRTY_SIX_MONTH",
    "category": "LICENSE",
    "licenseResource": {
      "coresPerLicense": "3-4",
      "amount": "4",
      "license": "https://www.googleapis.com/compute/v1/projects/suse-sap-cloud/global/licenses/sles-sap-12"
      }
}

Apply committed use discount recommendations

Committed use discount recommendations are available in the Google Cloud console. The Recommender generates a card with information about your VM usage over the last 30 days. If your VMs show a trend of uncommitted usage over 30 days, the Recommender classifies this as an opportunity to purchase committed use discounts to reduce your VM costs.

Usage is considered uncommitted and eligible if the following is true.

• The VM was active for the entire duration of the 30 days.
• The VM's SKU is part of an eligible committed use discount bucket.
• The VM's usage was not already covered by an existing commitment.

Recommendations are refreshed once per day and take the last 30 days of usage history into consideration.

Recommendations for committed use discounts are generated by two separate algorithms, which you can select from when purchasing (or accepting) them on the summary card.

• Stable usage recommendations cover minimum stable usage over time.
• Optimal recommendations are based on overall usage and might cover resources that are not on all the time.

You can read more about commitment recommendations in the committed use discount recommender documentation.

Limitations

Committed use discount recommendations are available for the CPU and memory component of machine type commitments only. Committed use discount recommendations are not available for SSD, GPU or license commitments.

Review and accept a recommendation

For how to purchase the recommended commitments, see purchasing recommendations.

Dismiss a recommendation

For how to dismiss your commitment recommendations or to restore recommendations that were previously dismissed, see dismissing recommendations.

History of recommendations

To view the history of your applied and dismissed commitment recommendations, see viewing the history of recommendations.

Enable committed use discount sharing

By default, resource-based CUDs are applied to the project where you purchased your resource-based commitments and are project-scoped discounts. If you move the project for which you purchased your commitments to a different Cloud Billing account, then you continue to receive the applicable committed use discounts for that project under the new Cloud Billing account.

To share the discount across eligible usage in all projects linked to your Cloud Billing account, enable committed use discount sharing from the Google Cloud console.

When you enable committed use discount sharing, the commitment scope is changed from Project to Billing account. After you change your commitment scope to Billing account by enabling discount sharing, you cannot disable discount sharing to revert back to project scope. Rather, Cloud Billing Support must perform this action for you.

Discount sharing works in conjunction with your attribution configuration. You can choose to use proportional attribution or prioritized attribution.

Unless you configure your attribution preferences first, when you enable discount sharing, it defaults to using proportional attribution for your Compute Engine resource-based commitments.

If you want to configure your attribution configuration before you enable discount sharing, see choose attribution for resource-based commitments for more information and how to enable each type of attribution.

Permissions required for this task

To perform this task, you must have the following permissions:

You need specific permissions on the Cloud Billing account to access billing account information. To update the commitment scope to enable discount sharing, you need a role that includes the following permission on the Cloud Billing account:

• billing.subscriptions.update on the Cloud Billing account

To gain this permission using a predefined role, ask your billing administrator to grant you the Billing Account Administrator role on the Cloud Billing account.

Complete the following steps to enable committed use discount sharing:

1. Sign in to your Cloud Billing account in the Google Cloud console.

   Sign in to your Cloud Billing account

2. At the prompt, choose the Cloud Billing account for which you'd like to configure your committed use discounts to use discount sharing. The Billing Overview page opens for the selected Cloud Billing account.

3. From the Billing navigation menu, select CUD analysis to view the Committed use discounts analysis page.

4. On the Committed use discount analysis page, in the Commitment type dropdown, select Resource-based commitments.

5. Below the Resource based commitments report title, locate the Commitment scope.

   • Project scope indicates that discount sharing is not enabled for resource-based committed use discounts. Project-scope discounts are only applied to eligible usage in the project in which the commitments are purchased.
   • Billing account scope indicates that discount sharing is already enabled for the resource-based commitments. Billing-account-scope commitments apply the committed use discounts across all eligible usage in all projects associated with the Cloud Billing account.

6. To change the commitment scope setting, select Edit.

   • If the current scope is Project, in the text entry box, type Enable to enable discount sharing across the billing account, then click Enable Billing Account Scope to save your changes.

     Caution: After you change your commitment scope to Billing account, discount sharing is enabled on all of the current and future projects associated with the Cloud Billing account. You cannot disable discount sharing to revert back to Project scope. Rather, Cloud Billing Support must perform this action for you.

   • If the current scope is Billing account, then discount sharing is already enabled. To disable discount sharing and revert to Project-scoped commitments, click Contact support.

Important: It can take up to 24 hours for a new discount sharing commitment scope to take effect. After 24 hours, confirm that your billing scope is set to Billing Account. If it isn't, contact Cloud Billing Support.

You only need to enable discount sharing on one project-scoped resource-based commitment to affect the scope of all resource-based commitments in the same Cloud Billing account. When you enable committed use discount sharing, your commitment scope changes as follows:

• All of your current and active resource-based committed use discounts in all of the projects under the same Cloud Billing account, including those you previously purchased and new ones you purchase in the future, are shared across your Cloud Billing account.
• Your sustained use discounts are also pooled and shared across all projects within your Cloud Billing account.
• When you change your commitment scope configuration, the change takes effect on the following day at 12 AM US and Canadian Pacific Time (UTC-8 or UTC-7).
• If you move the project to a new Cloud Billing account, your discount sharing settings change. For information on the effects of changing the Cloud Billing account for a project, see Change the Cloud Billing account linked to a project.

To get a better understanding of how committed use discounts impact and appear on your bill, see Understand your bill with committed use discounts.

Important: After you enable discount sharing through the console, you can only disable it with the assistance of Cloud Billing support. If you disable discount sharing with the assistance of Cloud Billing support, all committed use discounts revert to the default setting of applying only to the projects through which with they were purchased. The reverted setting becomes effective at the beginning of the following month.

Combine reservations with commitments

A committed use discount provides a 1- or 3-year discounted price agreement, but it does not reserve capacity in a specific zone. A reservation ensures that capacity is held in a specific zone even if the reserved VMs are not running. By combining a reservation with a commitment, you get discounted, reserved resources.

To purchase a commitment and get discounted prices for GPUs and Local SSDs, create and attach a reservation when purchasing the commitment. For these resources, the location and size of the reservation can't be changed for the duration of your commitment.

For information about commitments with attached reservations, see Attach reservations to commitments.

Note: If you move the project for which you purchased commitments to a different Cloud Billing account, then you continue to receive committed use discounts for that project under the new Cloud Billing account. Learn about changing the Cloud Billing account for a project.

View active commitments

View commitments in the console or the API.

Console

In the Google Cloud console, view a list of commitments in the Committed use discounts page.

Go to Committed use discounts

gcloud

Make a request using the commitments list command:

gcloud compute commitments list

The tool returns a list of commitments:

 NAME              REGION    END_TIMESTAMP                  STATUS
 my-commitment     us-east1  2018-03-17T00:00:00.000-07:00  NOT_YET_ACTIVE

API

You can get a list of commitments across all regions by making an aggregatedList request to the following URL:

https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/aggregated/commitments

Which returns a list of commitments:

"commitments": [
{
  "kind": "compute#commitment",
  "id": "3294122326373778983",
  "creationTimestamp": "2017-02-09T15:18:32.411-08:00",
  "name": "example-commitment",
  "region": "https://www.googleapis.com/compute/v1/projects/example-project/regions/us-central1",
  "selfLink": "https://www.googleapis.com/compute/v1/projects/example-project/regions/us-central1/commitments/example-commitment",
  "status": "NOT_YET_ACTIVE",
  "statusMessage": "The commitment is not yet active (its startTimestamp is in the future). It will not apply to current resource usage.",
  "plan": "TWELVE_MONTH",
  "startTimestamp": "2017-02-10T00:00:00.000-08:00",
  "endTimestamp": "2018-02-10T00:00:00.000-08:00",
  "resources": [
    {
      "type": "VCPU",
      "amount": "5"
    },
    {
      "type": "MEMORY",
      "amount": "32500"
    }]
  }
]

A commitment can have one of the following statuses:

• CREATING: the commitment is being created.
• NOT_YET_ACTIVE: the commitment has been created but is not yet active. Commitments are effective at midnight the following day.
• ACTIVE: the commitment is active.
• EXPIRED: the commitment has expired. Compute Engine reserves the right to remove expired commitments that are older than 210 days from the expiration date.

Modify a commitment

You can modify your active commitments in the following ways:

• You can change the auto-renew status for your commitment. For more information, see Renew commitments automatically.
• You can modify the amount of resources in your commitments by either merging or splitting your existing commitments. For more information, see Merge and split commitments.
• You can upgrade the term of your 1-year commitments and convert them into 3-year commitments. For more information, see Upgrade the term of commitments
• You can change the Cloud Billing account that is linked to, and pays for, the project where you purchased your resource-based commitments. Learn about changing the Cloud Billing account for a project.

After you create the commitment, you can't modify the commitment's project, type, or region.

Cancel a commitment

After you create a commitment, you can't cancel it. You must pay the agreed upon monthly amount for the duration of the commitment. Commitments are not affected by future pricing changes to the standard prices for Compute Engine resources.

If you accidentally purchased a commitment or made a mistake configuring your commitment, contact Google Cloud Billing Support for help.

Understand your bill with committed use discounts

Read the following documents to gain a better understanding of your billing:

• View and download the cost details of your invoice or statement.
• Analyze the effectiveness of your committed use discounts.
• Understand your savings with cost breakdown reports.

Support

If you have any questions regarding committed use discounts on your bill, you can contact Google Cloud support.

What's next

• Learn how to merge and split resource-based commitments.
• Learn how to upgrade the term of resource-based commitments.
• Learn how to analyze the effectiveness of your resource-based CUDs.
• Learn how to renew resource-based commitments automatically.
• Review the prices of your VMs with and without CUDs.