Why is an Amazon RDS DB instance stuck in the modifying state when I try to increase the allocated storage?
Last updated: 2019-12-11
I want to increase the allocated storage for an Amazon Relational Database Service (Amazon RDS) DB instance, but the operation is stuck in the modifying state.
By design, storage scaling operations for an Amazon RDS DB instance have a minimal impact on ongoing database operations. For this reason, the operations are long running and can take time to complete. The following factors can affect the time required to increase the allocated storage of an RDS DB instance:
- If you move between storage media types, such as from magnetic to SSD or PIOPS, downtime is required at the beginning of the process to enable or disable any EBS optimizations on the destination media type. If a DB instance uses a single Availability Zone, the downtime can be several minutes. If a DB instance uses multiple Availability Zones, less downtime is required.
- If you have large workload running at the time of the operation, the operation can take longer to complete because the time required to complete a storage operation is proportional to the running workload. It's a best practice to schedule storage increase operations outside peak hours to reduce the time required to complete the operation.
- If you have high-load conditions, create a read replica for an RDS DB instance, perform storage scaling operations on the read replica, and then promote the read replica DB instance to the primary DB instance.
After a storage modification has started, the operation can't be canceled, and the DB instance status is modifying until the Amazon Elastic Block Store (Amazon EBS) operations are complete. You can restore a DB instance to a specified time or restore from a DB snapshot to create a new DB instance with the original storage configuration. A DB instance that's restored won't be in the modifying status.