You need to enable JavaScript to run this app.
Elastic Compute Service

Elastic Compute Service

Copy page
Download PDF
Temporary upgrade of bandwidth
Creating temporary bandwidth upgrade tasks
Copy page
Download PDF
Creating temporary bandwidth upgrade tasks
You can use the orchestration feature to batch upgrade the temporary bandwidth of Subscription EIPs. This way, you can handle traffic peaks (during holidays, promotions, and other periods), thereby supporting the stable operation of your business while saving bandwidth costs during off-peak hours.​
tip​
This feature is currently in Beta. If you need a trial, contact your account manager.​
Concept​
​
Concept​
Description​
Temporary bandwidth upgrade​
Temporarily increase the bandwidth upper limit of an EIP for a specific period to meet sudden business growth or temporary high traffic requirements. The bandwidth upper limit automatically reverts to its original value when the period ends.​
Security block​
A security measure that restricts the access to or usage of an EIP, implemented to safeguard network security and prevent the continuation of illegal or malicious activities.​
​
Prerequisites​
  • The EIP pending temporary bandwidth upgrade is associated with an instance. For more information, see Associating EIPs.​
Limits​
​
Limits​
Description​
EIP​
Temporary bandwidth upgrades are only supported for Subscription EIPs.​
​
Subscription EIPs in the blocked status do not support temporary bandwidth upgrade.​
Time​
The minimum duration for a temporary bandwidth upgrade is 1 hour, and the maximum duration is 720 hours (30 days).​
​
When you upgrade the bandwidth of an EIP that is currently undergoing a temporary bandwidth upgrade, the new bandwidth upper limit cannot be lower than the current bandwidth upper limit, and the new restoration time (execution start time plus duration) must be later than the current restoration time (execution start time plus duration).​
For example, if the restoration time for the first temporary bandwidth upgrade of an EIP is June 20, then the earliest restoration time for the second temporary bandwidth upgrade is June 21.​
​
Usage notes​
​
Temporary bandwidth upgrade phase​
Description​
Before the upgrade​
For fee changes related to temporary bandwidth upgrades, see Billing rules for temporary configuration upgrades.​
Upgrading​
You cannot decrease the bandwidth upper limit for an EIP undergoing a temporary bandwidth upgrade. We recommend that you specify an appropriate bandwidth upper limit before you initiate a temporary bandwidth upgrade.​
​
EIPs undergoing a temporary bandwidth upgrade cannot be unsubscribed. If you want to unsubscribe an EIP of this type, you need to wait until the restoration time is reached and all unsubscription rules are satisfied.​
After the upgrade​
When the temporary bandwidth upgrade expires, the bandwidth upper limit is automatically restored. This may disrupt business traffic transmission and cause packet loss. Evaluate the potential impact on your business and proceed with caution.​
​
Procedure ​
  1. Log in to the ECS console.​
  1. In the left-side navigation pane, click "Maintenance & Monitoring > Orchestration".​
  1. In the top menu bar, select the region where your business is located.​
  1. On the "CloudOps Orchestration" page, click the "Common tasks" tab.​
  1. Click the "Temporary upgrade of bandwidth" menu.​
  1. Click the "Create task" button and configure the parameters described in the following table.​
  • ​
    Parameter​​
    Description​
    Sample value​
    Select resource​
    ​
    ​
    Resource scope​
    The type of resource on which you want to execute the O&M command. The default value is "EIP".​
    EIP​
    Select Elastic IP (EIP)​
    Select EIPs that are eligible for batch operations based on information such as EIP name or ID, and association status. You can select multiple EIPs.​
    tip​
    You can select up to 100 EIPs at the same time.​
    -​
    Argument settings​
    ​
    ​
    Execution mode​
    Supported task execution modes:​
    • Execute immediately: After the job is created, it is executed for one time immediately.​
    • Timed execution: The task is executed automatically once at the time you specify.​
    tip​
    The execution time must be accurate to the minute and can not be earlier than the current time.​
    • Periodic execution (default): The task is executed automatically on a cycle starting from the specified start time, at intervals you specify (in minutes, hours, or days), and stops automatically at the specified end time. You need to configure the following information:​
    • Repeat cycle: Specify the interval at which the job is executed repeatedly. The repeat interval must be longer than the timeout period. Value:​
    • by minute: The minimum interval is 5 minutes.​
    • by hour: The minimum interval is 1 hour.​
    • by day: The minimum interval is 1 day.​
    • Start time: Specify the time when the periodic job is first executed. This time must be later than the current time.​
    • Stop time: Specify the time when the periodic task stops. The task automatically stops at this time.​
    • If the task is not being executed at the stop time, it automatically stops and will never be executed again.​
    • If the job is being executed at the stop time, it automatically stops after the execution is complete and will never be executed again.​
    • If the interval between the stop time and the start time is less than one repeat cycle, the task is executed only once.​
    • Time zone: Fixed to GMT +08:00 (China Standard Time).​
    tip​
    The execution interval is independent of the actual execution duration of the task and is calculated based on the "Start time" you specify. For example, if the start time for a job is 2022-12-20 11:00:00, the repeat cycle is 1 hour, and the duration of the first execution is 3 minutes, the second execution starts at 2022-12-20 12:00:00.​
    Execute immediately​
    Duration​
    Select the duration for temporary bandwidth. The valid duration ranges from 1 to 720 hours. The default duration is 4 hours.​
    4 hours​
    Maximum bandwidth​
    Select the bandwidth upper limit for the EIP in the temporary upgrade. The valid upper limit ranges from 1 to 1,000 Mbps. The default upper limit is 100 Mbps.​
    100Mbps​
    Concurrency control​
    ​
    ​
    Concurrency rate​
    • Specify the number of concurrent executions for a batch instance task, which refers to the maximum number of instances that can undergo operations or receive requests at the same time. For example, if you have 50 instances and set this parameter to 10, the task will be executed in 5 batches, and commands will be sent to 10 instances simultaneously in each batch.​
    • Value range: 1-100.​
    10​
    Maximum error count​
    Specify the maximum number or percent of errors allowed while executing a temporary bandwidth upgrade task within a specific operation or scope.​
    • Error count: Applicable to scenarios where the error count needs attention. Value range: 0-100.​
    • If the error count is set to 0, no errors are allowed. That is, if an error occurs even once while performing a task, the entire task will stop (fail).​
    • If the error count is set to 100, a maximum of 100 errors is allowed. That is, as long as the number of errors during the execution of a task does not exceed 100, the task will succeed, but if errors exceed 100 before the task is completed, the entire task will stop (fail).​
    tip​
    The next step is allowed to proceed only when the actual number of failures across all batches of the task is less than or equal to the maximum number of errors you specify.​
    • Percent: Applicable to scenarios where the impact of errors on the entire task needs attention. Value range: 0-100%.​
    • If the maximum error percent is set to 0%, no errors are allowed. That is, if an error occurs even once while performing a task, the entire task will stop (fail).​
    • If the maximum error percent is set to 100%, the task will succeed regardless of the number of errors.​
    tip​
    The next step is allowed to proceed only when the actual failure rate (percentage of failed instances) across all batches of the task is less than or equal to the maximum error rate (percentage) you specify.​
    Error quantity: 1​
    ​
    Relevant Information​
    ​
    ​
    Project​
    You can add the cloud assistant to the project and manage it in the project dimension, which helps maintain resource independence and data security. For more information about projects, see Project management.​
    default​
    Tag​
    A tag is a key-value pair used to identify resources. Tags help you categorize resources based on different dimensions, such as purpose, owner, or environment. This allows you to easily search and aggregate your resources. For more information about tags, see Tag management.​
    Key1:Value1​
    ​
  1. Click "Create" to complete the actions.​
  1. After you confirm that the configuration information is correct, click the "Confirm" button to complete the operation.​
The selected task is executed on the selected EIPs, which has a wide-ranging impact. Confirm that all information is correct before you submit the request.​
Subsequent steps​
  • After the task is created, the system automatically redirects to the temporary bandwidth upgrade tasks page and starts executing the task according to the specified execution method and execution time.​
  • After a task is created, the bills related to the task are automatically settled by using the subscription billing method. You can go to the Billing center to view the bills. For more information, see Subscription billing method.​
Last updated: 2026.06.18 17:48:26