This topic describes how to use the temporary bandwidth upgrade feature of OOS (OOS) to temporarily upgrade the bandwidth. You can schedule the upgrade to take effect in a specific period every day or on specific days. You can specify the start time and days by using a CRON expression.OOS
Limits
The temporary bandwidth upgrade feature applies only to Elastic Compute Service (ECS) instances, Tair (Redis OSS-compatible) instances, and Elastic IP Address (EIP) instances.
The temporary bandwidth upgrade feature has the following limits on ECS instances:
Only the public bandwidth of ECS instances that use the pay-by-bandwidth method can be temporarily upgraded. ECS instances that use the pay-by-traffic method do not support the temporary bandwidth upgrade feature.
The public bandwidth of ECS instances that reside in the classic network cannot be upgraded from 0 Mbit/s. To upgrade the bandwidth, you must restart ECS instances in the ECS console or by using ECS API operations for the changes to take effect.
ECS instances must use the subscription billing method. ECS instances whose billing method is pay-as-you-go do not support the temporary bandwidth upgrade feature.
Procedure
Go to the OOS>Common O&M Tasks>Temporary Bandwidth Upgrade page and click Create.
In the Resource Type section of the Create Temporary Update Task for Bandwidth page, select a resource type, such as ECS, ApsaraDB for Redis, or EIP.
In the Parameter Settings section, set the parameters.
ECS
You must specify Execution Cycle, Start Time, Duration of Bandwidth Upgrade (Hours), End Time, Maximum Internet Outbound Bandwidth (Mbit/s), and Permissions.
ImportantValid values for Maximum Internet Outbound Bandwidth: 0 to 200. OOS does not verify this parameter. If the bandwidth that you specified exceeds the limits of ECS instances, the temporary bandwidth upgrade may fail. In this case, you can submit a ticket in the ECS console to increase the bandwidth limit or specify a valid bandwidth value.
Take note of the following parameters:
Duration of Bandwidth Upgrade (Hours): The duration cannot be less than 4 hours. The end time must be on the hour and the duration cannot be less than 4 hours.
Valid values for Maximum Internet Outbound Bandwidth (Mbit/s): 0 to 200. OOS does not verify this parameter. If the bandwidth that you specified exceeds the limits of ECS instances, the temporary bandwidth upgrade may fail. In this case, you can submit a ticket in the ECS console to increase the bandwidth limit or specify a valid bandwidth value.
Permissions: You can select Default Associated Role or Specify RAM Role and Use Permissions Granted to This Role. If you select a RAM role, you must specify the RAM role assumed by OOS. In this example, OOSServiceRole is selected.
NoteIf no RAM role is available, see Grant permissions to OOS. If you know how to create a RAM role for OOS, you can directly click Manual Authorization. For more information about the required permission policy, see the following JSON script:
ApsaraDB for Redis
You must specify Scheduled Task Type, Additional Bandwidth (Mbit/s), and Duration of Bandwidth Upgrade.
Take note of the following parameters:
Additional Bandwidth (Mbit/s): You can specify up to six times the default bandwidth. Maximum value: 192 Mbit/s. For example, if the default bandwidth is 10 Mbit /s, valid values are 0 to 60 Mbit/s.
Permissions: You can select Default Associated Role or Specify RAM Role and Use Permissions Granted to This Role. If you select a RAM role, you must specify the RAM role assumed by OOS. In this example, OOSServiceRole is selected.
NoteIf no RAM role is available, see Grant permissions to OOS. If you know how to create a RAM role for OOS, you can directly click Manual Authorization. For more information about the required permission policy, see the following JSON script:
EIP
You must specify Scheduled Task Type, Bandwidth (Mbit/s), and Duration of Bandwidth Upgrade.
Take note of the following parameters:
Bandwidth (Mbit/s): Specify the maximum bandwidth of the EIP. Valid values: 1 to 500. You are charged on a pay-by-bandwidth basis.
Permissions: You can select Default Associated Role or Specify RAM Role and Use Permissions Granted to This Role. If you select a RAM role, you must specify the RAM role assumed by OOS. In this example, OOSServiceRole is selected.
NoteIf no RAM role is available, see Grant permissions to OOS. If you know how to create a RAM role for OOS, you can directly click Manual Authorization. For more information about the required permission policy, see the following JSON script:
In the Select Instances section, select an instance.
The method of selecting instances varies with resource types. For example, you can manually select instances, specify instance tags, and specify instance resource groups.
(Optional). Set the parameters in the Advanced and Execution Settings sections.
In the Advanced section, specify Rate control type and Error Threshold to control the execution of the task.
NoteFor more information about concurrency control, see Loop.
In the Execution Settings section, select a tag, a resource group, execution mode, and whether to save the task as a template for later use.
On the Temporary Bandwidth Upgrade page, click Create.
After the task is created, you can click the task ID in the Execution ID column to view the details.