Amazon RDS event categories and event messages for Aurora

configuration change

Reset master credentials.

None

configuration change

Database Activity Streams is started on your database cluster.

For more information see Monitoring Amazon Aurora with Database Activity Streams.

configuration change

Database Activity Streams is stopped on your database cluster.

For more information see Monitoring Amazon Aurora with Database Activity Streams.

DB cluster created.

None

DB cluster deleted.

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

Amazon RDS has been unable to create credentials to access your Amazon S3 Bucket for your DB cluster name. This is due to the S3 snapshot ingestion IAM role not being configured correctly in your account or the specified Amazon S3 bucket cannot be found. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

For more information, see Physical migration from MySQL by using Percona XtraBackup and Amazon S3 .

failure

The DB cluster failed to scale from units to units for this reason: reason.

Scaling failed for the Aurora Serverless DB cluster.

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.

failure

Failed to partition DB instances in DB cluster name for patching.

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 version has been upgraded.

Patching of the DB cluster has completed.

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

maintenance

Upgrade preparation in progress: cluster_name

maintenance

Starting offline patches to DB instances in partition name/name for DB cluster name: partition_n.

maintenance

We were unable to upgrade your DB cluster operating system. You can wait for the next maintenance window, or you can upgrade your DB cluster operating system manually.

notification

Failed to migrate from name to name. Reason: reason.

Migration to an Aurora DB cluster failed.

notification

Failed to convert name.name to InnoDB. Reason: reason.

An attempt to convert a table from the source database to InnoDB failed during the migration to an Aurora DB cluster.

notification

Unable to upgrade DB cluster name because the instance name has a status of name. Resolve the issue or delete the instance and try again.

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

Scaling DB cluster from units to units for this reason: reason.

Scaling initiated for the Aurora Serverless DB cluster.

notification

The DB cluster has scaled from units to units.

Scaling completed for the Aurora Serverless DB cluster.

notification

The DB cluster is being paused.

An automatic pause was initiated for the Aurora Serverless DB cluster.

notification

The DB cluster is paused.

The Aurora Serverless DB cluster has been paused.

notification

Pause was canceled for the DB cluster.

The pause was canceled for the Aurora Serverless DB cluster.

notification

The DB cluster is being resumed.

notification

The DB cluster is resumed.

notification

The DB cluster has scaled from units to units, but scaling wasn't seamless for this reason: reason.

Seamless scaling completed with the force option for the Aurora Serverless DB cluster. Connections might have been interrupted as required.

notification

DB cluster stopped.

None

notification

DB cluster started.

None

notification

DB cluster stop failed.

None

notification

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

None

notification

Renamed cluster from name to name.

None

notification

Export task failed.

The DB cluster export task failed.

notification

Export task canceled.

The DB cluster export task was canceled.

notification

Export task completed.

The DB cluster export task completed.

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.

notification

DB instances in DB cluster name have been partitioned: list_of_partitions. DB cluster is online.

backup

Creating manual cluster snapshot.

None

backup

Manual cluster snapshot created.

None

The cluster snapshot export task failed.

None

The cluster snapshot export task was canceled.

None

The cluster snapshot export task completed.

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 Aurora MySQL or RDS for MariaDB.

backtrack

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

The actual Backtrack window is the same as the target Backtrack window.

None

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

Finished applying modification to allocated storage.

None

configuration change

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

None

configuration change

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

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

creation

DB instance created.

None

deletion

DB instance deleted.

None

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

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 to access your Amazon S3 Bucket for your DB instance name. This is due to the S3 snapshot ingestion IAM role not being configured correctly in your account or the specified Amazon S3 bucket cannot be found. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

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

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

The DB instance can't be created because of insufficient resource limits. 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.

None

maintenance

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

None

maintenance

Database instance upgrade is in progress.

None

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

DB instance stopped.

None

notification

DB instance started.

None

notification, serverless

Initiated pause for the DB instance.

A new attempt to pause an idle Aurora Serverless v2 DB instance was started.

notification, serverless

Pause was canceled for the DB instance.

An attempt to pause an idle Aurora Serverless v2 DB instance was unsuccessful, due to workload.

notification, serverless

Successfully paused the DB instance.

The Aurora Serverless v2 DB instance was paused.

notification, serverless

Initiated resume for the DB instance.

The Aurora Serverless v2 DB instance started resuming, due to new workload or administrative or maintenance activity.

notification, serverless

Successfully resumed the DB instance.

notification, global database

Attempt to block writes for DB cluster cluster_id in Region region_id succeeded.

Aurora began blocking writes at the storage layer in preparation for switchover or failover of an Aurora global database.

notification, global database

Attempt to block writes for DB cluster cluster_id in Region region_id timed out.

Aurora wasn't able to block writes at the storage layer in preparation for switchover or failover of an Aurora global database. The switchover or failover will proceed but you might need to recover recently written data from the snapshot of the original primary cluster.

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

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

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 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, minor version, operating system patch is available for your DB instance. For information about applying updates, see Operating system updates for Aurora DB clusters.

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.

Data load job failed.

The data loading job failed for the reason that appears in the error message.

Initializing infrastructure for the Data Load job.

None

Data load job is in progress.

None

Data load job completed successfully.

None

Canceling Data load job as per customer’s request.

None

Data load job canceled.

None

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