Amazon RDS event categories and event messages
Amazon RDS generates a significant number of events in categories that you can subscribe to using the Amazon RDS Console, AWS CLI, or the API. Each category applies to a source type.
DB instance events
The following table shows the event category and a list of events when a DB instance is the source type.
|
Category |
Amazon RDS event ID |
Description |
|---|---|---|
|
availability |
RDS-EVENT-0006 |
The DB instance restarted. |
|
availability |
RDS-EVENT-0004 |
DB instance shutdown. |
|
availability |
RDS-EVENT-0022 |
An error has occurred while restarting MySQL. |
|
availability |
RDS-EVENT-0221 |
The 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 |
RDS-EVENT-0222 |
Free storage capacity for DB instance [instance name] is low at [percentage]% of the allocated storage (allocated storage: [value], free storage: [value]). The database will be shut down to prevent corruption if free storage is lower than [value]. You can increase the allocated storage to address this issue. |
|
backup |
RDS-EVENT-0001 |
Backing up the DB instance. |
|
backup |
RDS-EVENT-0002 |
Finished DB Instance backup. |
|
backup |
RDS-EVENT-0086 |
RDS was unable to associate the option group with the database instance. Confirm that the option group is supported on your DB instance class and configuration. For more information see Working with option groups. |
|
configuration change |
RDS-EVENT-0009 |
The DB instance has been added to a security group. |
|
configuration change |
RDS-EVENT-0024 |
The DB instance is being converted to a Multi-AZ DB instance. |
|
configuration change |
RDS-EVENT-0030 |
The DB instance is being converted to a Single-AZ DB instance. |
|
configuration change |
RDS-EVENT-0012 |
Applying modification to database instance class. |
|
configuration change |
RDS-EVENT-0018 |
The current storage settings for this DB instance are being changed. |
|
configuration change |
RDS-EVENT-0011 |
A parameter group for this DB instance has changed. |
|
configuration change |
RDS-EVENT-0092 |
A parameter group for this DB instance has finished updating. |
|
configuration change |
RDS-EVENT-0028 |
Automatic backups for this DB instance have been disabled. |
|
configuration change |
RDS-EVENT-0032 |
Automatic backups for this DB instance have been enabled. |
|
configuration change |
RDS-EVENT-0033 |
There are [count] users that match the master user name. Users not tied to a specific host have been reset. |
|
configuration change |
RDS-EVENT-0025 |
The DB instance has been converted to a Multi-AZ DB instance. |
|
configuration change |
RDS-EVENT-0029 |
The DB instance has been converted to a Single-AZ DB instance. |
|
configuration change |
RDS-EVENT-0014 |
The DB instance class for this DB instance has changed. |
|
configuration change |
RDS-EVENT-0017 |
The storage settings for this DB instance have changed. |
|
configuration change |
RDS-EVENT-0010 |
The DB instance has been removed from a security group. |
|
configuration change |
RDS-EVENT-0016 |
The master password for the DB instance has been reset. |
|
configuration change |
RDS-EVENT-0067 |
An attempt to reset the master password for the DB instance has failed. |
|
configuration change |
RDS-EVENT-0078 |
The Enhanced Monitoring configuration has been changed. |
|
configuration change |
RDS-EVENT-0217 |
Applying autoscaling-initiated modification to allocated storage. |
|
configuration change |
RDS-EVENT-0218 |
Finished applying autoscaling-initiated modification to allocated storage. |
|
creation |
RDS-EVENT-0005 |
DB instance created. |
|
deletion |
RDS-EVENT-0003 |
The DB instance has been deleted. |
|
failover |
RDS-EVENT-0013 |
A Multi-AZ failover that resulted in the promotion of a standby instance has started. |
|
failover |
RDS-EVENT-0015 |
A Multi-AZ failover that resulted in the promotion of a standby instance is complete. It may take several minutes for the DNS to transfer to the new primary DB instance. |
|
failover |
RDS-EVENT-0034 |
Amazon RDS is not attempting a requested failover because a failover recently occurred on the DB instance. |
|
failover |
RDS-EVENT-0049 | A Multi-AZ failover has completed. |
|
failover |
RDS-EVENT-0050 |
A Multi-AZ activation has started after a successful instance recovery. |
|
failover |
RDS-EVENT-0051 |
A Multi-AZ activation is complete. Your database should be accessible now. |
|
failover |
RDS-EVENT-0065 |
The instance has recovered from a partial failover. |
|
failure |
RDS-EVENT-0031 |
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 |
RDS-EVENT-0035 |
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, the customer action would be to modify the memory parameter and reboot the DB instance. |
|
failure |
RDS-EVENT-0036 |
The DB instance is in an incompatible network. Some of the specified subnet IDs are invalid or do not exist. |
|
failure |
RDS-EVENT-0058 |
Error while creating Statspack user account PERFSTAT. Drop the account before you add the Statspack option. |
|
failure |
RDS-EVENT-0079 |
Enhanced Monitoring cannot be enabled without the enhanced monitoring IAM role. For information on creating the enhanced monitoring IAM role, see To create an IAM role for Amazon RDS enhanced monitoring. |
|
failure |
RDS-EVENT-0080 |
Enhanced Monitoring was disabled due to an error making the configuration change. It is likely that the enhanced monitoring IAM role is configured incorrectly. For information on creating the enhanced monitoring IAM role, see To create an IAM role for Amazon RDS enhanced monitoring. |
|
failure |
RDS-EVENT-0081 |
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 |
RDS-EVENT-0165 |
The RDS Custom DB instance is outside the support perimeter. |
|
failure |
RDS-EVENT-0188 |
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 |
RDS-EVENT-0219 |
The DB instance is in an invalid state. No actions are necessary. Autoscaling will retry later. |
|
failure |
RDS-EVENT-0220 |
The DB instance is in the cooling-off period for a previous scale storage operation. We are optimizing your instance. This takes at least six hours. No actions are necessary. Autoscaling will retry after the cooling-off period. |
|
failure |
RDS-EVENT-0223 |
Storage autoscaling is unable to scale the storage for the reason: [reason]. |
|
failure |
RDS-EVENT-0224 |
Storage autoscaling has triggered a pending scale storage task that would reach the maximum storage threshold. Increase the maximum storage threshold. |
|
low storage |
RDS-EVENT-0007 |
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 |
|
low storage |
RDS-EVENT-0089 |
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. |
|
maintenance |
RDS-EVENT-0026 |
Offline maintenance of the DB instance is taking place. The DB instance is currently unavailable. |
|
maintenance |
RDS-EVENT-0027 |
Offline maintenance of the DB instance is complete. The DB instance is now available. |
|
maintenance |
RDS-EVENT-0047 |
Patching of the DB instance has completed. |
|
maintenance |
RDS-EVENT-0155 |
The DB instance has a DB engine minor version upgrade available. |
|
maintenance, notification |
RDS-EVENT-0191 |
An Oracle time zone file update is available. If you update your Oracle 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 |
RDS-EVENT-0192 |
The upgrade of your Oracle time zone file has begun. For more information, see Oracle time zone file autoupgrade. |
|
maintenance, notification |
RDS-EVENT-0193 |
Your Oracle DB instance is using latest time zone file version, and either of the following is true:
For more information, see Oracle time zone file autoupgrade. |
|
maintenance, notification |
RDS-EVENT-0194 |
The upgrade of your Oracle time zone file has completed. For more information, see Oracle time zone file autoupgrade. |
|
maintenance, failure |
RDS-EVENT-0195 |
The upgrade of the time zone file failed. For more information, see Oracle time zone file autoupgrade. |
|
notification |
RDS-EVENT-0044 | Operator-issued notification. For more information, see the event message. |
|
notification |
RDS-EVENT-0048 | Patching of the DB instance has been delayed. |
|
notification |
RDS-EVENT-0054 | 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 MySQL on Amazon RDS. |
|
notification |
RDS-EVENT-0055 |
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 |
RDS-EVENT-0056 |
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 |
RDS-EVENT-0064 | The TDE key has been rotated. For information about recommended best practices, see Amazon RDS basic operational guidelines. |
|
notification |
RDS-EVENT-0084 |
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 |
RDS-EVENT-0087 |
The DB instance has been stopped. |
|
notification |
RDS-EVENT-0088 |
The DB instance has been started. |
|
notification |
RDS-EVENT-0154 |
The DB instance is being started due to it exceeding the maximum allowed time being stopped. |
|
notification |
RDS-EVENT-0157 |
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 |
RDS-EVENT-0158 |
DB instance is in a state that can't be upgraded. |
|
notification |
RDS-EVENT-0167 |
The RDS Custom support perimeter configuration has changed. |
|
notification |
RDS-EVENT-0225 |
Storage size [value] GB is approaching the maximum storage threshold [value] GB. Increase the maximum storage threshold. |
|
read replica |
RDS-EVENT-0045 |
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. |
|
read replica |
RDS-EVENT-0046 | The read replica has resumed replication. 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 |
RDS-EVENT-0057 |
Replication on the read replica was terminated. |
|
read replica |
RDS-EVENT-0062 |
Replication on the read replica was manually stopped. |
|
read replica |
RDS-EVENT-0063 |
Replication on the read replica was reset. |
|
read replica |
RDS-EVENT-0202 |
Read replica creation failed. |
|
recovery |
RDS-EVENT-0020 |
Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered. |
|
recovery |
RDS-EVENT-0021 |
Recovery of the DB instance is complete. |
|
recovery |
RDS-EVENT-0023 |
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 |
RDS-EVENT-0052 |
Recovery of the Multi-AZ instance has started. Recovery time will vary with the amount of data to be recovered. |
|
recovery |
RDS-EVENT-0053 |
Recovery of the Multi-AZ instance is complete. |
|
recovery |
RDS-EVENT-0066 |
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 |
RDS-EVENT-0166 |
The RDS Custom DB instance is inside the support perimeter. |
|
restoration |
RDS-EVENT-0008 |
The DB instance has been restored from a DB snapshot. |
|
restoration |
RDS-EVENT-0019 |
The DB instance has been restored from a point-in-time backup. |
|
security |
RDS-EVENT-0068 |
RDS is decrypting the CloudHSM partition password to make updates to the instance. For more information see Oracle Database Transparent Data Encryption (TDE) with AWS CloudHSM in the AWS CloudHSM User Guide. |
DB parameter group events
The following table shows the event category and a list of events when a DB parameter group is the source type.
DB security group events
The following table shows the event category and a list of events when a DB security group is the source type.
DB snapshot events
The following table shows the event category and a list of events when a DB snapshot is the source type.
