Stay organized with collections
Save and categorize content based on your preferences.
You can upgrade the term of your 1-year commitments and convert them into
3-year commitments to get a higher discount rate for your committed resources
and continue receiving committed use discounts (CUDs) for a longer time period.
This document shows you how to upgrade the term of your commitment from 1 year
to 3 years.
How a term upgrade works
When you upgrade the term for your commitment, the expiration date of the
commitment moves into the future by two years. The upgraded commitment term
becomes valid at 12 AM US and Canadian Pacific Time (UTC-8, or UTC-7 during
daylight saving time) on the day following the upgrade operation, and you begin
to receive the new CUD percentage that is applicable for your upgraded
term.
Upgrading your commitment's term changes the
term extension eligibility window
for your commitment. After the term upgrade takes effect, Compute Engine
updates the eligibility window to remain open up to 1 year from the start date
of the ongoing term. Upgrading the term doesn't affect the following properties
of your commitment:
Name
Start date
Region
Project
Commitment type
Auto renew status
Committed resources
The process of term upgrade remains the same regardless of whether your
commitment has a preset term length or a custom term length. Any attached
reservations for your commitment continue to exist throughout the
lifetime of your upgraded term, unless you manually replace them.
Example of an upgraded commitment
The following table shows an example where the term of an existing commitment
(commitment-1) gets upgraded by 2 years:
Commitment property
Before term upgrade
After term upgrade
Name
commitment-1
commitment-1
Type
N2
N2
Region
us-central-1
us-central-1
Project
example-project-1
example-project-1
Resources
vCPUs: 200
Memory: 200 GB
vCPUs: 200
Memory: 200 GB
Term
1 year
3 years
Start date*
January 1, 2020
January 1, 2020
End date†
January 1, 2021
January 1, 2023
Term extension eligibility window open until
May 1, 2020
January 1, 2021
Auto-renew status
Disabled
Disabled
*Commitment starts at 12 AM US and Canadian Pacific Time
(UTC-8 or UTC-7) on the specified start date.
†Commitment ends at 12 AM US and Canadian Pacific Time
(UTC-8 or UTC-7) on the specified end date.
Quota considerations
You don't typically need to request additional quota when you upgrade your
commitment's term. However, if you upgrade a commitment's term on the same day
that it expires, you must verify
that you still have sufficient quota available. That's because on the day that a
commitment expires, whatever quota the commitment was using up gets released
back into your pool of available quota, and it might get used up by your other
business needs.
Pricing implications
Your commitment fee is the sum of the discounted prices of all your committed
resources. When you upgrade your commitment's term, Compute Engine
applies the new 3-year CUD percentage and recalculates the discounted price for
each committed resource. To do this recalculation, Compute Engine uses
the prevailing on-demand price of each resource on the day your original term
became active. This new discounted price for each resource stays the same until
the end of your upgraded term, even if the on-demand prices change.
Limitations
You can upgrade the term for only active commitments.
You can't upgrade the term for software license commitments.
Perform a term upgrade
Upgrade your commitment's term by using the gcloud CLI,
Google Cloud console, or the Compute Engine API.
Permissions required for this task
To perform this task, you must have the following
permissions:
compute.commitments.update on the project or organization.
Console
In the Google Cloud console, select the project where you want to
upgrade your commitment's term, and go to the Committed use discounts
page.
To initiate the term upgrade operation for a commitment, select an active
hardware commitment in the Hardware commitments tab of the
Commitment list page and click
event_available Upgrade.
Alternatively, you can click the name of the active commitment that you
want to upgrade. After the Hardware commitment details page opens,
click event_available Upgrade.
In the Upgrade committed use discount pane that appears, verify the
New end time of your modified commitment and click Upgrade.
To finish the term upgrade operation and return to the Commitment list
page, in the Upgrade your commitment? dialogue that appears, review
the terms and conditions and then click Upgrade.
COMMITMENT_NAME: the name of the commitment whose
term you want to upgrade.
REGION: the region of your commitment whose term
you want to upgrade.
PROJECT_NAME: the name of the project for which
you want to upgrade the commitment.
For example, consider a 1-year commitment, commitment-upgrade-example, in
us-central1 region and for the project project-upgrade-example. The
following gcloud CLI command upgrades the commitment's term and
modifies it into a 3-year commitment.
PROJECT_ID: the project ID of the project where
you want to upgrade your commitment's term.
REGION: the region of the commitment whose term
you want to upgrade.
COMMITMENT_NAME: the name of the commitment whose
term you want to upgrade.
For example, consider a 1-year commitment, commitment-upgrade-example in
us-central1 region and for the project project-upgrade-example. The
following Compute Engine API request upgrades the commitment's term
and modifies it into a 3-year commitment.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eYou can upgrade your 1-year commitments to 3-year commitments to secure a higher discount rate on committed resources and extend the period for receiving committed use discounts (CUDs).\u003c/p\u003e\n"],["\u003cp\u003eUpgrading the commitment term extends the expiration date by two years, and the new CUD rate becomes effective the day after the upgrade at 12 AM US and Canadian Pacific Time.\u003c/p\u003e\n"],["\u003cp\u003eThe term upgrade process does not alter the commitment's name, start date, region, project, commitment type, auto-renew status, or committed resources.\u003c/p\u003e\n"],["\u003cp\u003eUpgrading the commitment term affects the term extension eligibility window, extending the window up to 1 year from the ongoing term's start date.\u003c/p\u003e\n"],["\u003cp\u003eThe discounted prices are recalculated when upgrading the commitment's term using the on-demand prices from the day the original term became active, and these new discounted prices remain consistent throughout the upgraded term.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nYou can upgrade the term of your 1-year commitments and convert them into\n3-year commitments to get a higher discount rate for your committed resources\nand continue receiving committed use discounts (CUDs) for a longer time period.\n\nThis document shows you how to upgrade the term of your commitment from 1 year\nto 3 years.\n\nHow a term upgrade works\n\nWhen you upgrade the term for your commitment, the expiration date of the\ncommitment moves into the future by two years. The upgraded commitment term\nbecomes valid at 12 AM US and Canadian Pacific Time (UTC-8, or UTC-7 during\ndaylight saving time) on the day following the upgrade operation, and you begin\nto receive the new CUD percentage that is applicable for your upgraded\nterm.\n\nUpgrading your commitment's term changes the\n[term extension eligibility window](/compute/docs/committed-use-discounts/extend-commitment-term#term-extension-eligibility-window)\nfor your commitment. After the term upgrade takes effect, Compute Engine\nupdates the eligibility window to remain open up to 1 year from the start date\nof the ongoing term. Upgrading the term doesn't affect the following properties\nof your commitment:\n\n- Name\n- Start date\n- Region\n- Project\n- Commitment type\n- Auto renew status\n- Committed resources\n\nThe process of term upgrade remains the same regardless of whether your\ncommitment has a preset term length or a custom term length. Any attached\nreservations for your commitment continue to exist throughout the\nlifetime of your upgraded term, unless you manually replace them.\n\nExample of an upgraded commitment\n\nThe following table shows an example where the term of an existing commitment\n(`commitment-1`) gets upgraded by 2 years:\n\n| **Commitment property** | **Before term upgrade** | **After term upgrade** |\n|----------------------------------------------|----------------------------------------|----------------------------------------|\n| Name | commitment-1 | commitment-1 |\n| Type | N2 | N2 |\n| Region | us-central-1 | us-central-1 |\n| Project | example-project-1 | example-project-1 |\n| Resources | - vCPUs: 200 \u003c!-- --\u003e - Memory: 200 GB | - vCPUs: 200 \u003c!-- --\u003e - Memory: 200 GB |\n| Term | 1 year | 3 years |\n| Start date\\* | January 1, 2020 | January 1, 2020 |\n| End date† | January 1, 2021 | January 1, 2023 |\n| Term extension eligibility window open until | May 1, 2020 | January 1, 2021 |\n| Auto-renew status | Disabled | Disabled |\n\n\n^\\*^Commitment starts at 12 AM US and Canadian Pacific Time\n(UTC-8 or UTC-7) on the specified start date. \n\n^†^Commitment ends at 12 AM US and Canadian Pacific Time\n(UTC-8 or UTC-7) on the specified end date.\n\n\u003cbr /\u003e\n\nQuota considerations\n\nYou don't typically need to request additional quota when you upgrade your\ncommitment's term. However, if you upgrade a commitment's term on the same day\nthat it expires, you must [verify](/compute/docs/instances/signing-up-committed-use-discounts#to-check-quota-in-the-console)\nthat you still have sufficient quota available. That's because on the day that a\ncommitment expires, whatever quota the commitment was using up gets released\nback into your pool of available quota, and it might get used up by your other\nbusiness needs.\n\nPricing implications\n\nYour commitment fee is the sum of the discounted prices of all your committed\nresources. When you upgrade your commitment's term, Compute Engine\napplies the new 3-year CUD percentage and recalculates the discounted price for\neach committed resource. To do this recalculation, Compute Engine uses\nthe prevailing on-demand price of each resource on the day your original term\nbecame active. This new discounted price for each resource stays the same until\nthe end of your upgraded term, even if the on-demand prices change.\n| **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.\n\nLimitations\n\n- You can upgrade the term for only active commitments.\n- You can't upgrade the term for software license commitments.\n\nPerform a term upgrade\n\nUpgrade your commitment's term by using the gcloud CLI,\nGoogle Cloud console, or the Compute Engine API.\n| **Note:** If you are using the gcloud CLI or the Compute Engine API to upgrade a commitment's term and also want to [enable auto renew](/compute/docs/instances/renew-commitments-automatically) on that commitment, then you must do so using two separate operations. You can perform these two operations at the same time using the Google Cloud console, but on the gcloud CLI or the Compute Engine API, you must enable auto renew either before or after you upgrade the commitment's term.\n\nPermissions required for this task\n\nTo perform this task, you must have the following\n[permissions](/iam/docs/overview#permissions):\n\n\n- `compute.commitments.update` on the project or organization. \n\nConsole\n\n1. In the Google Cloud console, select the project where you want to\n upgrade your commitment's term, and go to the **Committed use discounts**\n page.\n\n [Go to Committed use discounts](https://console.cloud.google.com/compute/commitments)\n2. To initiate the term upgrade operation for a commitment, select an active\n hardware commitment in the **Hardware commitments** tab of the\n **Commitment list** page and click\n event_available **Upgrade**.\n\n - Alternatively, you can click the name of the active commitment that you want to upgrade. After the **Hardware commitment details** page opens, click event_available **Upgrade**.\n3. In the **Upgrade committed use discount** pane that appears, verify the\n **New end time** of your modified commitment and click **Upgrade**.\n\n4. To finish the term upgrade operation and return to the **Commitment list**\n page, in the **Upgrade your commitment?** dialogue that appears, review\n the terms and conditions and then click **Upgrade**.\n\ngcloud\n\nTo upgrade your commitment's term, use the\n[gcloud compute commitments update command](/sdk/gcloud/reference/compute/commitments/update)\ncommand with the `--plan` flag. \n\n```\ngcloud compute commitments update COMMITMENT_NAME \\\n --plan=36-month \\\n --region=REGION \\\n --project=PROJECT_NAME\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eCOMMITMENT_NAME\u003c/var\u003e: the name of the commitment whose term you want to upgrade.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region of your commitment whose term you want to upgrade.\n- \u003cvar translate=\"no\"\u003ePROJECT_NAME\u003c/var\u003e: the name of the project for which you want to upgrade the commitment.\n\nFor example, consider a 1-year commitment, `commitment-upgrade-example`, in\n`us-central1` region and for the project `project-upgrade-example`. The\nfollowing gcloud CLI command upgrades the commitment's term and\nmodifies it into a 3-year commitment. \n\n```\ngcloud compute commitments update commitment-upgrade-example \\\n --plan=36-month \\\n --region=us-central1 \\\n --project=project-upgrade-example\n```\n\nREST\n\nTo upgrade your commitment's term, use the\n[`regionCommitments.update` method](/compute/docs/reference/rest/v1/regionCommitments/update). \n\n```\nPATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments/COMMITMENT_NAME\n{\n \"name\": COMMITMENT_NAME,\n \"plan\": \"THIRTY_SIX_MONTH\",\n}\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the project ID of the project where you want to upgrade your commitment's term.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region of the commitment whose term you want to upgrade.\n- \u003cvar translate=\"no\"\u003eCOMMITMENT_NAME\u003c/var\u003e: the name of the commitment whose term you want to upgrade.\n\nFor example, consider a 1-year commitment, `commitment-upgrade-example` in\n`us-central1` region and for the project `project-upgrade-example`. The\nfollowing Compute Engine API request upgrades the commitment's term\nand modifies it into a 3-year commitment. \n\n```\nPATCH https://compute.googleapis.com/compute/v1/projects/project-upgrade-example/regions/us-central1/commitments/commitment-upgrade-example\n{\n \"name\": \"commitment-upgrade-example\",\n \"plan\": \"THIRTY_SIX_MONTH\",\n}\n```\n\nWhat's next\n\n- Learn how to [renew commitments automatically](/compute/docs/instances/renew-commitments-automatically).\n- Learn how to [extend the term length of resource-based commitments](/compute/docs/committed-use-discounts/extend-commitment-term).\n- Learn how to [merge and split resource-based commitments](/compute/docs/instances/merge-and-split-commitments).\n- Learn how to [analyze the effectiveness of your CUDs](/billing/docs/how-to/cud-analysis-resource-based)."]]
