Sign In to the Console
Amazon Aurora
User Guide for Aurora (API Version 2014-10-31)

AWS Documentation » Amazon Relational Database Service (RDS) » User Guide for Aurora » Monitoring an Amazon Aurora DB Cluster » Using Amazon RDS Event Notification

Using Amazon RDS Event Notification

Amazon RDS uses the Amazon Simple Notification Service (Amazon SNS) to provide notification when an Amazon RDS event occurs. These notifications can be in any notification form supported by Amazon SNS for an AWS Region, such as an email, a text message, or a call to an HTTP endpoint.

Amazon RDS groups these events into categories that you can subscribe to so that you can be notified when an event in that category occurs. You can subscribe to an event category for a DB instance, DB cluster, DB cluster snapshot, DB parameter group, or DB security group. For example, if you subscribe to the Backup category for a given DB instance, you are notified whenever a backup-related event occurs that affects the DB instance. If you subscribe to a configuration change category for a DB security group, you are notified when the DB security group is changed. You also receive notification when an event notification subscription changes.

For Amazon Aurora, events occur at the cluster rather than instance level, so you don't receive events if you subscribe to an Aurora DB instance. Subscribe to the DB cluster instead.

Event notifications are sent to the addresses that you provide when you create the subscription. You might want to create several different subscriptions, such as one subscription receiving all event notifications and another subscription that includes only critical events for your production DB instances. You can easily turn off notification without deleting a subscription by choosing No for Enabled in the Amazon RDS console or by setting the Enabled parameter to false using the AWS CLI or Amazon RDS API.

Note

Amazon RDS event notifications using SMS text messages are currently available for topic Amazon Resource Names (ARNs) and Amazon RDS resources in the US-East (Northern Virginia) Region. For more information on using text messages with SNS, see Sending and Receiving SMS Notifications Using Amazon SNS.

Amazon RDS uses the ARN of an Amazon SNS topic to identify each subscription. The Amazon RDS console creates the ARN for you when you create the subscription. If you use the CLI or API, you create the ARN by using the Amazon SNS console or the Amazon SNS API when you create a subscription.

Billing for Amazon RDS event notification is through the Amazon Simple Notification Service (Amazon SNS). Amazon SNS fees apply when using event notification. For more information on Amazon SNS billing, see Amazon Simple Notification Service Pricing.

The process for subscribing to Amazon RDS event notification is as follows:

  1. Create an Amazon RDS event notification subscription by using the Amazon RDS console, AWS CLI, or API.

  2. Amazon RDS sends an approval email or SMS message to the addresses you submitted with your subscription. To confirm your subscription, choose the link in the notification you were sent.

  3. When you have confirmed the subscription, the status of your subscription is updated in the Amazon RDS console's My Event Subscriptions section.

  4. You then begin to receive event notifications.

The following section lists all categories and events that you can be notified of. It also provides information about subscribing to and working with Amazon RDS event subscriptions.

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, which can be a DB instance, DB snapshot, DB security group, or DB parameter group.

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 is restarting due to a previous controlled shutdown, or a recovery. The DB instance will be unavailable until the restart completes.

availability

 RDS-EVENT-0004

The DB instance is undergoing a controlled shutdown.

availability

 RDS-EVENT-0022

An error has occurred while restarting MySQL or MariaDB.

backup

 RDS-EVENT-0001

A backup of the DB instance has started.

backup

 RDS-EVENT-0002

A backup of the DB instance is complete.

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

The DB instance class for this DB instance is being changed.

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.

creation

 RDS-EVENT-0005

A DB instance is being created.

deletion

 RDS-EVENT-0003

The DB instance is being deleted.

failover

 RDS-EVENT-0034

Amazon RDS is not attempting a requested failover because a failover recently occurred on the DB instance.

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-0065

The instance has recovered from a partial failover.
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.

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-0036

The DB instance is in an incompatible network. Some of the specified subnet IDs are invalid or do not exist.

failure

 RDS-EVENT-0035

The DB instance has invalid parameters. For example, MySQL could not start because a memory-related parameter is set too high for this instance class, so the customer action would be to modify the memory parameter and reboot the DB instance.

failure

 RDS-EVENT-0058

Error while creating Statspack user account PERFSTAT. Please drop the account before adding 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-0082

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 Migrating Data from MySQL by Using an Amazon S3 Bucket .

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. For more information, see Viewing DB Instance Metrics.

low storage

 RDS-EVENT-0007

The allocated storage for the DB instance has been exhausted. To resolve this issue, you should 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. For more information, see Viewing DB Instance Metrics.

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.

notification RDS-EVENT-0044 Operator-issued notification. For more information, see the event message.
notification RDS-EVENT-0047 Patching of the DB instance has completed.
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. Please reduce the number of tables on your DB instance.

For information about recommended best practices, see Best Practices with Amazon Aurora.

notification RDS-EVENT-0056

The number of databases you have for your DB instance exceeds the recommended best practices for Amazon RDS. Please reduce the number of databases on your DB instance.

For information about recommended best practices, see Best Practices with Amazon Aurora.

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-0155

The DB instance has a DB engine minor version upgrade available.
read replica RDS-EVENT-0045 An error has occurred in the read replication process. For more information, see the event message.

For information on troubleshooting Read Replica errors, see Troubleshooting a MySQL or MariaDB Read Replica Problem.

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.

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.

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

The CloudHSM Classic partition password was decrypted by the system.

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

Description

configuration change

 RDS-EVENT-0037

The parameter group was modified.

The following table shows the event category and a list of events when a DB security group is the source type.

Category

 RDS Event ID

Description

configuration change

 RDS-EVENT-0038

The security group has been modified.

failure

 RDS-EVENT-0039

The Amazon EC2 security group owned by [user] does not exist; authorization for the security group has been revoked.

The following table shows the event category and a list of events when an Aurora DB cluster is the source type.

Category

 RDS Event ID

Description

failover

 RDS-EVENT-0069

A failover for the DB cluster has failed.

failover

 RDS-EVENT-0070

A failover for the DB cluster has restarted.

failover

 RDS-EVENT-0071

A failover for the DB cluster has finished.

failover

 RDS-EVENT-0072

A failover for the DB cluster has begun within the same Availability Zone.

failover

 RDS-EVENT-0073

A failover for the DB cluster has begun across Availability Zones.

failure

 RDS-EVENT-0083

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 Migrating Data from MySQL by Using an Amazon S3 Bucket .

notification

 RDS-EVENT-0076

Migration to an Aurora DB cluster failed.

notification

 RDS-EVENT-0077

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

notification

 RDS-EVENT-0149

A scaling point was not found.

notification

 RDS-EVENT-0150

The DB cluster stopped.

notification

 RDS-EVENT-0151

The DB cluster started.

notification

 RDS-EVENT-0152

The DB cluster stop failed.

notification

 RDS-EVENT-0153

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

notification

 RDS-EVENT-0156

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

The following table shows the event category and a list of events when an Aurora DB cluster snapshot is the source type.

Category

 RDS Event ID

Description

backup

 RDS-EVENT-0074

Creation of a manual DB cluster snapshot has started.

backup

 RDS-EVENT-0075

A manual DB cluster snapshot has been created.

Subscribing to Amazon RDS Event Notification

You can create an Amazon RDS event notification subscription so you can be notified when an event occurs for a given DB instance, DB snapshot, DB security group, or DB parameter group. The simplest way to create a subscription is with the RDS console. If you choose to create event notification subscriptions using the CLI or API, you must create an Amazon Simple Notification Service topic and subscribe to that topic with the Amazon SNS console or Amazon SNS API. You will also need to retain the Amazon Resource Name (ARN) of the topic because it is used when submitting CLI commands or API actions. For information on creating an SNS topic and subscribing to it, see Getting Started with Amazon SNS.

You can specify the type of source you want to be notified of and the Amazon RDS source that triggers the event. These are defined by the SourceType (type of source) and the SourceIdentifier (the Amazon RDS source generating the event). If you specify both the SourceType and SourceIdentifier, such as SourceType = db-instance and SourceIdentifier = myDBInstance1, you receive all the DB instance events for the specified source. If you specify a SourceType but don't specify a SourceIdentifier, you receive notice of the events for that source type for all your Amazon RDS sources. If you don't specify either the SourceType or the SourceIdentifier, you are notified of events generated from all Amazon RDS sources belonging to your customer account.

Note

Event notifications might take up to five minutes to be delivered.

AWS Management Console

To subscribe to RDS event notification

  1. Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/.

  2. In navigation pane, choose Event subscriptions.

  3. In the Event subscriptions pane, choose Create event subscription.

  4. In the Create event subscription dialog box, do the following:

    1. For Name, enter a name for the event notification subscription.

    2. For Send notifications to, choose an existing Amazon SNS ARN for an Amazon SNS topic, or choose create topic to enter the name of a topic and a list of recipients.

    3. For Source type, choose a source type.

    4. Choose Yes to enable the subscription. If you want to create the subscription but to not have notifications sent yet, choose No.

    5. Depending on the source type you selected, choose the event categories and sources that you want to receive event notifications for.

    6. Choose Create.

The Amazon RDS console indicates that the subscription is being created.

List DB event notification subscriptions
CLI

To subscribe to RDS event notification, use the AWS CLI create-event-subscription command. Include the following required parameters:

  • --subscription-name

  • --sns-topic-arn

Example

For Linux, OS X, or Unix:

aws rds create-event-subscription \
    --subscription-name myeventsubscription \
    --sns-topic-arn arn:aws:sns:us-east-1:802#########:myawsuser-RDS \
    --enabled

For Windows:

aws rds create-event-subscription ^
    --subscription-name myeventsubscription ^
    --sns-topic-arn arn:aws:sns:us-east-1:802#########:myawsuser-RDS ^
    --enabled
API

To subscribe to Amazon RDS event notification, call the Amazon RDS API function CreateEventSubscription. Include the following required parameters:

  • SubscriptionName

  • SnsTopicArn

Listing Your Amazon RDS Event Notification Subscriptions

You can list your current Amazon RDS event notification subscriptions.

AWS Management Console

To list your current Amazon RDS event notification subscriptions

  1. Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/.

  2. In the navigation pane, choose Event subscriptions. The Event subscriptions pane shows all your event notification subscriptions.

    List DB event notification subscriptions
CLI

To list your current Amazon RDS event notification subscriptions, use the AWS CLI describe-event-subscriptions command.

Example

The following example describes all event subscriptions.

aws rds describe-event-subscriptions

The following example describes the myfirsteventsubscription. 

aws rds describe-event-subscriptions --subscription-name myfirsteventsubscription
API

To list your current Amazon RDS event notification subscriptions, call the Amazon RDS API DescribeEventSubscriptions action.

Example

The following code example lists up to 100 event subscriptions.

https://rds.us-east-1.amazonaws.com/
   ?Action=DescribeEventSubscriptions
   &MaxRecords=100
   &SignatureMethod=HmacSHA256
   &SignatureVersion=4
   &Version=2014-09-01
   &X-Amz-Algorithm=AWS4-HMAC-SHA256
   &X-Amz-Credential=AKIADQKE4SARGYLE/20140428/us-east-1/rds/aws4_request
   &X-Amz-Date=20140428T161907Z
   &X-Amz-SignedHeaders=content-type;host;user-agent;x-amz-content-sha256;x-amz-date
   &X-Amz-Signature=4208679fe967783a1a149c826199080a066085d5a88227a80c6c0cadb3e8c0d4

The following example describes the myfirsteventsubscription. 

https://rds.us-east-1.amazonaws.com/
   ?Action=DescribeEventSubscriptions
   &SignatureMethod=HmacSHA256
   &SignatureVersion=4
   &SubscriptionName=myfirsteventsubscription
   &Version=2014-09-01
   &X-Amz-Algorithm=AWS4-HMAC-SHA256
   &X-Amz-Credential=AKIADQKE4SARGYLE/20140428/us-east-1/rds/aws4_request
   &X-Amz-Date=20140428T161907Z
   &X-Amz-SignedHeaders=content-type;host;user-agent;x-amz-content-sha256;x-amz-date
   &X-Amz-Signature=4208679fe967783a1a149c826199080a066085d5a88227a80c6c0cadb3e8c0d4

Modifying an Amazon RDS Event Notification Subscription

After you have created a subscription, you can change the subscription name, source identifier, categories, or topic ARN.

AWS Management Console

To modify an Amazon RDS event notification subscription

  1. Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/.

  2. In the navigation pane, choose Event subscriptions.

  3. In the Event subscriptions pane, choose the subscription that you want to modify and choose Edit.

  4. Make your changes to the subscription in either the Target or Source section.

  5. Choose Edit. The Amazon RDS console indicates that the subscription is being modified.

    List DB event notification subscriptions
CLI

To modify an Amazon RDS event notification subscription, use the AWS CLI modify-event-subscription command. Include the following required parameter:

  • --subscription-name

Example

The following code enables myeventsubscription.

For Linux, OS X, or Unix:

aws rds modify-event-subscription \
    --subscription-name myeventsubscription \
    --enabled

For Windows:

aws rds modify-event-subscription ^
    --subscription-name myeventsubscription ^
    --enabled
API

To modify an Amazon RDS event, call the Amazon RDS API action ModifyEventSubscription. Include the following required parameter:

  • SubscriptionName

Adding a Source Identifier to an Amazon RDS Event Notification Subscription

You can add a source identifier (the Amazon RDS source generating the event) to an existing subscription.

AWS Management Console

You can easily add or remove source identifiers using the Amazon RDS console by selecting or deselecting them when modifying a subscription. For more information, see Modifying an Amazon RDS Event Notification Subscription.

CLI

To add a source identifier to an Amazon RDS event notification subscription, use the AWS CLI add-source-identifier-to-subscription command. Include the following required parameters:

  • --subscription-name

  • --source-identifier

Example

The following example adds the source identifier mysqldb to the myrdseventsubscription subscription.

For Linux, OS X, or Unix:

aws rds add-source-identifier-to-subscription \
    --subscription-name myrdseventsubscription \
    --source-identifier mysqldb

For Windows:

aws rds add-source-identifier-to-subscription ^
    --subscription-name myrdseventsubscription ^
    --source-identifier mysqldb
API

To add a source identifier to an Amazon RDS event notification subscription, call the Amazon RDS API AddSourceIdentifierToSubscription. Include the following required parameters:

  • SubscriptionName

  • SourceIdentifier

Removing a Source Identifier from an Amazon RDS Event Notification Subscription

You can remove a source identifier (the Amazon RDS source generating the event) from a subscription if you no longer want to be notified of events for that source.

AWS Management Console

You can easily add or remove source identifiers using the Amazon RDS console by selecting or deselecting them when modifying a subscription. For more information, see Modifying an Amazon RDS Event Notification Subscription.

CLI

To remove a source identifier from an Amazon RDS event notification subscription, use the AWS CLI remove-source-identifier-from-subscription command. Include the following required parameters:

  • --subscription-name

  • --source-identifier

Example

The following example removes the source identifier mysqldb from the myrdseventsubscription subscription.

For Linux, OS X, or Unix:

aws rds remove-source-identifier-from-subscription \
    --subscription-name myrdseventsubscription \
    --source-identifier mysqldb

For Windows:

aws rds remove-source-identifier-from-subscription ^
    --subscription-name myrdseventsubscription ^
    --source-identifier mysqldb
API

To remove a source identifier from an Amazon RDS event notification subscription, use the Amazon RDS API RemoveSourceIdentifierFromSubscription command. Include the following required parameters:

  • SubscriptionName

  • SourceIdentifier

Listing the Amazon RDS Event Notification Categories

All events for a resource type are grouped into categories. To view the list of categories available, use the following procedures.

AWS Management Console

When you create or modify an event notification subscription, the event categories are displayed in the Amazon RDS console. For more information, see Modifying an Amazon RDS Event Notification Subscription.

List DB event notification categories
CLI

To list the Amazon RDS event notification categories, use the AWS CLI describe-event-categories command. This command has no required parameters.

Example 

aws rds describe-event-categories
API

To list the Amazon RDS event notification categories, use the Amazon RDS API DescribeEventCategories command. This command has no required parameters.

Deleting an Amazon RDS Event Notification Subscription

You can delete a subscription when you no longer need it. All subscribers to the topic will no longer receive event notifications specified by the subscription.

AWS Management Console

To delete an Amazon RDS event notification subscription

  1. Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/.

  2. In the navigation pane, choose DB Event Subscriptions.

  3. In the My DB Event Subscriptions pane, choose the subscription that you want to delete.

  4. Choose Delete.

  5. The Amazon RDS console indicates that the subscription is being deleted.

    Delete an event notification subscription
CLI

To delete an Amazon RDS event notification subscription, use the AWS CLI delete-event-subscription command. Include the following required parameter:

  • --subscription-name

Example

The following example deletes the subscription myrdssubscription. 

delete-event-subscription --subscription-name myrdssubscription
API

To delete an Amazon RDS event notification subscription, use the RDS API DeleteEventSubscription command. Include the following required parameter:

  • SubscriptionName