DocsICP FilingConsole
官方文档
首页

Recurring temporary bandwidth upgrade for subscription instances

更新时间：
复制 MD 格式
产品详情
我的收藏

You can use Operation Orchestration Service (OOS) to periodically and temporarily increase the fixed public bandwidth of subscription instances. For example, you can schedule a temporary upgrade for any time window each day. By specifying the start time, duration, and end time for the task, you can automate recurring bandwidth adjustments.

Use cases

  • Sudden traffic spikes: Some services, such as online education, live streaming, and e-commerce promotions, experience predictable traffic patterns with peak access during specific times, such as daily rush hours, weekends, or holidays. During these periods, you may need to temporarily increase public bandwidth to handle sudden surges in traffic.

  • Data backup and synchronization: If your business runs periodic backup or sync jobs that require high network bandwidth, temporarily increasing bandwidth during the backup window speeds up transfers and helps ensure the job finishes on time without affecting normal workloads.

  • Scheduled data processing: Some applications process large volumes of data at specific times. A temporary bandwidth upgrade can improve processing efficiency.

Important

Prerequisites

Before you begin, make sure that your instance meets the following requirements:

  • The instance is a subscription instance.

  • The instance uses a fixed public IP address, and the billing method for its public bandwidth is pay-by-fixed-bandwidth.

  • The region where the instance is located supports CloudOps Orchestration Service. For the regions supported by CloudOps Orchestration Service, see Usage limits.

  • You have granted RAM permissions to OOS. For more information, see Set a RAM role for OOS and grant permissions.

    Required permissions for the RAM role

    {
    "Version": "1",
    "Statement": [
        {
            "Action": "oos:*",
            "Resource": "*",
            "Effect": "Allow"
        },
        {
            "Action": "ram:PassRole",
            "Resource": "*",
            "Effect": "Allow",
            "Condition": {
                "StringEquals": {
                    "acs:Service": "oos.aliyuncs.com"
                }
            }
        },
        {
            "Action": [
                "ecs:DescribeInstances",
                "ecs:ModifyInstanceNetworkSpec"
            ],
            "Resource": "*",
            "Effect": "Allow"
        }
    ]
}

Billing

Temporary bandwidth upgrade tasks are charged automatically when they are triggered. Make sure your account has a sufficient balance to prevent task failures due to an insufficient balance. To top up your account, see Online recharge.

  • During the temporary upgrade period, you can upgrade or downgrade the fixed bandwidth or change the public bandwidth billing method from pay-by-fixed-bandwidth to pay-by-traffic.

    • If you permanently upgrade the fixed bandwidth, you are charged for the permanent upgrade in addition to the temporary upgrade fee.

    • If you downgrade the fixed bandwidth or change the billing method to pay-by-traffic, the temporary upgrade is canceled and refunded.

  • A temporary bandwidth upgrade does not require an instance restart and takes effect after a successful payment. After the upgrade takes effect, you cannot cancel it or adjust the upgrade schedule.

To view the estimated cost, go to the Temporary Bandwidth Upgrade task page and check the reference price for a single cycle in the lower-right corner.

For example, the price might be displayed as ¥ 2220.

Notes

  • A temporary bandwidth upgrade does not change the existing public or private IP addresses of the instance.

  • If you upgrade the public bandwidth of an instance from 0 Mbps to a non-zero value, a public IP address is automatically assigned. When the upgrade period ends and the bandwidth returns to 0 Mbps, the public IP address is immediately released.

  • A temporary bandwidth upgrade does not increase the base public bandwidth of the instance. If you renew the instance before the upgrade period ends, the renewal is based on the original base public bandwidth.

    The base public bandwidth is the amount you purchased when creating the instance or during a subsequent configuration upgrade.

Limitations

  • Feature limitations

    • You can only temporarily upgrade public bandwidth. Temporary downgrades are not supported.

    • Temporary bandwidth upgrades are not supported for BGP (Multi-ISP) Pro lines in the China (Hong Kong) region.

  • Bandwidth limit

    The maximum bandwidth is 200 Mbps for the pay-by-bandwidth billing method.

  • Upgrade time limits

    • You can temporarily upgrade bandwidth only within the current billing cycle, and the end time of the bandwidth upgrade cannot be later than the instance's expiration date. If you have renewed the instance with a downgraded configuration in the current cycle, you must wait until the next billing cycle to perform a temporary upgrade.

    • The start time of a temporary bandwidth upgrade can be specified to the minute, but the end time must be on the hour. The interval between the start and end times must be at least 4 hours. For a longer upgrade duration, permanently upgrade the fixed bandwidth. For more information, see Modify the bandwidth of a subscription instance.

  • Limitations during the upgrade period

    • After a temporary bandwidth upgrade starts, you cannot change the billing method of a subscription instance or its subscription system disk to pay-as-you-go. However, you can change the billing method of a subscription data disk to pay-as-you-go.

    • To perform another temporary upgrade while one is active, the new bandwidth must exceed the current upgraded bandwidth.

Procedure

  1. Log on to the Operation Orchestration Service (OOS) console.

  2. In the left-side navigation pane, choose Automated Task > Common O&M Tasks > Temporary Bandwidth Upgrade, and then click Create.

  3. Configure the parameters for the temporary bandwidth upgrade task.

    Parameter

    Description

    Resource Types

    Select ECS Instance.

    Execution Frequency

    Select Daily, Specified Time, or Specified Cron Expression based on your needs. For Specified Time, you can select one or more days from Monday to Sunday. For more information about cron expressions, see cron expressions.

    Bandwidth Upgrade Start Time

    OOS creates a bandwidth upgrade order at the specified start time.

    Important

    A slight delay is introduced before the bandwidth upgrade takes effect. This prevents order failures caused by API call latency and improves the success rate.

    Execution Duration (Hours)

    The duration of the bandwidth upgrade must be at least 4 hours. The end time is calculated by adding the duration to the start time.

    The end time must be on the hour. For example, if the start time is 14:05 and the duration is 4 hours, the end time is 19:00.

    Maximum Internet Outbound Bandwidth (Mbit/s)

    Set the target bandwidth for the temporary upgrade. The value can range from 0 to 200 Mbps.

    Important

    OOS does not validate the bandwidth value. If the value you set exceeds the limit for the ECS instance type, the temporary bandwidth upgrade may fail.

    End Time

    Select the date and time when the task should end.

    Permissions

    Select the service-linked role or a specified RAM role.

  4. Click Select Instances to expand the configuration, and then select the instances whose bandwidth you want to upgrade.

  5. (Optional) Configure advanced options.

    • Rate Control: When upgrading bandwidth for a large number of instances, you can use Concurrency-based Control or Batch-based Control. Set the Concurrency or Batch Array to control how many instances are upgraded simultaneously. For more information about these parameters, see Loop and rate control.

    • Error Threshold: When upgrading bandwidth for multiple instances, you can specify the number of allowed failures. This setting stops the task if the number of errors exceeds the specified limit. The default value is 0, which means the task stops after a single failure. For more information, see Error control (MaxErrors).

  6. (Optional) Configure execution parameters.

    • Description, Execution Tags: Add a description or tags to the task for easier management and identification.

    • Executed Resource Group: Select a resource group for the execution.

    • Save as Template: Select this option if you want to save the configuration of this temporary bandwidth upgrade task as a custom OOS template. You can use this template to run the same upgrade task again in the future.

  7. Confirm the estimated cost for a single cycle, and then click Create.

    Important

    This price is a reference for a single cycle only. The actual charges are based on the final order.

  8. In the Parameter Confirmation dialog box, confirm the Basic Information and Targets, and then click OK.

    Also, confirm the Balance Confirmation (ensure your account balance is sufficient or your credit card can be charged) and the Task Information (including parameters like maximum outbound public bandwidth, execution cycle, bandwidth upgrade duration, task end time, and concurrency rate).

Manage temporary bandwidth upgrade tasks

After you create a temporary bandwidth upgrade task, an execution is generated on the Temporary Bandwidth Upgrade page of the CloudOps Orchestration Service (OOS) console. You can view the task details, modify the task, or cancel the task as needed.

  • View task details: Click Details to view the Basic Information, Task Information, and Execution Progress.

  • Modify task: If the temporary bandwidth upgrade task no longer meets your needs, for example, if you need to change the execution schedule or bandwidth value, click Modify to reconfigure the execution parameters.

    Important

    You cannot cancel or change the schedule of an active upgrade. The modified task will be billed and executed according to the new cycle.

  • Cancel task: If you no longer need the temporary bandwidth upgrade, you can click Cancel to cancel the task.

Previous：Temporarily upgrade fixed public bandwidth for subscription instancesNext：Modify the bandwidth of an EIP