When attempting to increase the allocated storage for an Amazon RDS DB instance, the operation appears to be stuck in the modifying state.

Increasing the allocated storage of an Amazon RDS DB instance is designed to be low impact to the process to be completed with minimal impact to ongoing database operations. This operation is long running and therefore slow by design.

Some factors that affect the amount of time required to increase the allocated storage of an Amazon RDS DB instance include:

  • After a storage modification has started, it is not possible to cancel the operation. If you want to stop a running storage modification, you can use the rollback method to complete a point-in-time restore or a restore from snapshot to create a new instance with the original storage configuration.
  • When moving between storage media types, such as from magnetic to SSD or PIOPS, some downtime is required at the start of the process to enable or disable any EBS optimizations on the destination media type. This downtime can be several minutes when the RDS DB instance resides in a single availability zone; somewhat less downtime is required when the RDS DB instance uses multiple availability zones.
  • The rate at which storage scaling operations complete is inversely proportional to the current workload of the DB instance. You should schedule operations to increase allocated storage during non-peak hours to reduce the amount of time required to complete storage scaling.
  • Under very high load conditions, a possible option to consider is to create a read replica of the existing DB instance, perform storage scaling operations on the read replica, and then promote the read replica instance to the primary instance.

Amazon RDS, DB instance, modifying, stuck, hang, rds-modify-db-instance, ModifyDBInstance, AllocatedStorage, increase

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.