Use CloudOps Orchestration Service (OOS) to automatically upgrade the bandwidth of your Tair or Redis instances at scheduled times and revert to the default bandwidth when the high-traffic window ends — keeping costs in check without manual intervention.
Choose a bandwidth upgrade method
Three methods are available. Pick the one that matches how predictable your traffic is:
| Method | How it's triggered | Best for |
|---|---|---|
| Scheduled upgrade (this guide) | Preset date and time; one-time or recurring | Fixed traffic peaks you can predict in advance — promotions, nightly batch jobs, daily sync windows |
| Bandwidth elastic scaling | Automatically triggered and recovered based on bandwidth utilization | Unpredictable surges and dynamic workloads |
| Manual bandwidth adjustment | Manual operation | One-off changes, such as long-term instance bandwidth adjustments |
Billing
You are charged hourly based on the amount of additional bandwidth and the duration of use. Pricing varies by region. The default bandwidth included with your instance type is not charged — only the extra bandwidth you purchase. See Billable items for regional pricing details.
Prerequisites
Before you begin, ensure that you have:
-
A RAM role that grants OOS access to ApsaraDB for Tair (Redis OSS-compatible). See Create a RAM role for OOS and grant permissions
The RAM role needs at minimum the following two permissions:
{
"Version": "1",
"Statement": [
{
"Effect": "Allow",
"Action": [
"kvstore:DescribeInstances",
"kvstore:EnableAdditionalBandwidth"
],
"Resource": "*"
}
]
}Alternatively, grant the AliyunKvstoreFullAccess system policy to the role if you prefer broader access to all ApsaraDB for Tair (Redis OSS-compatible) resources.
Schedule a bandwidth upgrade
-
Go to the OOS console.
-
In the left navigation pane, choose Automated Task > Common O&M Tasks.
-
Select Temporary Bandwidth Upgrade and click Create.
-
Configure the O&M task with the settings below. For parameters not covered here, see CloudOps Orchestration Service.
Select resource type
Select ApsaraDB For Redis Instance.
Set parameters
-
Set Scheduled Task Type. Select Executed Periodically to run on a recurring schedule, or choose a one-time option. In the example below, the task runs daily at 11:00 with a defined cycle start and end date.
-
Set Additional Bandwidth (in MB/s). How the bandwidth is distributed depends on your instance architecture:
Architecture Behavior Standard Bandwidth is added to the single node. No data shard ID required. Cluster or read/write splitting Default data shard ID is ALL — the specified bandwidth is added to each shard or node. Total additional bandwidth = Additional Bandwidth x number of shards (nodes). To add different bandwidth amounts to specific shards, enter the shard IDs separated by commas (,) and add a corresponding Bandwidth Arrays entry for each shard ID.
-
Set Duration Of Bandwidth Upgrade (in hours). The minimum duration is 1 hour. After the duration elapses, bandwidth reverts to the default configuration automatically.
-
Under Permissions, select the RAM role you created in the Prerequisites section.
Select instances
Select the region where your instance resides and select the instance.
Advanced options
Use the default values for both tabs.
Execution settings
Use the default values for both tabs.
-
-
Click Create, then click OK in the confirmation dialog.
Verify the task
When Execution Status shows Active, OOS executes the task at the times defined in Timer Trigger Configure.
On the task details page, you can review:
-
Historical execution tasks
-
Upcoming execution tasks
-
Execution Logs