Viewing instance status - Amazon Relational Database Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Viewing instance status

Using the Amazon RDS console, you can quickly access the status of your DB instance.

Viewing Amazon RDS DB instance status

The status of a DB instance indicates the health of the DB instance. You can use the following procedures to view the DB instance status in the Amazon RDS console, the Amazon CLI command, or the API operation.

Note

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 about maintenance status, see Applying updates for a DB instance.

Find the possible status values for DB instances in the following table. This table also shows whether you will be billed for the DB instance and storage, billed only for storage, or not billed. For all DB instance statuses, you are always billed for backup usage.

DB instance status Billed Description

Available

Billed

The DB instance is healthy and available.

Backing-up

Billed

The DB instance is currently being backed up.

Configuring-enhanced-monitoring

Billed

Enhanced Monitoring is being enabled or disabled for this DB instance.

Configuring-iam-database-auth

Billed

Amazon Identity and Access Management (IAM) database authentication is being enabled or disabled for this DB instance.

Configuring-log-exports

Billed

Publishing log files to Amazon CloudWatch Logs is being enabled or disabled for this DB instance.

Converting-to-vpc

Billed

The DB instance is being converted from a DB instance that is not in an Amazon Virtual Private Cloud (Amazon VPC) to a DB instance that is in an Amazon VPC.

Creating

Not billed

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

Delete-precheck

Not billed

Amazon RDS is validating that read replicas are healthy and are safe to delete.

Deleting

Not billed

The DB instance is being deleted.

Failed

Not billed

The DB instance has failed and Amazon RDS can't recover it. Perform a point-in-time restore to the latest restorable time of the DB instance to recover the data.

Inaccessible-encryption-credentials

Not billed

The Amazon KMS key used to encrypt or decrypt the DB instance can't be accessed or recovered.

Inaccessible-encryption-credentials-recoverable

Billed for storage

The KMS key used to encrypt or decrypt the DB instance can't be accessed. However, if the KMS key is active, restarting the DB instance can recover it.

For more information, see Encrypting a DB instance.

Incompatible-network

Not billed

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

Incompatible-option-group

Billed

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

Incompatible-parameters

Billed

Amazon RDS can't start the DB instance because the parameters specified in the DB instance's DB parameter group aren't compatible with the DB instance. Revert the parameter changes or make them compatible with the DB instance to regain access to your DB instance. For more information about the incompatible parameters, check the Recent Events list for the DB instance.

Incompatible-restore

Not billed

Amazon RDS can't 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.

Insufficient-capacity Not billed

Amazon RDS can’t create your instance because sufficient capacity isn’t currently available. To create your DB instance in the same AZ with the same instance type, delete your DB instance, wait a few hours, and try to create again. Alternatively, create a new instance using a different instance class or AZ.

Maintenance

Billed

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.

Modifying

Billed

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

Moving-to-vpc

Billed

The DB instance is being moved to a new Amazon Virtual Private Cloud (Amazon VPC).

Rebooting

Billed

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

Resetting-master-credentials

Billed

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

Renaming

Billed

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

Restore-error

Billed

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

Starting

Billed for storage

The DB instance is starting.

Stopped

Billed for storage

The DB instance is stopped.

Stopping

Billed for storage

The DB instance is being stopped.

Storage-config-upgrade

Billed

The storage file system configuration of the DB instance is being upgraded. This status only applies to green databases within a blue/green deployment, or to DB instance read replicas.

Storage-full

Billed

The DB instance has reached its storage capacity allocation. This is a critical status, and we recommend that you fix this issue immediately. To do so, scale up your storage by modifying the DB instance. To avoid this situation, set Amazon CloudWatch alarms to warn you when storage space is getting low.

Storage-optimization

Billed

Amazon RDS is optimizing the storage of your DB instance. The DB instance is fully operational. The storage optimization process is usually short, but can sometimes take up to and even beyond 24 hours.

Upgrading

Billed

The database engine version is being upgraded.

To view the status of a DB instance
  1. Sign in to the Amazon Web Services Management Console and open the Amazon RDS console at https://console.amazonaws.cn/rds/.

  2. In the navigation pane, choose Databases.

    The Databases page appears with the list of DB instances. For each DB instance , the status value is displayed.

    View the status of a DB instance

To view DB instance and its status information by using the Amazon CLI, use the describe-db-instances command. For example, the following Amazon CLI command lists all the DB instances information .

aws rds describe-db-instances

To view a specific DB instance and its status, call the describe-db-instances command with the following option:

  • DBInstanceIdentifier – The name of the DB instance.

aws rds describe-db-instances --db-instance-identifier mydbinstance

To view just the status of all the DB instances, use the following query in Amazon CLI.

aws rds describe-db-instances --query 'DBInstances[*].[DBInstanceIdentifier,DBInstanceStatus]' --output table

To view the status of the DB instance using the Amazon RDS API, call the DescribeDBInstances operation.