Docs

Database Workshop

AutoOps

Storage space expansion management

Database Workshop (DBW) provides the automatic scaling up feature, which can help you respond quickly and perform scaling up operations when your business grows rapidly, so as to ensure that your system can run stably and meet the ever-increasing business needs. This article describes how to enable, view, modify, and close automatic scaling up rules.

Prerequisites

An RDS for PostgreSQL instance has been created. For detailed steps, see Creating an instance.

tip

This feature is not supported when the instance status is creating, recovering, importing, error, deleted, terminated, waiting for payment, billing suspension in progress, billing restoring, billing reclaiming or reconstructing.

If the target instance has security control enabled, you need to apply for operation and maintenance read-only or read/write permissions for the current account. For more information, refer to Enabling instance security control (RDS for PostgreSQL), and Applying for operation permissions (RDS for PostgreSQL).

Precautions

Currently, only automatic scaling up of instance storage space is supported. After a rule is triggered, automatic scaling up is usually completed in about 10 minutes. After automatic scaling up is complete, DBW will not perform automatic scaling down according to business scenarios. Therefore, if scaling down is needed, you must perform the operation manually. For details, see Change configuration.

Each expansion step is Min (maximum available storage space, twice the current storage space); if the instance's current storage space is 500 GB and the maximum available storage space is 800 GB, then the expansion will be to 800 GB.

Automatic disk expansion cannot guarantee successful expansion in all scenarios due to physical limitations of local SSDs, insufficient host storage space, insufficient account balance, and other reasons. If expansion fails, the system will suspend the automatic scaling up task.

Performing configuration change operations on the instance may prevent the instance from performing automatic scaling up. For example, in an automatic capacity expansion configuration, the maximum capacity can be expanded to 1500 GB. However, if you change the storage space of the instance to 1600 GB, the automatic capacity expansion rule will not be triggered. You can modify the automatic expansion rules to trigger them normally; if you do not need this function, you can disable it yourself.

If the automatic expansion fails, the system will suspend subsequent expansion tasks until the cause of the failure is detected and resolved.

During automatic scaling up, most operations related to databases, accounts, and networks cannot be performed.

Automatic scaling up does not cause changes to the instance ID and connection address.

RDS for PostgreSQL instances now support storage space exceeding 3000 GB. However, this capacity level is currently a whitelisted feature. To use larger storage specifications, Submit a ticket to contact technical support.

If your instance has automatic scaling up enabled, after applying for this feature, be sure to manually increase the upper limit of the scaling rule. Otherwise, the rule's upper limit will remain at the default 3000 GB, and the instance will be unable to scale to the newly requested storage space.

Before using the AutoOps function, make sure that there is sufficient balance in the account to support changing the instance configuration. For more billing information about the product, see Billing overview.

Enable automatic scaling up rules

Log on to the DBW console.

On the top menu bar, select the project and region.

On the left navigation bar, select Operation and maintenance management > Observation and diagnosis.

On the Observation and diagnosis page, click AutoOps.

In the upper-right corner of the page, locate the drop-down list and select the target database type - RDS for PostgreSQL.

In the upper-right corner of the page, locate the drop-down list and select the target instance.

On the AutoOps tab, click Configure AutoOps rules under Storage expansion.

On the Configure AutoOps rules panel, configure the following parameters.

Parameter	Description
Automatic expansion	Select Enable auto scaling to enable the automatic scaling up function.
Scaling up type	Currently, only selecting Storage space is supported, and modification is not supported.
Available storage space	Available storage space percentage threshold: Set the available storage space percentage threshold as required. The unit is percentage, and the value range is 10% ~ 50%. The scale-up upper limit configuration range is 20 GB ~ 12000 GB. Available storage space threshold: Set the maximum storage space threshold for scaling up the instance as needed. When the available storage space percentage of the instance is less than or equal to the set threshold, the instance will start scaling up. The lower limit of the instance storage space threshold is the instance's current used storage space + 20 GB, and the upper limit is the upper limit of the storage space value range corresponding to the instance primary node specification, in GB. For more information about the range of storage space values that can be selected for different specifications, see Product specifications. tip Storage capacity over 3000 GB is currently an allowlisted feature, available only in the China (Beijing), China (Shanghai), and China (Guangzhou) regions. To use it, submit a ticket to contact technical support to apply for usage. For example, if you set the threshold for the available storage space percentage to 50%, and the available instance storage space to 600 GB, then when the available storage space percentage of the instance is less than or equal to 50%, the instance will start scaling up and can be changed to a maximum of 600 GB.

Click OK.

View the triggered scaling up event

tip

You can view scaling up events within the last 30 days at most.

Log on to the DBW console.

On the top menu bar, select the project and region.

On the left navigation bar, select Operation and maintenance management > Observation and diagnosis.

On the Observation and diagnosis page, click AutoOps.

In the upper-right corner of the page, locate the drop-down list and select the target database type - RDS for PostgreSQL.

In the upper-right corner of the page, locate the drop-down list and select the target instance.

On the AutoOps tab, set the time range for the query events as needed. The target events to view include Event ID, Event status, Trigger value, Trigger condition, Rule type, Before/After adjustment, Trigger time and Last update time.

tip

Before/After adjustment represents the storage space before and after triggering automatic scaling up.

Modify auto scaling rules

Log on to the DBW console.

On the top menu bar, select the project and region.

On the left navigation bar, select Operation and maintenance management > Observation and diagnosis.

On the Observation and diagnosis page, click AutoOps.

In the upper-right corner of the page, locate the drop-down list and select the target database type - RDS for PostgreSQL.

In the upper-right corner of the page, locate the drop-down list and select the target instance.

On the AutoOps tab, click Configure AutoOps rules under Storage expansion.

On the Configure AutoOps rules panel, configure the following parameters.

Parameter	Description
Automatic expansion	Select Enable auto scaling to enable the automatic scaling up function.
Scaling up type	Currently, only selecting Storage space is supported, and modification is not supported.
Available storage space	Available storage space percentage threshold: Set the available storage space percentage threshold as required. The unit is percentage, and the value range is 10% ~ 50%. The scale-up upper limit configuration range is 20 GB ~ 12000 GB. Available storage space threshold: Set the maximum storage space threshold for scaling up the instance as needed. When the available storage space percentage of the instance is less than or equal to the set threshold, the instance will start scaling up. The lower limit of the instance storage space threshold is the instance's current used storage space + 20 GB, and the upper limit is the upper limit of the storage space value range corresponding to the instance primary node specification, in GB. For more information about the range of storage space values that can be selected for different specifications, see Product specifications. tip For example, if you set the threshold for the available storage space percentage to 50%, and the available instance storage space to 600 GB, then when the available storage space percentage of the instance is less than or equal to 50%, the instance will start scaling up and can be changed to a maximum of 600 GB. Storage capacity over 3000 GB is currently an allowlisted feature, available only in the China (Beijing), China (Shanghai), and China (Guangzhou) regions. To use it, submit a ticket to contact technical support to apply for usage.

Click OK.

Disable auto scaling rules

Log on to the DBW console.

On the top menu bar, select the project and region.

On the left navigation bar, select Operation and maintenance management > Observation and diagnosis.

On the Observation and diagnosis page, click AutoOps.

In the upper-right corner of the page, locate the drop-down list and select the target database type - RDS for PostgreSQL.

In the upper-right corner of the page, locate the drop-down list and select the target instance.

On the AutoOps tab, click Configure AutoOps rules under Storage expansion.

In the Configure AutoOps rules control panel, clear Enable auto scaling.

Click OK.

FAQs

Error	reason	Solution
Pre-check failed: Exceeds the maximum storage space that you configured, and the system will not be able to complete the automatic scaling up normally.	The instance specifications are greater than the configured auto-scaling available storage space threshold.	You can adjust the available storage space threshold for automatic scaling up as appropriate. If there are any anomalies, relevant prompts will appear after you confirm the change. You can make corresponding modifications based on the specific prompts. For detailed operations, see Modifying scaling up rules.
Pre-check failed: The host where the node is located has insufficient storage space, and the system will not be able to complete automatic scaling up normally.	The disk does not meet the local scaling up rules.	We suggest that you change the storage space of the target instance. After the change is complete, the system will select a host with more remaining storage space. If the error persists, we suggest that you readjust the instance's storage space. For details, see Change configuration. tip After scaling the instance, you can check for any exceptions on the Auto Scaling page. If there are any exceptions, hover your mouse over the event status to view the specific cause of the error and make corrections based on the prompts. For detailed operations, see Viewing triggered scaling up event.
Pre-check failed: Insufficient account balance. The system will not be able to automatically scale up.	Insufficient account balance	You need to recharge the current account to ensure sufficient account resources. For detailed operations, see Recharge.
Pre-check failed: The expansion conditions are not met, and the system can not complete automatic scaling up normally.	The instance may be in the process of modifying.	If the instance status is not running or changing, the system will automatically record the expansion failure event during the automatic expansion process. If the instance is running, submit a ticket to contact technical staff for troubleshooting and identifying the specific issue.

Last updated: 2026.08.04 11:16:30