All Products
Search
Document Center

:Time-segmented elasticity assurances

Last Updated:Aug 18, 2026

If your business experiences cyclical fluctuations in resource demand, such as traffic peaks at fixed times daily or weekly, you can use a time-segmented elasticity assurance to lock in ECS capacity in advance. Unlike Immediate or Scheduled Elasticity Assurance, a time-segmented elasticity assurance offers more flexible, recurring capacity assurance. It activates repeatedly during preset time slots (for example, 18:00 to 24:00 daily) within a specified period (for example, 30 days) to precisely match business scenarios with tidal traffic patterns.

Overview

A time-segmented elasticity assurance is a resource purchasing and usage model that balances flexibility with guaranteed availability, designed to provide capacity assurance for pay-as-you-go ECS instances. This model is ideal for daily elastic demands with irregular, short usage times and durations.

Key concepts

Concept

Description

Resource pool

Formerly known as a private pool. After you create a time-segmented elasticity assurance, the system locks inventory for your account and creates a dedicated resource pool for your exclusive use.

Capacity

The number of assured instances that can be created from the resource pool. Unused capacity refers to the number of assured instances that can still be created. Used capacity is the number of instances that you have created.

Assurance duration

The total number of days the assurance policy is active. For example, if you require assurance from 12:00 to 17:00 every day for one week, starting next Monday, the assurance duration is one week.

Assurance start time

The time when the assurance policy begins to take effect. For example, if you require assurance from 12:00 to 17:00 every day for one week, starting next Monday, the assurance start time is next Monday.

Inactive period

A period within the assurance duration when the policy is not active. During this time, the capacity is in a locked state, and you cannot use it to create ECS instances. Unlike an expired assurance, it becomes active again according to its schedule.

Use cases

  • Predictable, tidal workloads: For example, daily traffic surges in the gaming and e-commerce industries, or peak traffic during holidays and non-working hours.

    image

  • Regular, periodic peak workloads: For example, peak hours for online education platforms or financial services during fixed business hours.

Lifecycle

image

Billing

When you use a time-segmented elasticity assurance, you must pay an upfront assurance fee. When you use the reserved capacity, you also incur ECS instance fees.

  • Assurance fee:

  • ECS instance fees: Billed on a pay-as-you-go basis.

For example, if you want to assure capacity for an ecs.g7.2large instance in the China (Hong Kong) region for 8 hours, the assurance fee is calculated as follows: ≈ USD 0.31.

Note

The prices in this example are for reference only. For the latest pricing, see the ECS pricing page.

Create a time-segmented assurance

  1. Log on to the ECS console.

  2. In the left-side navigation pane, choose Deployment & Elasticity > icon1 > Elasticity Assurance.

  3. On the Elasticity Assurance page, click Create Elasticity Assurance.

  4. On the Create Elasticity Assurance page, configure the parameters for the time-segmented elasticity assurance and click Next.

    Parameter

    Description

    Elasticity Assurance Name

    Enter a name for the time-segmented elasticity assurance to help you identify it.

    The name must be 2 to 128 characters long. It must start with a letter or a Chinese character, and cannot start with http:// or https://. It can contain digits, colons (:), underscores (_), and hyphens (-).

    Region/Zone

    Select the region and availability zone of the instance type you want to assure.

    You cannot change the Region/Zone after the time-segmented elasticity assurance is created.

    Instance Type

    Select the instance type you want to assure.

    Capacity (Instances)

    Specify the number of instances for which you want to assure capacity. Valid values: 1 to 1,000.

    Validity Period Starts

    The time when the assurance becomes active. Options include:

    • Now: The assurance becomes active immediately after it is created. Reserved resources are used to guarantee the availability of pay-as-you-go instances.

    • Specify Effective Time: The assurance becomes active at a specified time after it is created. Reserved resources are used to guarantee the availability of pay-as-you-go instances.

    Duration (in Days)

    Enter a positive integer from 1 to 365.

    Validity Period Start Time

    If you set Validity Period Starts to Specify Effective Time, you must also set the Validity Period Start Time.

    Duplicated Rule

    • Recurrence policy: You can select one of the following recurrence rules:

      • Daily: Select the recurrence interval in days. For example, every 2 days means the assurance takes effect once every two days within the assurance duration.

      • Weekly: Select one or more days of the week on which the assurance will be active. Multiple days are supported.

      • Monthly: Select a start and end day. For example, 1st to 6th means the assurance is active from the 1st to the 6th day of each month.

    • Time: The start and end times must be on the hour and must be at least 4 hours apart.

    Private Pool Type

    • Open: A private pool that can be shared within your organization. Any instance that matches an open private pool can use its resources. You can also explicitly specify an open private pool at instance startup.

    • Targeted: A private pool reserved for a specific scenario or service. You must explicitly specify the pool when you create the instance.

    Description

    Enter a description for the time-segmented elasticity assurance to help you identify its purpose.

    Tag

    You can add a tag when you create a time-segmented elasticity assurance. You can also enable tag matching for open private pools for more fine-grained resource management.

  5. On the Preview page, confirm the assurance information, review the service notes and assurance fee, select I have read and understood the notes., and then click Submit.

Modify the recurrence rule

You can modify the assurance schedule of a time-segmented elasticity assurance only by calling the ModifyElasticityAssurance API operation. When you modify the schedule, the total assured duration must remain the same. You can modify the assurance schedule by changing the following parameters:

  • RecurrenceType: The recurrence rule type for the time-segmented elasticity assurance. Valid values:

    • Daily: The assurance recurs daily.

    • Weekly: The assurance recurs weekly.

    • Monthly: The assurance recurs monthly.

  • RecurrenceValue: The recurrence value for the time-segmented elasticity assurance.

    • If RecurrenceType is set to Daily, you can specify only one value from 1 to 31. For example, a value of 2 means the assurance recurs every two days.

    • If RecurrenceType is set to Weekly, you can specify multiple values separated by commas (,). The values for Sunday through Saturday are 0, 1, 2, 3, 4, 5, and 6, respectively. For example, a value of 1,2 means the assurance recurs on Mondays and Tuesdays.

    • If RecurrenceType is set to Monthly, the format is A-B. The values of A and B must be between 1 and 31, and B must be greater than or equal to A. For example, a value of 2-14 means the assurance recurs from the 2nd to the 14th day of each month.

  • StartHour: The start time of the recurring assurance. This must be on the hour. The interval between StartHour and EndHour must be at least 4 hours.

  • EndHour: The end time of the recurring assurance.

Modification examples

Modification method

Before modification

After modification

Modify the recurrence value, start time, and end time without changing the recurrence type.

RecurrenceType: Weekly

RecurrenceValue: 1,2

StartHour: 4

EndHour: 8

RecurrenceType: Weekly

RecurrenceValue: 3,4

StartHour: 10

EndHour: 14

Modify the recurrence type, recurrence value, start time, and end time.

RecurrenceType: Weekly

RecurrenceValue: 1,2

StartHour: 4

EndHour: 8

RecurrenceType: Monthly

RecurrenceValue: 11-12

StartHour: 9

EndHour: 13

Share a time-segmented assurance

Prerequisites

  • You have created a resource share for the elasticity assurance resource type. For more information, see Create a resource share.

  • The time-segmented elasticity assurance to be shared must be in the Active or Prepared state.

Procedure

  1. Log on to the ECS console.

  2. In the left-side navigation pane, choose Deployment & Elasticity > icon1 > Elasticity Assurance.

  3. Find the time-segmented elasticity assurance that you want to share and click Initiate Share in the Operation column.

  4. In the Share Private Pool dialog box, select a resource share and click OK.

  5. View the sharing status of the private pool.

    The Share Management tab displays the resource shares to which the private pool belongs and shows the usage of its shared capacity.

    On the Share Management tab, you can click Initiate Share to add the private pool to a resource share, or click Cancel Share in the record of an associated resource share to remove the association.

Capacity monitoring

Capacity monitoring shows the historical capacity data and usage of the time-segmented elasticity assurance.

  1. Log on to the ECS console.

  2. In the left-side navigation pane, choose Deployment & Elasticity > icon1 > Elasticity Assurance.

  3. Click the ID of the time-segmented elasticity assurance, or click Details in the Operation column.

  4. On the details page of the time-segmented elasticity assurance, click the Capacity Monitoring tab.

  5. Select a start date and an end date to view the total capacity, used capacity, and utilization rate for the specified period.