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.

failure

The upgrade_type version upgrade for DB cluster name was canceled because a failover occurred on the associated global database. The DB cluster is now running engine version version. Retry the upgrade when the global database is available.

Retry the upgrade when the global database is available.

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

global failover

Global database failover to DB cluster name in global database name completed. The DB cluster has no instances. Create a DB instance to access your data.

Create a DB instance to access your data.

global failover

Waiting for data synchronization with the target DB cluster. Current target DB cluster lag behind the primary DB cluster: %s.

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.

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 is in a state that cannot be upgraded.

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

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.

None

maintenance

The engine version of DB cluster name has been changed from previous_version to current_version to align with the new primary cluster name after a failover.

No action required. This change is automatic and keeps your global database consistent.

maintenance

The DB cluster name is running version version, which is higher than the target upgrade version version for the global cluster. We don't recommend having a secondary cluster on a higher version than the global cluster, as it can cause issues during failover or switchover. Consider upgrading your global cluster to match.

None

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.