Elastic scaling temporarily upgrades the CPU, memory, or connection limits of an ApsaraDB MyBase instance to handle predictable traffic spikes—such as promotional events like 618 and Double 11. After the deadline you set, ApsaraDB MyBase automatically restores the instance to its original specifications without any manual intervention.
Example: An e-commerce platform handles 100,000 visits per day on a 2-core, 16 GB instance. During Double 11, traffic reaches 1,000,000 visits. Configuring elastic scaling to upgrade the instance to 8 cores and 64 GB memory keeps the database stable through the spike—without a manual resize or service interruption.
Before you begin
An ApsaraDB MyBase dedicated cluster with at least one instance
Access to the ApsaraDB MyBase console
Usage notes
Elastic scaling is temporary. After the deadline, the instance automatically reverts to its original specifications. If you need a permanent resize, modify the instance class instead.
Available parameters vary by database engine. Not all resource types (CPU, memory, connections) are available for every engine. Check the Elastic Configuration panel in the console to see which options apply to your instance before planning your upgrade.
Configure elastic scaling
Log on to the ApsaraDB MyBase console.
In the top navigation bar, select the region where your instance is deployed.
In the left-side navigation pane, click Clusters. Find the dedicated cluster that contains your instance and click Details in the Actions column.
In the left-side navigation pane, click Instances. Find the instance you want to scale and choose More > Set Instance Scaling in the Actions column.
In the Elastic Configuration panel, set the following parameters.
The parameters available in the Elastic Configuration panel depend on the database engine of your instance.
Parameter Description Instance information Displays the instance ID, current CPU, memory, and maximum connections. Use these baseline values to decide how much to upgrade. Resource type The resource to upgrade: CPU, Memory, or Connections. Choose the resource that is most likely to become the bottleneck during your peak period. If you are unsure, start with CPU and memory. Set up resources The target quantity for the selected resource type after the upgrade. Base this on your expected peak load. Deadline of temporary dispatching The time when the instance reverts to its original specifications. Set this to after your peak period ends, with enough buffer for traffic to taper off. Restore to specification original configuration Select the checkbox next to a resource to cancel its upgrade. Leave this blank to let the upgrade run until the deadline. 
Click OK.
Verify the configuration
After clicking OK, confirm that the scaling took effect:
Click the instance ID.
On the Basic Information page, go to the Instance Resources section.
Confirm that the resource values match the upgraded specifications you configured.
If the values match, the elastic scaling policy is active and the instance is running on the upgraded specifications until the deadline.