Amazon RDS event categories and event messages

configuration change

Reset master credentials.

None

DB cluster created.

None

failover

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

None

failover

Promoting previous primary again: name.

None

failover

Completed failover to DB instance: name.

None

failover

Started same AZ failover to DB instance: name.

None

failover

Started cross AZ failover to DB instance: name.

None

failure

You can't create the DB cluster because of incompatible resources. message.

The message includes details about the failure.

failure

The DB cluster can't be created because of insufficient resource limits. message.

The message includes details about the failure.

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.

None

global failover

Global failover to DB cluster name in Region name failed.

None

global failover

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

None

global failover

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

None

global failover

Aurora finished changing the DNS name that the global writer endpoint resolves to.

None

maintenance

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

None

maintenance

Database cluster engine major version has been upgraded.

None

maintenance

Database cluster upgrade is in progress.

None

maintenance

Database cluster engine version_number version upgrade started. Cluster remains online.

None

maintenance

Operating system upgrade requirement detected.

None

maintenance

Cluster operating system upgrade starting.

None

maintenance

Cluster operating system upgrade completed.

None

maintenance

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

None

notification

Renamed cluster from name to name.

None

notification

Cluster topology is updated.

There are DNS changes to the DB cluster. This includes when new DB instances are added or deleted, or there's a failover.

backup

Creating manual cluster snapshot.

None

backup

Manual cluster snapshot created.

None

Creating automated cluster snapshot.

None

Automated cluster snapshot created.

None

availability

DB instance shutdown.

None

availability

DB instance restarted.

None

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.

None

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.

availability

The free storage capacity of the dedicated transaction log volume is too low for DB instance name. The log volume free storage is percentage of the allocated storage. [Allocated storage: amount, Free storage: amount] The database will be shut down to prevent corruption if the free storage is lower than amount. You can disable the dedicated transaction log volume to resolve this issue.

For more information, see Dedicated log volume (DLV).

availability

The free storage capacity of the dedicated transaction log volume is too low for DB instance name. The log volume free storage is percentage of the provisioned storage. [Provisioned Storage: amount, Free Storage: amount] You can disable the dedicated transaction log volume to resolve this issue.

For more information, see Dedicated log volume (DLV).

availability

Amazon RDS has scheduled a reboot for this read replica in this instance's next maintenance window after internal user password rotation.

None

backup

Backing up DB instance.

None

backup

Finished DB instance backup.

None

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

Updated to use DBParameterGroup name.

None

configuration change

Applying modification to database instance class.

None

configuration change

Finished applying modification to DB instance class.

None

configuration change

Reset master credentials.

None

configuration change

Finished applying modification to allocated storage.

None

configuration change

Applying modification to allocated storage.

None

configuration change

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

None

configuration change

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

None

configuration change

Disabled automated backups.

None

configuration change

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

None

configuration change

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

None

configuration change

Enabled automated backups.

None

configuration change

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

None

configuration change

Unable to reset your password. Error information: message.

None

configuration change

Monitoring Interval changed to number.

The Enhanced Monitoring configuration has been changed.

configuration change

Finished updating DB parameter group.

None

configuration change

Applying autoscaling-initiated modification to allocated storage.

None

configuration change

Finished applying autoscaling-initiated modification to allocated storage.

None

configuration change

Storage configuration upgrade started.

None

configuration change

Storage configuration upgrade completed.

None

configuration change

The dedicated log volume is disabled.

For more information, see Dedicated log volume (DLV).

configuration change

Disabling the dedicated log volume has started.

For more information, see Dedicated log volume (DLV).

configuration change

Enabling the dedicated log volume has started.

For more information, see Dedicated log volume (DLV).

configuration change

The dedicated log volume is enabled.

For more information, see Dedicated log volume (DLV).

configuration change

engine version doesn't support the memcached plugin. RDS will continue upgrading your DB instance and remove this plugin.

Starting with MySQL 8.3.0, the memcached plugin isn't supported. For more information, see Changes in MySQL 8.3.0 (2024-01-16, Innovation Release).

creation

DB instance created.

None

deletion

DB instance deleted.

None

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

None

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.

None

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.

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 AWS infrastructure, you can use the console or the AWS 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 because of incompatibilities related to the data dictionary. The DB instance was rolled back to MySQL version 5.7 because an attempted upgrade to version 8.0 failed, or rolled back to MySQL version 8.0 because an attempted upgrade to version 8.4 failed. For more information, see Rollback after failure to upgrade.

failure

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

None

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.

None

failure

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

None

failure

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

None

failure

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

None

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.

None

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.

None

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.

None

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.

failure

Storage configuration upgrade failed. Please retry the upgrade.

None

failure

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

Failed to join a host to a domain. Domain membership status for instance instancename has been set to Failed.

None

failure

Failed to join a host to your domain. During the domain join process, Microsoft Windows returned the error code message. Verify your network and permission configurations and issue a modify-db-instance request to re-attempt the domain join.

failure

The DB instance can't be created because of insufficient resource limits. message.

The message includes details about the failure.

failure

RDS was unable to configure the Kerberos endpoint in your domain. This might prevent Kerberos authentication for your DB instance. Verify the network configuration between your DB instance and domain controllers.

None

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.

None

maintenance

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

None

maintenance

Database instance upgrade is in progress.

None

maintenance

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

None

maintenance

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

None

maintenance

The downtime started for the DB instance.

None

maintenance

The engine version upgrade started.

None

maintenance

The engine version upgrade finished.

None

maintenance

The post-upgrade tasks are in progress.

None

maintenance

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

None

maintenance, failure

message

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

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.

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.

None

notification

DB instance started.

None

notification

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

None

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.

None

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

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

This event is invoked when the allocated 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 RDS Optimized Writes for MySQL and Improving write performance with Amazon RDS Optimized Writes for MariaDB.

You can perform storage configuration upgrade to enable Optimized Writes by Creating a blue/green deployment.

notification

The storage configuration for DB instance name supports a maximum size of 16384 GiB. Perform a storage configuration upgrade to support storage sizes greater than 16384 GiB.

You cannot increase the allocated storage size of the DB instance beyond 16384 GiB. To overcome this limitation, perform a storage configuration upgrade. For more information, see Upgrading the storage file system for a DB instance.

notification

The storage configuration for DB instance name supports a maximum table size of 2048 GiB. Perform a storage configuration upgrade to support table sizes greater than 2048 GiB.

RDS MySQL and MariaDB instances with this limitation cannot have a table size exceeding 2048 GiB. To overcome this limitation, perform a storage configuration upgrade. For more information, see Upgrading the storage file system for a DB instance.

notification

Amazon RDS could not find the secret SECRET ARN. message.

None

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 amount MiB you need at least amount 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.

None

read replica

Replication for the Read Replica has been manually stopped.

None

read replica

Replication from Non RDS instance has been reset.

None

read replica

Read replica creation failed.

None

read replica

Replication channel name started.

For information about replication channels, see Configuring multi-source-replication for Amazon RDS for MySQL.

read replica

Replication channel name stopped.

For information about replication channels, see Configuring multi-source-replication for Amazon RDS for MySQL.

read replica

Replication channel name was manually stopped.

For information about replication channels, see Configuring multi-source-replication for Amazon RDS for MySQL.

read replica

Replication channel name was reset.

For information about replication channels, see Configuring multi-source-replication for Amazon RDS for MySQL.

recovery

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

None

recovery

Recovery of the DB instance is complete.

None

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.

None

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.

recovery

Recovery of standby DB instance has started.

The standby DB instance is rebuilt during the recovery process. Database performance is impacted during the recovery process.

recovery

Recovery of standby DB instance has completed.

The standby DB instance is rebuilt during the recovery process. Database performance is impacted during the recovery process.

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 AWS CloudHSM partition password to make updates to the DB instance. For more information see Oracle Database Transparent Data Encryption (TDE) with AWS CloudHSM in the AWS 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 Operating system updates for RDS DB instances.

configuration change

Updated parameter name to value with apply method method.

None

configuration change

Applied change to security group.

None

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.

RDS modified DB proxy name.

None

RDS modified the end point of the DB proxy name.

None

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

None

configuration change

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

None

configuration change

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

None

creation

RDS created DB proxy name.

None

creation

RDS created endpoint name for DB proxy name.

None

RDS deleted DB proxy name.

None

deletion

RDS deleted endpoint name for DB proxy name.

None

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 name. The number of simultaneous connection requests from the client to the proxy has exceeded the limit.

None

creation

Preparing to create custom engine version name. The entire creation process may take up to four hours to complete.

None

creation

Creating custom engine version name.

None

creation

Validating custom engine version name.

None

creation

Custom engine version name has been created successfully.

None

creation

RDS can't create custom engine version name because of an internal issue. We are addressing the problem and will contact you if necessary. For further assistance, contact AWS Premium Support/.

None

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.

restoring

The maximum database count supported for point-in-time restore has changed.

The message includes details about the event.