Amazon Relational Database Service
User Guide (API Version 2014-10-31)

DB Instance Status

The status of a DB instance indicates the health of the instance. You can view the status of a DB instance by using the RDS console, the AWS CLI command describe-db-instances, or the API action DescribeDBInstances.


Amazon RDS also uses another status called maintenance status, which is shown in the Maintenance column of the Amazon RDS console. This value indicates the status of any maintenance patches that need to be applied to a DB instance. Maintenance status is independent of DB instance status. For more information on maintenance status, see Updating the Operating System for a DB Instance or DB Cluster.

DB Instance Status Description


The instance is healthy and available.


The instance is currently being backed up.


Enhanced Monitoring is being enabled or disabled for this instance.


The instance is being created. The instance is inaccessible while it is being created.


The instance is being deleted.


The instance has failed and Amazon RDS was unable to recover it.  Perform a point-in-time restore to the latest restorable time of the instance to recover the data.


The KMS key used to encrypt or decrypt the DB instance could not be accessed.


The supplied CloudHSM Classic user name or password is incorrect. Please update the CloudHSM Classic credentials for the DB instance.


Amazon RDS is attempting to perform a recovery action on an instance but is unable to do so because the VPC is in a state that is preventing the action from being completed.  This status can occur if, for example, all available IP addresses in a subnet were in use and Amazon RDS was unable to get an IP address for the DB instance.


Amazon RDS attempted to apply an option group change but was unable to do so, and Amazon RDS was unable to roll back to the previous option group state. Consult the Recent Events list for the DB instance for more information. This status can occur if, for example, the option group contains an option such as TDE and the DB instance does not contain encrypted information.


Amazon RDS was unable to start up the DB instance because the parameters specified in the instance's DB parameter group were not compatible. Revert the parameter changes or make them compatible with the instance to regain access to your instance. Consult the Recent Events list for the DB instance for more information about the incompatible parameters.


Amazon RDS is unable to do a point-in-time restore. Common causes for this status include using temp tables, using MyISAM tables with MySQL, or using Aria tables with MariaDB.


Amazon RDS is applying a maintenance update to the DB instance. This status is used for instance-level maintenance that RDS schedules well in advance. We're evaluating ways to expose additional maintenance actions to customers through this status.


The instance is being modified because of a customer request to modify the instance.


The instance is being rebooted because of a customer request or an Amazon RDS process that requires the rebooting of the instance.


The instance is being renamed because of a customer request to rename it.


The master credentials for the instance are being reset because of a customer request to reset them.


The DB instance encountered an error attempting to restore to a point-in-time or from a snapshot.


The DB instance is starting.


The DB instance is being stopped.


The DB instance is stopped.


The instance has reached its storage capacity allocation. This is a critical status and should be remedied immediately; you should scale up your storage by modifying the DB instance. Set CloudWatch alarms to warn you when storage space is getting low so you don't run into this situation.


Your DB instance is being modified to change the storage size or type. The DB instance is fully operational, but while the status of your DB instance is storage-optimization, you can't request any changes to the storage of your DB instance. The storage optimization process is usually short, but can sometimes take up to and even beyond 24 hours.


The database engine version is being upgraded.