Amazon RDS event categories and event messages for Aurora
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.
Topics
DB cluster events
The following table shows the event category and a list of events when a DB cluster is the source type.
Note
No event category exists for Aurora Serverless in the DB cluster event type. The Aurora Serverless events range from RDS-EVENT-0141 to RDS-EVENT-0149.
Category |
RDS event ID |
Message |
Notes |
---|---|---|---|
configuration change |
RDS-EVENT-0016 |
Reset master credentials. |
None |
configuration change |
RDS-EVENT-0179 |
Database Activity Streams is started on your database cluster. |
For more information see Monitoring Amazon Aurora with Database Activity Streams. |
configuration change |
RDS-EVENT-0180 |
Database Activity Streams is stopped on your database cluster. |
For more information see Monitoring Amazon Aurora with Database Activity Streams. |
creation | RDS-EVENT-0170 |
DB cluster created. |
None |
deletion | RDS-EVENT-0171 |
DB cluster deleted. |
None |
failover |
RDS-EVENT-0069 |
Cluster failover failed, check the health of your cluster instances and try again. |
None |
failover |
RDS-EVENT-0070 |
Promoting previous primary again: |
None |
failover |
RDS-EVENT-0071 |
Completed failover to DB instance: |
None |
failover |
RDS-EVENT-0072 |
Started same AZ failover to DB instance: |
None |
failover |
RDS-EVENT-0073 |
Started cross AZ failover to DB instance: |
None |
failure |
RDS-EVENT-0083 |
Amazon RDS has been unable to create credentials to access your Amazon S3 Bucket
for your DB cluster |
For more information, see Physical migration from MySQL by using Percona XtraBackup and Amazon S3 . |
failure |
RDS-EVENT-0143 |
The DB cluster failed to scale from |
Scaling failed for the Aurora Serverless DB cluster. |
failure |
RDS-EVENT-0354 |
You can't create the DB cluster because of incompatible resources.
|
The |
failure |
RDS-EVENT-0355 |
The DB cluster can't be created because of insufficient resource
limits. |
The |
global failover |
RDS-EVENT-0181 |
Global switchover to DB cluster |
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 |
RDS-EVENT-0182 |
Old primary DB cluster |
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 |
RDS-EVENT-0183 |
Waiting for data synchronization across global cluster members.
Current lags behind primary DB cluster: |
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 |
RDS-EVENT-0184 |
New primary DB cluster |
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 |
RDS-EVENT-0185 |
Global switchover to DB cluster |
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 |
RDS-EVENT-0186 |
Global switchover to DB cluster |
This event is for a switchover operation (previously called "managed planned failover"). |
global failover |
RDS-EVENT-0187 |
Global switchover to DB cluster |
This event is for a switchover operation (previously called "managed planned failover"). |
global failover |
RDS-EVENT-0238 |
Global failover to DB cluster |
None |
global failover |
RDS-EVENT-0239 |
Global failover to DB cluster |
None |
global failover |
RDS-EVENT-0240 |
Started resynchronizing members of DB cluster |
None |
global failover |
RDS-EVENT-0241 |
Finished resynchronizing members of DB cluster |
None |
maintenance |
RDS-EVENT-0156 |
The DB cluster has a DB engine minor version upgrade available. |
None |
maintenance |
RDS-EVENT-0173 |
Database cluster engine version has been upgraded. |
Patching of the DB cluster has completed. |
maintenance |
RDS-EVENT-0176 |
Database cluster engine major version has been upgraded. |
None |
maintenance |
RDS-EVENT-0177 |
Database cluster upgrade is in progress. |
None |
maintenance |
RDS-EVENT-0286 |
Database cluster engine version upgrade started. |
None |
maintenance |
RDS-EVENT-0287 |
Operating system upgrade requirement detected. |
None |
maintenance |
RDS-EVENT-0288 |
Cluster operating system upgrade starting. |
None |
maintenance |
RDS-EVENT-0289 |
Cluster operating system upgrade completed. |
None |
maintenance |
RDS-EVENT-0363 |
Upgrade preparation in progress: |
Upgrade prechecks have started for the DB cluster. |
notification |
RDS-EVENT-0076 |
Failed to migrate from |
Migration to an Aurora DB cluster failed. |
notification |
RDS-EVENT-0077 |
Failed to convert |
An attempt to convert a table from the source database to InnoDB failed during the migration to an Aurora DB cluster. |
notification |
RDS-EVENT-0085 |
Unable to upgrade DB cluster |
An error occurred while attempting to patch the Aurora DB cluster. Check your instance status, resolve the issue, and try again. For more information see Maintaining an Amazon Aurora DB cluster. |
notification |
RDS-EVENT-0141 |
Scaling DB cluster from |
Scaling initiated for the Aurora Serverless DB cluster. |
notification |
RDS-EVENT-0142 |
The DB cluster has scaled from |
Scaling completed for the Aurora Serverless DB cluster. |
notification |
RDS-EVENT-0144 |
The DB cluster is being paused. |
An automatic pause was initiated for the Aurora Serverless DB cluster. |
notification |
RDS-EVENT-0145 |
The DB cluster is paused. |
The Aurora Serverless DB cluster has been paused. |
notification |
RDS-EVENT-0146 |
Pause was canceled for the DB cluster. |
The pause was canceled for the Aurora Serverless DB cluster. |
notification |
RDS-EVENT-0147 |
The DB cluster is being resumed. |
A resume operation was initiated for the Aurora Serverless DB cluster. |
notification |
RDS-EVENT-0148 |
The DB cluster is resumed. |
The resume operation completed for the Aurora Serverless DB cluster. |
notification |
RDS-EVENT-0149 |
The DB cluster has scaled from |
Seamless scaling completed with the force option for the Aurora Serverless DB cluster. Connections might have been interrupted as required. |
notification |
RDS-EVENT-0150 |
DB cluster stopped. |
None |
notification |
RDS-EVENT-0151 |
DB cluster started. |
None |
notification |
RDS-EVENT-0152 |
DB cluster stop failed. |
None |
notification |
RDS-EVENT-0153 |
DB cluster is being started due to it exceeding the maximum allowed time being stopped. |
None |
notification |
RDS-EVENT-0172 |
Renamed cluster from |
None |
notification |
RDS-EVENT-0234 |
Export task failed. |
The DB cluster export task failed. |
notification |
RDS-EVENT-0235 |
Export task canceled. |
The DB cluster export task was canceled. |
notification |
RDS-EVENT-0236 |
Export task completed. |
The DB cluster export task completed. |
notification |
RDS-EVENT-0385 |
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. |
DB instance events
The following table shows the event category and a list of events when a DB instance is the source type.
Category |
RDS event ID |
Message |
Notes |
---|---|---|---|
availability |
RDS-EVENT-0004 |
DB instance shutdown. |
None |
availability |
RDS-EVENT-0006 |
DB instance restarted. |
None |
availability |
RDS-EVENT-0022 |
Error restarting mysql: |
An error has occurred while restarting Aurora MySQL or RDS for MariaDB. |
backtrack |
RDS-EVENT-0131 |
The actual Backtrack window is smaller than the target Backtrack window you specified. Consider reducing the number of hours in your target Backtrack window. |
For more information about backtracking, see Backtracking an Aurora DB cluster. |
backtrack |
RDS-EVENT-0132 |
The actual Backtrack window is the same as the target Backtrack window. |
None |
configuration change |
RDS-EVENT-0011 |
Updated to use DBParameterGroup
|
None |
configuration change |
RDS-EVENT-0012 |
Applying modification to database instance class. |
None |
configuration change |
RDS-EVENT-0014 |
Finished applying modification to DB instance class. |
None |
configuration change |
RDS-EVENT-0017 |
Finished applying modification to allocated storage. |
None |
configuration change |
RDS-EVENT-0025 |
Finished applying modification to convert to a Multi-AZ DB instance. |
None |
configuration change |
RDS-EVENT-0029 |
Finished applying modification to convert to a standard (Single-AZ) DB instance. |
None |
configuration change |
RDS-EVENT-0033 |
There are |
None |
configuration change |
RDS-EVENT-0067 |
Unable to reset your password. Error information:
|
None |
configuration change |
RDS-EVENT-0078 |
Monitoring Interval changed to
|
The Enhanced Monitoring configuration has been changed. |
configuration change |
RDS-EVENT-0092 |
Finished updating DB parameter group. |
None |
creation |
RDS-EVENT-0005 |
DB instance created. |
None |
deletion |
RDS-EVENT-0003 |
DB instance deleted. |
None |
failure |
RDS-EVENT-0035 |
Database instance put into |
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 |
RDS-EVENT-0036 |
Database instance in |
The DB instance is in an incompatible network. Some of the specified subnet IDs are invalid or do not exist. |
failure |
RDS-EVENT-0079 |
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 |
RDS-EVENT-0080 |
Amazon RDS has been unable to configure enhanced monitoring on your
instance: |
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 |
RDS-EVENT-0082 |
Amazon RDS has been unable to create credentials to access your Amazon S3
Bucket for your DB instance |
Aurora was unable to copy backup data from an Amazon S3 bucket. It is likely that the permissions for Aurora to access the Amazon S3 bucket are configured incorrectly. For more information, see Physical migration from MySQL by using Percona XtraBackup and Amazon S3 . |
failure |
RDS-EVENT-0254 |
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-0353 |
The DB instance can't be created because of insufficient resource limits.
|
The |
low storage |
RDS-EVENT-0007 |
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 |
low storage |
RDS-EVENT-0089 |
The free storage capacity for DB instance: |
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 |
RDS-EVENT-0227 |
Your Aurora cluster's storage is dangerously low with only
|
The Aurora storage subsystem is running low on space. |
maintenance |
RDS-EVENT-0026 |
Applying off-line patches to DB instance. |
Offline maintenance of the DB instance is taking place. The DB instance is currently unavailable. |
maintenance |
RDS-EVENT-0027 |
Finished applying off-line patches to DB instance. |
Offline maintenance of the DB instance is complete. The DB instance is now available. |
maintenance |
RDS-EVENT-0047 |
Database instance patched. |
None |
maintenance |
RDS-EVENT-0155 |
The DB instance has a DB engine minor version upgrade available. |
None |
maintenance |
RDS-EVENT-0178 |
Database instance upgrade is in progress. |
None |
notification |
RDS-EVENT-0044 |
|
This is an operator-issued notification. For more information, see the event message. |
notification |
RDS-EVENT-0048 |
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 |
RDS-EVENT-0087 |
DB instance stopped. |
None |
notification |
RDS-EVENT-0088 |
DB instance started. |
None |
read replica |
RDS-EVENT-0045 |
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
|
read replica |
RDS-EVENT-0046 |
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 |
read replica |
RDS-EVENT-0057 |
Replication streaming has been terminated. |
None |
recovery |
RDS-EVENT-0020 |
Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered. |
None |
recovery |
RDS-EVENT-0021 |
Recovery of the DB instance is complete. |
None |
recovery |
RDS-EVENT-0023 |
Emergent Snapshot Request: |
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 |
Multi-AZ instance recovery started. |
Recovery time will vary with the amount of data to be recovered. |
recovery |
RDS-EVENT-0053 |
Multi-AZ instance recovery completed. Pending failover or activation. |
None |
recovery |
RDS-EVENT-0361 |
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 |
RDS-EVENT-0362 |
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 |
RDS-EVENT-0019 |
Restored from DB instance |
The DB instance has been restored from a point-in-time backup. |
security patching |
RDS-EVENT-0230 |
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 patch is available. A new, minor version, operating system update is available for your DB instance. For information about applying updates, see Operating system updates in Amazon Aurora. |
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.
Category |
RDS event ID |
Message |
Notes |
---|---|---|---|
configuration change |
RDS-EVENT-0037 |
Updated parameter |
None |
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.
Note
DB security groups are resources for EC2-Classic. EC2-Classic was retired on August 15, 2022. If you
haven't migrated from EC2-Classic to a VPC, we recommend that you migrate as soon as possible. For more information,
see Migrate from EC2-Classic to a VPC in the Amazon EC2
User Guide and the blog
EC2-Classic Networking is Retiring – Here’s How to Prepare
Category |
RDS event ID |
Message |
Notes |
---|---|---|---|
configuration change |
RDS-EVENT-0038 |
Applied change to security group. |
None |
failure |
RDS-EVENT-0039 |
Revoking authorization as |
The security group owned by |
DB cluster snapshot events
The following table shows the event category and a list of events when a DB cluster snapshot is the source type.
Category |
RDS event ID |
Message |
Notes |
---|---|---|---|
backup |
RDS-EVENT-0074 |
Creating manual cluster snapshot. |
None |
backup |
RDS-EVENT-0075 |
Manual cluster snapshot created. |
None |
notification | RDS-EVENT-0162 |
The cluster snapshot export task failed. |
None |
notification | RDS-EVENT-0163 |
The cluster snapshot export task was canceled. |
None |
notification | RDS-EVENT-0164 |
The cluster snapshot export task completed. |
None |
backup | RDS-EVENT-0168 |
Creating automated cluster snapshot. |
None |
backup | RDS-EVENT-0169 |
Automated cluster snapshot created. |
None |
RDS Proxy events
The following table shows the event category and a list of events when an RDS Proxy is the source type.
Category |
RDS event ID |
Message |
Notes |
---|---|---|---|
configuration change | RDS-EVENT-0204 |
RDS modified DB proxy |
None |
configuration change | RDS-EVENT-0207 |
RDS modified the end point of the DB proxy |
None |
configuration change | RDS-EVENT-0213 |
RDS detected the addition of the DB instance and automatically added it to the target group of the DB proxy |
None |
configuration change |
RDS-EVENT-0214 |
RDS detected deletion of DB instance |
None |
configuration change |
RDS-EVENT-0215 |
RDS detected deletion of DB cluster |
None |
creation |
RDS-EVENT-0203 |
RDS created DB proxy |
None |
creation |
RDS-EVENT-0206 |
RDS created endpoint |
None |
deletion | RDS-EVENT-0205 |
RDS deleted DB proxy |
None |
deletion |
RDS-EVENT-0208 |
RDS deleted endpoint |
None |
failure |
RDS-EVENT-0243 |
RDS failed to provision capacity for proxy |
To determine the recommended number for your instance class, see Planning for IP address capacity. |
failure |
RDS-EVENT-0275 |
RDS throttled some connections to DB proxy
|
None |
Blue/green deployment events
The following table shows the event category and a list of events when a blue/green deployment is the source type.
For more information about blue/green deployments, see Using Amazon RDS Blue/Green Deployments for database updates.
Category |
Amazon RDS event ID |
Message |
Notes |
---|---|---|---|
creation |
RDS-EVENT-0244 |
Blue/green deployment tasks completed. You can make more modifications to the green environment databases or switch over the deployment. |
None |
failure |
RDS-EVENT-0245 |
Creation of blue/green deployment failed because the (source/target) DB (instance/cluster) wasn't found. |
None |
deletion |
RDS-EVENT-0246 |
Blue/green deployment deleted. |
None |
notification |
RDS-EVENT-0247 |
Switchover from |
None |
notification |
RDS-EVENT-0248 |
Switchover completed on blue/green deployment. |
None |
failure |
RDS-EVENT-0249 |
Switchover canceled on blue/green deployment. |
None |
notification |
RDS-EVENT-0259 |
Switchover from DB cluster
|
None |
notification |
RDS-EVENT-0260 |
Switchover from DB cluster
|
None |
failure |
RDS-EVENT-0261 |
Switchover from DB cluster
|
None |
notification |
RDS-EVENT-0311 |
Sequence sync for switchover of DB cluster
|
None |
notification |
RDS-EVENT-0312 |
Sequence sync for switchover of DB cluster
|
None |
failure |
RDS-EVENT-0314 |
Sequence sync for switchover of DB cluster
|
None |