Renewal Overview

You can renew yearly/monthly instances you created to prolong their validity periods.

If an instance is renewed when it is in a grace period or retention period, the renewal for this instance starts from the time when the resource expires, instead of the time when the instance is renewed.

Renewal Functions

**Table 1** Function descriptions
Function	Description
Manually Renewing Resources	You can manually renew resources to extend their usage duration.
Enabling Auto-Renewal	You can enable auto-renewal for instances that you plan to use for a long time to avoid instance release due to untimely renewal.
One-Click Renewal	You can renew a large number of instances at a time.
From Yearly/Monthly to Pay-per-Use Upon Expiration	You can change the billing mode to pay-per-use if future service development is unpredictable.
Non-Renewal After Expiration	You will no longer use instances after they expire.

Impacts of Expiration

After a yearly/monthly instance expires, renew it in a timely manner if you want to continue using the instance.

When the instance enters the grace period, you can still use it.
When the grace period ends, the retention period starts. During this time, the instance is frozen and cannot be used, but its stored data is retained.
After the retention period ends, the instance will be automatically deleted. In this case, the instance cannot be retrieved or renewed.

If a yearly/monthly instance is renewed when it is in a grace period or retention period, the time spent in the period will be deducted from the renewal duration.

Example: You purchased a monthly EVS disk on March 31, 2024, and the resource would expire on April 30, 2024. The grace period and retention period of yearly/monthly resources on Huawei Cloud (International website) are both 15 days. On May 18, 2024, the resource was in the grace period and renewed for one month. There are only 13 days remaining because the resource would expire on May 31, 2024.

Viewing the Expiration Time

On the Renewals page, you can filter resources by Expires and view the expiration time of each instance in the Provisioned/Expires column in the renewal list.

Click to enlarge

By Expires, you can quickly search for instances that are in the specified status or will expire in the specified period.

Expires in 7 days, 15 days, 30 days, or custom number of days: Instances or resources that are about to expire in the specified time range can be renewed in advance.
Expired (in grace period): Instances will enter the grace period upon expiration. In this period, the instances can still be used.
Frozen (in retention period): Instances will enter the retention period after the grace period ends. In this period, the instances cannot be used.

Renewal Constraints

**Table 2** Renewal constraints
Category	Description
Renewals not supported	Reserved instances are not renewable. Pay-per-use resources and spot instances are not renewable. If an order is not completed, the resources cannot be renewed. If an order for changing the specifications of a yearly/monthly resource has been submitted but has not been completed, the resource cannot be renewed. Yearly/monthly resources that have been changed or are being changed to pay-per-use billing mode are not renewable. If a partner's customer accounts in the reseller model is frozen by the partner, the renewals are not allowed for the accounts. Contact the partner to handle it. Unsubscribed or released resources are not renewable. Products no longer available are not renewable.
Overall renewal constraints	If a yearly/monthly resource has supplemented resources, it cannot be renewed until the supplements are provisioned. This ensures that both the primary and supplemented resources expire at the same time. Attached resources must be renewed collectively, while configured resources can be renewed either collectively or independently. Example: You subscribed to a monthly ECS with a system disk attached and a VPC configured. When you renew the ECS, the attached system disk must be renewed together, while the configured VPC can be renewed independently. Solution product portfolios and DevCloud packages must be renewed as a whole. If a small-granularity package has a renewal discount, you can only renew the package as a whole. If it does not have a renewal discount, you can renew the resources in the package separately. Example: You have purchased a promotional package of a monthly ECS (specifications: s6.small.1 ECS + VPC network). If it has a renewal discount, you must renew the whole package to apply that discount. If it does not have a renewal discount, you can renew the ECS and VPC separately. For any other package, you can renew it as a whole or renew specific resources in the package. However, after you renew specific resources in a package, the package cannot be renewed as a whole any longer and discounts for the whole package renewal cannot be applied. Resources in a combined service like an ECS need to be renewed as a whole.
Batch renewal constraints	Resources in commercial use cannot be renewed together with those pending commercial use. Offline Dedicated Cloud cannot be renewed in batches. If an order is not completed, the resources cannot be renewed in batches. Trial products cannot be renewed in batches. Portfolio products cannot be renewed in batches. Products no longer available cannot be renewed in batches.