1년 약정 기간을 업그레이드하고 3년 약정으로 변환하여 약정된 리소스에 대해 더 높은 할인율을 적용받고 더 오랜 기간 동안 계속 약정 사용 할인을 받을 수 있습니다.
이 문서에서는 약정 기간을 1년에서 3년으로 업그레이드하는 방법을 보여줍니다.
약정 기간 업그레이드 방식
약정 기간을 업그레이드하면 약정 만료일이 2년 미뤄집니다. 업그레이드된 약정 기간은 미국 및 캐나다 태평양 표준시를 기준으로 업그레이드 작업 다음 날 오전 12시(UTC-8 또는 일광 절약 시간에는 UTC-7)에 유효하며 새로운 CUD 비율이 적용됩니다.
약정 기간을 업그레이드하면 약정에 대한 기간 연장 자격요건 기간이 변경됩니다. 기간 업그레이드가 적용되면 Compute Engine은 자격요건 기간을 업데이트하여 진행 중인 기간의 시작일로부터 최대 1년 동안 유지합니다. 약정 기간을 업그레이드해도 약정의 다음 속성에는 영향을 미치지 않습니다.
이름
시작일
지역
프로젝트
약정 유형
자동 갱신 상태
커밋된 리소스
약정 기간이 미리 설정되어 있는지 커스텀 기간이 있는지 여부에 상관없이 기간 업그레이드 프로세스는 동일하게 유지됩니다. 약정에 연결된 예약은 수동으로 대체하지 않는 한 업그레이드된 기간의 전체 기간에 걸쳐서 계속 존재합니다.
업그레이드된 약정 예시
다음 표에서는 기존 약정의 기간(commitment-1)이 2년으로 업그레이드되는 예시를 보여줍니다.
약정 속성
기간 업그레이드 전
기간 업그레이드 후
이름
commitment-1
commitment-1
유형
N2
N2
지역
us-central-1
us-central-1
프로젝트
example-project-1
example-project-1
리소스
vCPU: 200
메모리: 200GB
vCPU: 200
메모리: 200GB
용어
1년
3년
시작 날짜*
2020년 1월 1일
2020년 1월 1일
종료일†
2021년 1월 1일
2023년 1월 1일
기간 연장 자격 요건 신청 기간:
2020년 5월 1일
2021년 1월 1일
자동 갱신 상태
사용 중지됨
사용 중지됨
*약정은 미국 및 캐나다 태평양 표준시를 기준으로 지정된 시작 날짜의 오전 12시(UTC-8 또는 UTC-7)에 시작됩니다. †약정은 미국 및 캐나다 태평양 표준시를 기준으로 지정된 종료 날짜의 오전 12시(UTC-8 또는 UTC-7)에 종료됩니다.
할당량 고려 사항
일반적으로 약정 기간을 업그레이드할 때는 추가 할당량을 요청할 필요가 없습니다. 하지만 약정 기간이 만료되는 날에 약정 기간을 업그레이드하는 경우, 아직 사용 가능한 할당량이 충분한지 확인해야 합니다. 이는 약정이 만료되는 날에 약정에 사용된 할당량이 사용 가능한 할당량 풀로 다시 릴리스되고 다른 비즈니스 요구사항에 의해 소진될 수 있기 때문입니다.
가격 책정 영향
약정 요금은 모든 약정 리소스의 할인된 가격 합계입니다. 약정 기간을 업그레이드하면 Compute Engine이 새로운 3년 CUD 백분율을 적용하고 각 약정 리소스에 대해 할인된 가격을 다시 계산합니다. 이 계산을 수행하기 위해 Compute Engine은 원래 기간이 활성화된 날짜에 각 리소스의 우세한 주문형 가격을 사용합니다. 각 리소스에 대한 이러한 새로운 할인 가격은 주문형 가격이 변경되더라도 업그레이드된 기간이 종료될 때까지 동일하게 유지됩니다.
제한사항
활성 약정의 기간만 업그레이드할 수 있습니다.
소프트웨어 라이선스 약정 기간을 업그레이드할 수 없습니다.
약정 기간 업그레이드 수행
gcloud CLI,Google Cloud 콘솔 또는 Compute Engine API를 사용하여 약정 기간을 업그레이드합니다.
project-upgrade-example 프로젝트의 us-central1 리전에 있는 1년 약정 commitment-upgrade-example을 예로 들어 보겠습니다. 다음 Compute Engine API 요청은 약정 기간을 업그레이드하여 3년 약정으로 수정합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-11(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)."]]
