Configuring Storage Autoscaling
Scenarios
With storage autoscaling enabled, when RDS detects that you are running out of database space, it automatically scales up your storage.
Autoscaling up the storage of a read replica does not affect that of the primary DB instance. Therefore, you can separately autoscale read replicas to meet service requirements. New storage space of read replicas after autoscaling up must be greater than or equal to that of the primary DB instance.
You can enable storage autoscaling in either of the following ways:
- Enable this function when you create a DB instance.
- Enable this function after you create a DB instance. See the operations provided in this section.
Constraints
- The maximum allowed storage is 4,000 GB.
- For a primary/standby DB instance, autoscaling the storage for the primary node will also autoscale the storage for the standby node.
- Storage autoscaling is unavailable when the DB instance is in any of the following statuses: changing instance class, upgrading a minor version, migrating the standby DB instance, and rebooting.
Procedure
- Log in to the management console.
- Click in the upper left corner of the page and choose Databases > Relational Database Service.
- On the Instances page, click the target DB instance or read replica (click in front of a DB instance to locate the read replica).
- In the Storage Space area, click Configure Autoscaling.
- In the displayed dialog box, set the following parameters:
Table 1 Parameter description Parameter
Description
Enable autoscaling
If you select this option, autoscaling is enabled.
Trigger If Available Storage Drops To
If the available storage drops to a specified threshold or 10 GB, autoscaling is triggered.
Autoscaling Limit
The default value range is from 40 GB to 4,000 GB. The limit must be no less than the storage of the DB instance.
- Click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.