Amazon RDS event categories and event messages

DB cluster created.

failover

Cluster failover failed, check the health of your cluster instances and try again.

failover

Promoting previous primary again: name.

failover

Completed failover to DB instance: name.

failover

Started same AZ failover to DB instance: name.

failover

Started cross AZ failover to DB instance: name.

global failover

Global switchover to DB cluster name in Region name started.

This event is for a switchover operation (previously called "managed planned failover").

The process can be delayed because other operations are running on the DB cluster.

global failover

Old primary DB cluster name in Region name successfully shut down.

This event is for a switchover operation (previously called "managed planned failover").

The old primary instance in the global database isn't accepting writes. All volumes are synchronized.

global failover

Waiting for data synchronization across global cluster members. Current lags behind primary DB cluster: reason.

This event is for a switchover operation (previously called "managed planned failover").

A replication lag is occurring during the synchronization phase of the global database failover.

global failover

New primary DB cluster name in Region name was successfully promoted.

This event is for a switchover operation (previously called "managed planned failover").

The volume topology of the global database is reestablished with the new primary volume.

global failover

Global switchover to DB cluster name in Region name finished.

This event is for a switchover operation (previously called "managed planned failover").

The global database switchover is finished on the primary DB cluster. Replicas might take long to come online after the failover completes.

global failover

Global switchover to DB cluster name in Region name is cancelled.

This event is for a switchover operation (previously called "managed planned failover").

global failover

Global switchover to DB cluster name in Region name failed.

This event is for a switchover operation (previously called "managed planned failover").

global failover

Global failover to DB cluster name in Region name completed.

global failover

Global failover to DB cluster name in Region name failed.

global failover

Started resynchronizing members of DB cluster name in Region name after global failover.

global failover

Finished resynchronizing members of DB cluster name in Region name after global failover.

maintenance

Database cluster engine major version has been upgraded.

maintenance

Database cluster engine version upgrade started.

maintenance

Operating system upgrade requirement detected.

maintenance

Cluster operating system upgrade starting.

maintenance

Cluster operating system upgrade completed.

maintenance

Database cluster has been patched: source version version_number => new_version_number.

Renamed cluster from name to name.

availability

DB instance restarted.

availability

DB instance shutdown.

availability

Error restarting mysql: message.

An error has occurred while restarting MySQL.

availability

DB instance has reached the storage-full threshold, and the database has been shut down. You can increase the allocated storage to address this issue.

availability

Free storage capacity for DB instance name is low at percentage of the allocated storage [Allocated storage: amount, Free storage: amount]. The database will be shut down to prevent corruption if free storage is lower than amount. You can increase the allocated storage to address this issue.

backup

Backing up DB instance.

backup

Finished DB instance backup.

backup

We are unable to associate the option group name with the database instance name. Confirm that option group name is supported on your DB instance class and configuration. If so, verify all option group settings and retry.

For more information see Working with option groups.

configuration change

Applying modification to convert to a Multi-AZ DB instance.

configuration change

Applying modification to convert to a standard (Single-AZ) DB instance.

configuration change

Applying modification to database instance class.

configuration change

Applying modification to allocated storage.

configuration change

Updated to use DBParameterGroup name.

configuration change

Finished updating DB parameter group.

configuration change

Disabled automated backups.

configuration change

Enabled automated backups.

configuration change

There are number users matching the master username; only resetting the one not tied to a specific host.

configuration change

Finished applying modification to convert to a Multi-AZ DB instance.

configuration change

Finished applying modification to convert to a standard (Single-AZ) DB instance.

configuration change

Finished applying modification to DB instance class.

configuration change

Finished applying modification to allocated storage.

configuration change

Reset master credentials.

configuration change

Unable to reset your password. Error information: message.

configuration change

Monitoring Interval changed to number.

The Enhanced Monitoring configuration has been changed.

configuration change

Applying autoscaling-initiated modification to allocated storage.

configuration change

Finished applying autoscaling-initiated modification to allocated storage.

creation

DB instance created.

deletion

DB instance deleted.

failover

Multi-AZ instance failover started.

A Multi-AZ failover that resulted in the promotion of a standby DB instance has started.

failover

Multi-AZ failover to standby complete - DNS propagation may take a few minutes.

A Multi-AZ failover that resulted in the promotion of a standby DB instance is complete. It may take several minutes for the DNS to transfer to the new primary DB instance.

failover

Abandoning user requested failover since a failover recently occurred on the database instance.

Amazon RDS isn't attempting a requested failover because a failover recently occurred on the DB instance.

failover

failover

Multi-AZ instance activation started.

A Multi-AZ activation has started after a successful DB instance recovery

failover

Multi-AZ instance activation completed.

A Multi-AZ activation is complete. Your database should be accessible now.

failover

Recovered from partial failover.

failure

DB instance put into name state. RDS recommends that you initiate a point-in-time-restore.

The DB instance has failed due to an incompatible configuration or an underlying storage issue. Begin a point-in-time-restore for the DB instance.

Unable to move incompatible-network database, name, to the available status: message

The database networking configuration is invalid. The database could not be moved from incompatible-network to available.

failure

Database instance put into state. message.

The DB instance has invalid parameters. For example, if the DB instance could not start because a memory-related parameter is set too high for this instance class, your action would be to modify the memory parameter and reboot the DB instance.

failure

Database instance in state. message.

The DB instance is in an incompatible network. Some of the specified subnet IDs are invalid or do not exist.

failure

The Statspack installation failed. message.

Error while creating Oracle Statspack user account PERFSTAT. Drop the account before you add the STATSPACK option.

failure

Amazon RDS has been unable to create credentials for enhanced monitoring and this feature has been disabled. This is likely due to the rds-monitoring-role not being present and configured correctly in your account. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

Enhanced Monitoring can't be enabled without the Enhanced Monitoring IAM role. For information about creating the IAM role, see To create an IAM role for Amazon RDS enhanced monitoring.

failure

Amazon RDS has been unable to configure enhanced monitoring on your instance: name and this feature has been disabled. This is likely due to the rds-monitoring-role not being present and configured correctly in your account. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

Enhanced Monitoring was disabled because an error occurred during the configuration change. It is likely that the Enhanced Monitoring IAM role is configured incorrectly. For information about creating the enhanced monitoring IAM role, see To create an IAM role for Amazon RDS enhanced monitoring.

failure

Amazon RDS has been unable to create credentials for name option. This is due to the name IAM role not being configured correctly in your account. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

The IAM role that you use to access your Amazon S3 bucket for SQL Server native backup and restore is configured incorrectly. For more information, see Setting up for native backup and restore.

failure

The RDS Custom DB instance is outside the support perimeter.

It's your responsibility to fix configuration issues that put your RDS Custom DB instance into the unsupported-configuration state. If the issue is with the Amazon infrastructure, you can use the console or the Amazon CLI to fix it. If the issue is with the operating system or the database configuration, you can log in to the host to fix it.

For more information, see RDS Custom support perimeter.

failure

The DB instance is in a state that can't be upgraded. message

Amazon RDS was unable to upgrade a MySQL DB instance from version 5.7 to version 8.0 because of incompatibilities related to the data dictionary. The DB instance was rolled back to MySQL version 5.7. For more information, see Rollback after failure to upgrade from MySQL 5.7 to 8.0.

failure

DB instance is in an invalid state. No actions are necessary. Autoscaling will retry later.

failure

DB instance is in the cooling-off period for a previous scale storage operation. We're optimizing your DB instance. This takes at least 6 hours. No actions are necessary. Autoscaling will retry after the cooling-off period.

failure

Storage autoscaling is unable to scale the storage for the reason: reason.

failure

Storage autoscaling has triggered a pending scale storage task that will reach or exceed the maximum storage threshold. Increase the maximum storage threshold.

failure

DB instance has a storage type that's currently unavailable in the Availability Zone. Autoscaling will retry later.

failure

Underlying storage quota for this customer account has exceeded the limit. Please increase the allowed storage quota to let the scaling go through on the instance.

failure

RDS-EVENT-0278

The DB instance creation failed. message

The message includes details about the failure.

failure

RDS-EVENT-0279

The promotion of the RDS Custom read replica failed. message

The message includes details about the failure.

failure

RDS-EVENT-0280

RDS Custom couldn't upgrade the DB instance because the pre-check failed. message

The message includes details about the failure.

failure

RDS-EVENT-0281

RDS Custom couldn't modify the DB instance because the pre-check failed. message

The message includes details about the failure.

failure

RDS-EVENT-0282

RDS Custom couldn't modify the DB instance because the Elastic IP permissions aren't correct. Please confirm the Elastic IP address is tagged with AWSRDSCustom.

failure

RDS-EVENT-0283

RDS Custom couldn't modify the DB instance because the Elastic IP limit has been reached in your account. Release unused Elastic IPs or request a quota increase for your Elastic IP address limit.

failure

RDS-EVENT-0284

RDS Custom couldn't convert the instance to high availability because the pre-check failed. message

The message includes details about the failure.

failure

RDS-EVENT-0285

RDS Custom couldn't create a final snapshot for the DB instance because message.

The message includes details about the failure.

low storage

Allocated storage has been exhausted. Allocate additional storage to resolve.

The allocated storage for the DB instance has been consumed. To resolve this issue, allocate additional storage for the DB instance. For more information, see the RDS FAQ. You can monitor the storage space for a DB instance using the Free Storage Space metric.

low storage

The free storage capacity for DB instance: name is low at percentage of the provisioned storage [Provisioned Storage: size, Free Storage: size]. You may want to increase the provisioned storage to address this issue.

The DB instance has consumed more than 90% of its allocated storage. You can monitor the storage space for a DB instance using the Free Storage Space metric.

low storage

Your Aurora cluster's storage is dangerously low with only amount terabytes remaining. Please take measures to reduce the storage load on your cluster.

The Aurora storage subsystem is running low on space.

maintenance

Applying off-line patches to DB instance.

Offline maintenance of the DB instance is taking place. The DB instance is currently unavailable.

maintenance

Finished applying off-line patches to DB instance.

Offline maintenance of the DB instance is complete. The DB instance is now available.

maintenance

Database instance patched.

maintenance

The DB instance has a DB engine minor version upgrade available.

maintenance

The pre-check started for the DB engine version upgrade.

maintenance

The pre-check finished for the DB engine version upgrade.

maintenance

The downtime started for the DB instance.

maintenance

The engine version upgrade started.

maintenance

The engine version upgrade finished.

maintenance

The post-upgrade tasks are in progress.

maintenance

The DB engine version upgrade failed. The engine version upgrade rollback succeeded.

maintenance, notification

A new version of the time zone file is available for update.

If you update your RDS for Oracle DB engine, Amazon RDS generates this event if you haven't chosen a time zone file upgrade and the database doesn’t use the latest DST time zone file available on the instance. For more information, see Oracle time zone file autoupgrade.

maintenance, notification

The update of your time zone file has started.

The upgrade of your Oracle time zone file has begun. For more information, see Oracle time zone file autoupgrade.

maintenance, notification

No update is available for the current time zone file version.

Your Oracle DB instance is using latest time zone file version, and either of the following statements is true:

For more information, see Oracle time zone file autoupgrade.

maintenance, notification

The update of your time zone file has finished.

The update of your Oracle time zone file has completed. For more information, see Oracle time zone file autoupgrade.

maintenance, failure

message

The update of the Oracle time zone file failed. For more information, see Oracle time zone file autoupgrade.

notification

message

This is an operator-issued notification. For more information, see the event message.

notification

Delaying database engine upgrade since this instance has read replicas that need to be upgraded first.

Patching of the DB instance has been delayed.

notification

message

The MySQL storage engine you are using is not InnoDB, which is the recommended MySQL storage engine for Amazon RDS. For information about MySQL storage engines, see Supported storage engines for RDS for MySQL.

notification

message

The number of tables you have for your DB instance exceeds the recommended best practices for Amazon RDS. Reduce the number of tables on your DB instance. For information about recommended best practices, see Amazon RDS basic operational guidelines.

notification

message

The number of databases you have for your DB instance exceeds the recommended best practices for Amazon RDS. Reduce the number of databases on your DB instance. For information about recommended best practices, see Amazon RDS basic operational guidelines.

notification

The TDE encryption key was rotated successfully.

For information about recommended best practices, see Amazon RDS basic operational guidelines.

notification

Unable to convert the DB instance to Multi-AZ: message.

You attempted to convert a DB instance to Multi-AZ, but it contains in-memory file groups that are not supported for Multi-AZ. For more information, see Multi-AZ deployments for Amazon RDS for Microsoft SQL Server.

notification

DB instance stopped.

notification

DB instance started.

notification

DB instance is being started due to it exceeding the maximum allowed time being stopped.

notification

Unable to modify the DB instance class. message.

RDS can't modify the DB instance class because the target instance class can't support the number of databases that exist on the source DB instance. The error message appears as: "The instance has N databases, but after conversion it would only support N". For more information, see Limitations for Microsoft SQL Server DB instances.

notification

Database instance is in a state that cannot be upgraded: message.

notification

message

The RDS Custom support perimeter configuration has changed.

notification

The gp2 burst balance credits for the RDS database instance are low. To resolve this issue, reduce IOPS usage or modify your storage settings to enable higher performance.

The gp2 burst balance credits for the RDS database instance are low. To resolve this issue, reduce IOPS usage or modify your storage settings to enable higher performance. For more information, see I/O credits and burst performance in the Amazon Elastic Compute Cloud User Guide.

notification

Storage size amount GB is approaching the maximum storage threshold amount GB. Increase the maximum storage threshold.

This event is invoked when storage reaches 80% of the maximum storage threshold. To avoid the event, increase the maximum storage threshold.

notification

Your DB instance's storage modification encountered an internal error. The modification request is pending and will be retried later.

An error has occurred in the read replication process. For more information, see the event message.

In addition, see the troubleshooting section for read replicas for your DB engine.

notification

The database is using the doublewrite buffer. message. For more information see the RDS Optimized Writes for name documentation.

RDS Optimized Writes is incompatible with the instance storage configuration. For more information, see Improving write performance with Amazon RDS Optimized Writes for MySQL and Improving write performance with Amazon RDS Optimized Writes for MariaDB.

read replica

Replication has stopped.

Replication on your DB instance has been stopped due to insufficient storage. Scale storage or reduce the maximum size of your redo logs to let replication continue. To accommodate redo logs of size %d MiB you need at least %d MiB free storage.

read replica

Replication for the Read Replica resumed.

This message appears when you first create a read replica, or as a monitoring message confirming that replication is functioning properly. If this message follows an RDS-EVENT-0045 notification, then replication has resumed following an error or after replication was stopped.

read replica

Replication streaming has been terminated.

read replica

Replication for the Read Replica has been manually stopped.

read replica

Replication from Non RDS instance has been reset.

read replica

Read replica creation failed.

recovery

Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered.

recovery

Recovery of the DB instance is complete.

recovery

Emergent Snapshot Request: message.

A manual backup has been requested but Amazon RDS is currently in the process of creating a DB snapshot. Submit the request again after Amazon RDS has completed the DB snapshot.

recovery

Multi-AZ instance recovery started.

Recovery time will vary with the amount of data to be recovered.

recovery

Multi-AZ instance recovery completed. Pending failover or activation.

recovery

Instance will be degraded while mirroring is reestablished: message.

The SQL Server DB instance is re-establishing its mirror. Performance will be degraded until the mirror is reestablished. A database was found with non-FULL recovery model. The recovery model was changed back to FULL and mirroring recovery was started. (<dbname>: <recovery model found>[,...])"

recovery

message

The RDS Custom DB instance is inside the support perimeter.

restoration

Restored from DB instance name to name.

The DB instance has been restored from a point-in-time backup.

security

Decrypting hsm partition password to update instance.

RDS is decrypting the Amazon CloudHSM partition password to make updates to the DB instance. For more information see Oracle Database Transparent Data Encryption (TDE) with Amazon CloudHSM in the Amazon CloudHSM User Guide.

security patching

A system update is available for your DB instance. For information about applying updates, see 'Maintaining a DB instance' in the RDS User Guide.

A new Operating System update is available.

A new, minor version, operating system update is available for your DB instance. For information about applying updates, see Working with operating system updates.

configuration change

Updated parameter name to value with apply method method.

configuration change

Applied change to security group.

failure

Revoking authorization as user.

The security group owned by user doesn't exist. The authorization for the security group has been revoked because it is invalid.

backup

Creating manual cluster snapshot.

backup

Manual cluster snapshot created.

Creating automated cluster snapshot.

Automated cluster snapshot created.

RDS modified DB proxy name.

RDS modified the end point of the DB proxy name.

RDS detected the addition of the DB instance and automatically added it to the target group of the DB proxy name.

configuration change

RDS detected creation of DB instance name and automatically added it to target group name of DB proxy name.

configuration change

RDS detected deletion of DB instance name and automatically removed it from target group name of DB proxy name.

configuration change

RDS detected deletion of DB cluster name and automatically removed it from target group name of DB proxy name.

creation

RDS created DB proxy name.

creation

RDS created endpoint name for DB proxy name.

RDS deleted DB proxy name.

deletion

RDS deleted endpoint name for DB proxy name.

failure

RDS failed to provision capacity for proxy name because there aren't enough IP addresses available in your subnets: name. To fix the issue, make sure that your subnets have the minimum number of unused IP addresses as recommended in the RDS Proxy documentation.

To determine the recommended number for your instance class, see Planning for IP address capacity.

failure

RDS throttled some connections to DB proxy (RDS Proxy).

creation

Blue/green deployment tasks completed. You can make more modifications to the green environment databases or switch over the deployment.

deletion

Blue/green deployment deleted.

failure

Creation of blue/green deployment failed because the (source/target) DB (instance/cluster) wasn't found.

failure

Switchover canceled on blue/green deployment.

failure

Switchover from primary source to target canceled due to reason.

failure

Switchover from source to target was canceled.

notification

Switchover started on blue/green deployment.

notification

Switchover completed on blue/green deployment.

notification

Switchover from primary source to target started.

notification

Switchover from primary source to target completed. Renamed databases.

notification

Switchover from source to target started.

notification

Switchover from source to target completed. Renamed databases.

failure

Creation failed for custom engine version name. message

The message includes details about the failure, such as missing files.

failure

Failure during deletion of custom engine version name. message

The message includes details about the failure.