# Monitoring Amazon RDS events
An *event* indicates a change in an environment. This can be an AWS environment, an SaaS partner service or application, or a custom application or service. For descriptions of the RDS events, see [Amazon RDS event categories and event messages](USER_Events.Messages.md).
**Topics**
+ [Overview of events for Amazon RDS](#rds-cloudwatch-events.sample)
+ [Viewing Amazon RDS events](USER_ListEvents.md)
+ [Working with Amazon RDS event notification](USER_Events.md)
+ [Creating a rule that triggers on an Amazon RDS event](rds-cloud-watch-events.md)
+ [Amazon RDS event categories and event messages](USER_Events.Messages.md)
## Overview of events for Amazon RDS
An *RDS event* indicates a change in the Amazon RDS environment. For example, Amazon RDS generates an event when the state of a DB instance changes from pending to running. Amazon RDS delivers events to EventBridge in near-real time.
**Note**
Amazon RDS emits events on a best effort basis. We recommend that you avoid writing programs that depend on the order or existence of notification events, because they might be out of sequence or missing.
Amazon RDS records events that relate to the following resources:
+ DB instances
For a list of DB instance events, see [DB instance events](USER_Events.Messages.md#USER_Events.Messages.instance).
+ DB parameter groups
For a list of DB parameter group events, see [DB parameter group events](USER_Events.Messages.md#USER_Events.Messages.parameter-group).
+ DB security groups
For a list of DB security group events, see [DB security group events](USER_Events.Messages.md#USER_Events.Messages.security-group).
+ DB snapshots
For a list of DB snapshot events, see [DB snapshot events](USER_Events.Messages.md#USER_Events.Messages.snapshot).
+ RDS Proxy events
For a list of RDS Proxy events, see [RDS Proxy events](USER_Events.Messages.md#USER_Events.Messages.rds-proxy).
+ Blue/green deployment events
For a list of blue/green deployment events, see [Blue/green deployment events](USER_Events.Messages.md#USER_Events.Messages.BlueGreenDeployments).
This information includes the following:
+ The date and time of the event
+ The source name and source type of the event
+ A message associated with the event
+ Event notifications include tags from when the message was sent and may not reflect tags at the time when the event occurred
# Viewing Amazon RDS events
You can retrieve the following event information for your Amazon RDS resources:
+ Resource name
+ Resource type
+ Time of the event
+ Message summary of the event
You can access events in the following parts of the AWS Management Console:
+ The **Events** tab, which shows events from the past 24 hours.
+ The **Recent events** table in the **Logs & events** section in the **Databases** tab, which can show events for up to the past 2 weeks.
You can also retrieve events by using the [describe-events](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-events.html) AWS CLI command, or the [DescribeEvents](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeEvents.html) RDS API operation. If you use the AWS CLI or the RDS API to view events, you can retrieve events for up to the past 14 days.
**Note**
If you need to store events for longer periods of time, you can send Amazon RDS events to EventBridge. For more information, see [Creating a rule that triggers on an Amazon RDS event](rds-cloud-watch-events.md)
For descriptions of the Amazon RDS events, see [Amazon RDS event categories and event messages](USER_Events.Messages.md).
To access detailed information about events using AWS CloudTrail, including request parameters, see [CloudTrail events](logging-using-cloudtrail.md#service-name-info-in-cloudtrail.events).
## Console
**To view all Amazon RDS events for the past 24 hours**
1. Sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).
1. In the navigation pane, choose **Events**.
The available events appear in a list.
1. (Optional) Enter a search term to filter your results.
The following example shows a list of events filtered by the characters **stopped**.
![\[List DB events\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/ListEvents.png)
## AWS CLI
To view all events generated in the last hour, call [describe-events](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-events.html) with no parameters.
```
aws rds describe-events
```
The following sample output shows that a DB instance has been stopped.
```
{
"Events": [
{
"EventCategories": [
"notification"
],
"SourceType": "db-instance",
"SourceArn": "arn:aws:rds:us-east-1:123456789012:db:testinst",
"Date": "2022-04-22T21:31:00.681Z",
"Message": "DB instance stopped",
"SourceIdentifier": "testinst"
}
]
}
```
To view all Amazon RDS events for the past 10080 minutes (7 days), call the [describe-events](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-events.html) AWS CLI command and set the `--duration` parameter to `10080`.
```
1. aws rds describe-events --duration 10080
```
The following example shows the events in the specified time range for DB instance *test-instance*.
```
aws rds describe-events \
--source-identifier test-instance \
--source-type db-instance \
--start-time 2022-03-13T22:00Z \
--end-time 2022-03-13T23:59Z
```
The following sample output shows the status of a backup.
```
{
"Events": [
{
"SourceType": "db-instance",
"SourceIdentifier": "test-instance",
"EventCategories": [
"backup"
],
"Message": "Backing up DB instance",
"Date": "2022-03-13T23:09:23.983Z",
"SourceArn": "arn:aws:rds:us-east-1:123456789012:db:test-instance"
},
{
"SourceType": "db-instance",
"SourceIdentifier": "test-instance",
"EventCategories": [
"backup"
],
"Message": "Finished DB Instance backup",
"Date": "2022-03-13T23:15:13.049Z",
"SourceArn": "arn:aws:rds:us-east-1:123456789012:db:test-instance"
}
]
}
```
## API
You can view all Amazon RDS instance events for the past 14 days by calling the [DescribeEvents](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeEvents.html) RDS API operation and setting the `Duration` parameter to `20160`.
# Working with 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.
**Topics**
+ [Overview of Amazon RDS event notification](USER_Events.overview.md)
+ [Granting permissions to publish notifications to an Amazon SNS topic](USER_Events.GrantingPermissions.md)
+ [Subscribing to Amazon RDS event notification](USER_Events.Subscribing.md)
+ [Amazon RDS event notification tags and attributes](USER_Events.TagsAttributesForFiltering.md)
+ [Listing Amazon RDS event notification subscriptions](USER_Events.ListSubscription.md)
+ [Modifying an Amazon RDS event notification subscription](USER_Events.Modifying.md)
+ [Adding a source identifier to an Amazon RDS event notification subscription](USER_Events.AddingSource.md)
+ [Removing a source identifier from an Amazon RDS event notification subscription](USER_Events.RemovingSource.md)
+ [Listing the Amazon RDS event notification categories](USER_Events.ListingCategories.md)
+ [Deleting an Amazon RDS event notification subscription](USER_Events.Deleting.md)
# Overview of Amazon RDS event notification
Amazon RDS groups events into categories that you can subscribe to so that you can be notified when an event in that category occurs.
**Topics**
+ [RDS resources eligible for event subscription](#USER_Events.overview.resources)
+ [Basic process for subscribing to Amazon RDS event notifications](#USER_Events.overview.process)
+ [Delivery of RDS event notifications](#USER_Events.overview.subscriptions)
+ [Billing for Amazon RDS event notifications](#USER_Events.overview.billing)
+ [Examples of Amazon RDS events using Amazon EventBridge](#events-examples)
## RDS resources eligible for event subscription
You can subscribe to an event category for the following resources:
+ DB instance
+ DB snapshot
+ DB parameter group
+ DB security group
+ RDS Proxy
+ Custom engine version
For example, if you subscribe to the backup category for a given DB instance, you're notified whenever a backup-related event occurs that affects the DB instance. If you subscribe to a configuration change category for a DB instance, you're notified when the DB instance is changed. You also receive notification when an event notification subscription changes.
You might want to create several different subscriptions. For example, you might create one subscription that receives all event notifications for all DB instances and another subscription that includes only critical events for a subset of the DB instances. For the second subscription, specify one or more DB instances in the filter.
## Basic process for subscribing to Amazon RDS event notifications
The process for subscribing to Amazon RDS event notification is as follows:
1. You create an Amazon RDS event notification subscription by using the Amazon RDS console, AWS CLI, or API.
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. Create the ARN by using the Amazon SNS console, the AWS CLI, or the Amazon SNS API.
1. Amazon RDS sends an approval email or SMS message to the addresses you submitted with your subscription.
1. You confirm your subscription by choosing the link in the notification you received.
1. The Amazon RDS console updates the **My Event Subscriptions** section with the status of your subscription.
1. Amazon RDS begins sending the notifications to the addresses that you provided when you created the subscription.
To learn about identity and access management when using Amazon SNS, see [Identity and access management in Amazon SNS](https://docs.aws.amazon.com/sns/latest/dg/sns-authentication-and-access-control.html) in the *Amazon Simple Notification Service Developer Guide*.
You can use AWS Lambda to process event notifications from a DB instance. For more information, see [Using AWS Lambda with Amazon RDS](https://docs.aws.amazon.com/lambda/latest/dg/services-rds.html) in the *AWS Lambda Developer Guide*.
## Delivery of RDS event notifications
Amazon RDS sends notifications to the addresses that you provide when you create the subscription. The notification can include message attributes which provide structured metadata about the message. For more information about message attributes, see [Amazon RDS event categories and event messages](USER_Events.Messages.md).
Event notifications might take up to five minutes to be delivered.
**Important**
Amazon RDS doesn't guarantee the order of events sent in an event stream. The event order is subject to change.
When Amazon SNS sends a notification to a subscribed HTTP or HTTPS endpoint, the POST message sent to the endpoint has a message body that contains a JSON document. For more information, see [Amazon SNS message and JSON formats](https://docs.aws.amazon.com/sns/latest/dg/sns-message-and-json-formats.html) in the *Amazon Simple Notification Service Developer Guide*.
You can configure SNS to notify you with text messages. For more information, see [ Mobile text messaging (SMS)](https://docs.aws.amazon.com/sns/latest/dg/sns-mobile-phone-number-as-subscriber.html) in the *Amazon Simple Notification Service Developer Guide*.
To turn off notifications without deleting a subscription, choose **No** for **Enabled** in the Amazon RDS console. Or you can set the `Enabled` parameter to `false` using the AWS CLI or Amazon RDS API.
## Billing for Amazon RDS event notifications
Billing for Amazon RDS event notification is through Amazon SNS. Amazon SNS fees apply when using event notification. For more information about Amazon SNS billing, see [ Amazon Simple Notification Service pricing](http://aws.amazon.com/sns/#pricing).
## Examples of Amazon RDS events using Amazon EventBridge
The following examples illustrate different types of Amazon RDS events in JSON format. For a tutorial that shows you how to capture and view events in JSON format, see [Tutorial: Log DB instance state changes using Amazon EventBridge](rds-cloud-watch-events.md#log-rds-instance-state).
**Topics**
+ [Example of a DB instance event](#rds-cloudwatch-events.db-instances)
+ [Example of a DB parameter group event](#rds-cloudwatch-events.db-parameter-groups)
+ [Example of a DB snapshot event](#rds-cloudwatch-events.db-snapshots)
### Example of a DB instance event
The following is an example of a DB instance event in JSON format. The event shows that RDS performed a multi-AZ failover for the instance named `my-db-instance`. The event ID is RDS-EVENT-0049.
```
{
"version": "0",
"id": "68f6e973-1a0c-d37b-f2f2-94a7f62ffd4e",
"detail-type": "RDS DB Instance Event",
"source": "aws.rds",
"account": "123456789012",
"time": "2018-09-27T22:36:43Z",
"region": "us-east-1",
"resources": [
"arn:aws:rds:us-east-1:123456789012:db:my-db-instance"
],
"detail": {
"EventCategories": [
"failover"
],
"SourceType": "DB_INSTANCE",
"SourceArn": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
"Date": "2018-09-27T22:36:43.292Z",
"Message": "A Multi-AZ failover has completed.",
"SourceIdentifier": "my-db-instance",
"EventID": "RDS-EVENT-0049"
}
}
```
### Example of a DB parameter group event
The following is an example of a DB parameter group event in JSON format. The event shows that the parameter `time_zone` was updated in parameter group `my-db-param-group`. The event ID is RDS-EVENT-0037.
```
{
"version": "0",
"id": "844e2571-85d4-695f-b930-0153b71dcb42",
"detail-type": "RDS DB Parameter Group Event",
"source": "aws.rds",
"account": "123456789012",
"time": "2018-10-06T12:26:13Z",
"region": "us-east-1",
"resources": [
"arn:aws:rds:us-east-1:123456789012:pg:my-db-param-group"
],
"detail": {
"EventCategories": [
"configuration change"
],
"SourceType": "DB_PARAM",
"SourceArn": "arn:aws:rds:us-east-1:123456789012:pg:my-db-param-group",
"Date": "2018-10-06T12:26:13.882Z",
"Message": "Updated parameter time_zone to UTC with apply method immediate",
"SourceIdentifier": "my-db-param-group",
"EventID": "RDS-EVENT-0037"
}
}
```
### Example of a DB snapshot event
The following is an example of a DB snapshot event in JSON format. The event shows the deletion of the snapshot named `my-db-snapshot`. The event ID is RDS-EVENT-0041.
```
{
"version": "0",
"id": "844e2571-85d4-695f-b930-0153b71dcb42",
"detail-type": "RDS DB Snapshot Event",
"source": "aws.rds",
"account": "123456789012",
"time": "2018-10-06T12:26:13Z",
"region": "us-east-1",
"resources": [
"arn:aws:rds:us-east-1:123456789012:snapshot:rds:my-db-snapshot"
],
"detail": {
"EventCategories": [
"deletion"
],
"SourceType": "SNAPSHOT",
"SourceArn": "arn:aws:rds:us-east-1:123456789012:snapshot:rds:my-db-snapshot",
"Date": "2018-10-06T12:26:13.882Z",
"Message": "Deleted manual snapshot",
"SourceIdentifier": "my-db-snapshot",
"EventID": "RDS-EVENT-0041"
}
}
```
# Granting permissions to publish notifications to an Amazon SNS topic
To grant Amazon RDS permissions to publish notifications to an Amazon Simple Notification Service (Amazon SNS) topic, attach an AWS Identity and Access Management (IAM) policy to the destination topic. For more information about permissions, see [ Example cases for Amazon Simple Notification Service access control](https://docs.aws.amazon.com/sns/latest/dg/sns-access-policy-use-cases.html) in the *Amazon Simple Notification Service Developer Guide*.
By default, an Amazon SNS topic has a policy allowing all Amazon RDS resources within the same account to publish notifications to it. You can attach a custom policy to allow cross-account notifications, or to restrict access to certain resources.
The following is an example of an IAM policy that you attach to the destination Amazon SNS topic. It restricts the topic to DB instances with names that match the specified prefix. To use this policy, specify the following values:
+ `Resource` – The Amazon Resource Name (ARN) for your Amazon SNS topic
+ `SourceARN` – Your RDS resource ARN
+ `SourceAccount` – Your AWS account ID
To see a list of resource types and their ARNs, see [Resources Defined by Amazon RDS](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonrds.html#amazonrds-resources-for-iam-policies) in the *Service Authorization Reference*.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "events.rds.amazonaws.com"
},
"Action": [
"sns:Publish"
],
"Resource": "arn:aws:sns:us-east-1:123456789012:topic_name",
"Condition": {
"ArnLike": {
"aws:SourceArn": "arn:aws:rds:us-east-1:123456789012:db:prefix-*"
},
"StringEquals": {
"aws:SourceAccount": "123456789012"
}
}
}
]
}
```
------
# Subscribing to Amazon RDS event notification
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 operations. For information on creating an SNS topic and subscribing to it, see [Getting started with Amazon SNS](https://docs.aws.amazon.com/sns/latest/dg/GettingStarted.html) in the *Amazon Simple Notification Service Developer Guide*.
You can specify the type of source you want to be notified of and the Amazon RDS source that triggers the event:
**Source type**
The type of source. For example, **Source type** might be **Instances**. You must choose a source type.
***Resources* to include**
The Amazon RDS resources that are generating the events. For example, you might choose **Select specific instances** and then **myDBInstance1**.
The following table explains the result when you specify or don't specify ***Resources* to include**.
| Resources to include | Description | Example |
| --- | --- | --- |
| Specified | RDS notifies you about all events for the specified resource only. | If your Source type is Instances and your resource is myDBInstance1, RDS notifies you about all events for myDBInstance1 only. |
| Not specified | RDS notifies you about the events for the specified source type for all your Amazon RDS resources. | If your **Source type** is **Instances**, RDS notifies you about all instance-related events in your account. |
An Amazon SNS topic subscriber receives every message published to the topic by default. To receive only a subset of the messages, the subscriber must assign a filter policy to the topic subscription. For more information about SNS message filtering, see [Amazon SNS message filtering](https://docs.aws.amazon.com/sns/latest/dg/sns-message-filtering.html) in the *Amazon Simple Notification Service Developer Guide*
## 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/](https://console.aws.amazon.com/rds/).
1. In navigation pane, choose **Event subscriptions**.
1. In the **Event subscriptions** pane, choose **Create event subscription**.
1. Enter your subscription details as follows:
1. For **Name**, enter a name for the event notification subscription.
1. For **Send notifications to**, do one of the following:
+ Choose **New email topic**. Enter a name for your email topic and a list of recipients. We recommend that you configure the events subscriptions to the same email address as your primary account contact. The recommendations, service events, and personal health messages are sent using different channels. The subscriptions to the same email address ensures that all the messages are consolidated in one location.
+ Choose **Amazon Resource Name (ARN)**. Then choose existing Amazon SNS ARN for an Amazon SNS topic.
If you want to use a topic that has been enabled for server-side encryption (SSE), grant Amazon RDS the necessary permissions to access the AWS KMS key. For more information, see [ Enable compatibility between event sources from AWS services and encrypted topics](https://docs.aws.amazon.com/sns/latest/dg/sns-key-management.html#compatibility-with-aws-services) in the *Amazon Simple Notification Service Developer Guide*.
1. For **Source type**, choose a source type. For example, choose **Instances** or **Parameter groups**.
1. Choose the event categories and resources that you want to receive event notifications for.
The following example configures event notifications for the DB instance named `testinst`.
![\[Enter source type\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/event-source.png)
1. Choose **Create**.
The Amazon RDS console indicates that the subscription is being created.
![\[List DB event notification subscriptions\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/EventNotification-Create2.png)
## AWS CLI
To subscribe to RDS event notification, use the AWS CLI [https://docs.aws.amazon.com/cli/latest/reference/rds/create-event-subscription.html](https://docs.aws.amazon.com/cli/latest/reference/rds/create-event-subscription.html) command. Include the following required parameters:
+ `--subscription-name`
+ `--sns-topic-arn`
**Example**
For Linux, macOS, or Unix:
```
aws rds create-event-subscription \
--subscription-name myeventsubscription \
--sns-topic-arn arn:aws:sns:us-east-1:123456789012:myawsuser-RDS \
--enabled
```
For Windows:
```
aws rds create-event-subscription ^
--subscription-name myeventsubscription ^
--sns-topic-arn arn:aws:sns:us-east-1:123456789012:myawsuser-RDS ^
--enabled
```
## API
To subscribe to Amazon RDS event notification, call the Amazon RDS API function [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateEventSubscription.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateEventSubscription.html). Include the following required parameters:
+ `SubscriptionName`
+ `SnsTopicArn`
# Amazon RDS event notification tags and attributes
When Amazon RDS sends an event notification to Amazon Simple Notification Service (SNS) or Amazon EventBridge, the notification contains message attributes and event tags. RDS sends the message attributes separately along with the message, while the event tags are in the body of the message. Use the message attributes and the Amazon RDS tags to add metadata to your resources. You can modify these tags with your own notations about the DB instances. For more information about tagging Amazon RDS resources, see [Tagging Amazon RDS resources](USER_Tagging.md).
By default, the Amazon SNS and Amazon EventBridge receives every message sent to them. SNS and EventBridge can filter the message and send the notifications to the preferred communication mode, such as an email, a text message, or a call to an HTTP endpoint.
**Note**
The notification sent in an email or a text message will not have event tags.
The following table shows the message attributes for RDS events sent to the topic subscriber.
| Amazon RDS event attribute | Description |
| --- | --- |
| EventID | Identifier for the RDS event message, for example, RDS-EVENT-0006. |
| Resource | The ARN identifier for the resource emitting the event, for example, `arn:aws:rds:ap-southeast-2:123456789012:db:database-1`. |
The RDS tags provide data about the resource that was affected by the service event. RDS adds the current state of the tags in the message body when the notification is sent to SNS or EventBridge.
For more information about filtering message attributes for SNS, see [Amazon SNS message filtering](https://docs.aws.amazon.com/sns/latest/dg/sns-message-filtering.html) in the *Amazon Simple Notification Service Developer Guide*.
For more information about filtering event tags for EventBridge, see [ Comparison operators for use in event patterns in Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-patterns-content-based-filtering.html) in the *Amazon EventBridge User Guide*.
For more information about filtering payload-based tags for SNS, see [Introducing payload-based message filtering for Amazon SNS](https://aws.amazon.com/blogs/compute/introducing-payload-based-message-filtering-for-amazon-sns/)
# Listing Amazon RDS event notification subscriptions
You can list your current Amazon RDS event notification subscriptions.
## 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/](https://console.aws.amazon.com/rds/).
1. In the navigation pane, choose **Event subscriptions**. The **Event subscriptions** pane shows all your event notification subscriptions.
![\[List DB event notification subscriptions\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/EventNotification-ListSubs.png)
## AWS CLI
To list your current Amazon RDS event notification subscriptions, use the AWS CLI [https://docs.aws.amazon.com/cli/latest/reference/rds/describe-event-subscriptions.html](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-event-subscriptions.html) 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 [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeEventSubscriptions.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeEventSubscriptions.html) action.
# 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.
## 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/](https://console.aws.amazon.com/rds/).
1. In the navigation pane, choose **Event subscriptions**.
1. In the **Event subscriptions** pane, choose the subscription that you want to modify and choose **Edit**.
1. Make your changes to the subscription in either the **Target** or **Source** section.
1. Choose **Edit**. The Amazon RDS console indicates that the subscription is being modified.
![\[List DB event notification subscriptions\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/EventNotification-Modify2.png)
## AWS CLI
To modify an Amazon RDS event notification subscription, use the AWS CLI [https://docs.aws.amazon.com/cli/latest/reference/rds/modify-event-subscription.html](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-event-subscription.html) command. Include the following required parameter:
+ `--subscription-name`
**Example**
The following code enables `myeventsubscription`.
For Linux, macOS, 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 operation [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyEventSubscription.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyEventSubscription.html). 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.
## 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](USER_Events.Modifying.md).
## AWS CLI
To add a source identifier to an Amazon RDS event notification subscription, use the AWS CLI [https://docs.aws.amazon.com/](https://docs.aws.amazon.com/) 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, macOS, 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 [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_AddSourceIdentifierToSubscription.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_AddSourceIdentifierToSubscription.html). 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.
## 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](USER_Events.Modifying.md).
## AWS CLI
To remove a source identifier from an Amazon RDS event notification subscription, use the AWS CLI [https://docs.aws.amazon.com/cli/latest/reference/rds/remove-source-identifier-from-subscription.html](https://docs.aws.amazon.com/cli/latest/reference/rds/remove-source-identifier-from-subscription.html) 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, macOS, 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 [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RemoveSourceIdentifierFromSubscription.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RemoveSourceIdentifierFromSubscription.html) 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.
## 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](USER_Events.Modifying.md).
![\[List DB event notification categories\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/EventNotification-Categories.png)
## AWS CLI
To list the Amazon RDS event notification categories, use the AWS CLI [https://docs.aws.amazon.com/cli/latest/reference/rds/describe-event-categories.html](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-event-categories.html) 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 [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeEventCategories.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeEventCategories.html) 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.
## 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/](https://console.aws.amazon.com/rds/).
1. In the navigation pane, choose **DB Event Subscriptions**.
1. In the **My DB Event Subscriptions** pane, choose the subscription that you want to delete.
1. Choose **Delete**.
1. The Amazon RDS console indicates that the subscription is being deleted.
![\[Delete an event notification subscription\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/EventNotification-Delete.png)
## AWS CLI
To delete an Amazon RDS event notification subscription, use the AWS CLI [https://docs.aws.amazon.com/cli/latest/reference/rds/delete-event-subscription.html](https://docs.aws.amazon.com/cli/latest/reference/rds/delete-event-subscription.html) command. Include the following required parameter:
+ `--subscription-name`
**Example**
The following example deletes the subscription `myrdssubscription`.
```
aws rds delete-event-subscription --subscription-name myrdssubscription
```
## API
To delete an Amazon RDS event notification subscription, use the RDS API [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DeleteEventSubscription.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DeleteEventSubscription.html) command. Include the following required parameter:
+ `SubscriptionName`
# Creating a rule that triggers on an Amazon RDS event
Using Amazon EventBridge, you can automate AWS services and respond to system events such as application availability issues or resource changes.
**Topics**
+ [Creating rules to send Amazon RDS events to Amazon EventBridge](#rds-cloudwatch-events.sending-to-cloudwatch-events)
+ [Tutorial: Log DB instance state changes using Amazon EventBridge](#log-rds-instance-state)
## Creating rules to send Amazon RDS events to Amazon EventBridge
You can write simple rules to indicate which Amazon RDS events interest you and which automated actions to take when an event matches a rule. You can set a variety of targets, such as an AWS Lambda function or an Amazon SNS topic, which receive events in JSON format. For example, you can configure Amazon RDS to send events to Amazon EventBridge whenever a DB instance is created or deleted. For more information, see the [Amazon CloudWatch Events User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/) and the [Amazon EventBridge User Guide](https://docs.aws.amazon.com/eventbridge/latest/userguide/).
**To create a rule that triggers on an RDS event:**
1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).
1. Under **Events** in the navigation pane, choose **Rules**.
1. Choose **Create rule**.
1. For **Event Source**, do the following:
1. Choose **Event Pattern**.
1. For **Service Name**, choose **Relational Database Service (RDS)**.
1. For **Event Type**, choose the type of Amazon RDS resource that triggers the event. For example, if a DB instance triggers the event, choose **RDS DB Instance Event**.
1. For **Targets**, choose **Add Target** and choose the AWS service that is to act when an event of the selected type is detected.
1. In the other fields in this section, enter information specific to this target type, if any is needed.
1. For many target types, EventBridge needs permissions to send events to the target. In these cases, EventBridge can create the IAM role needed for your event to run:
+ To create an IAM role automatically, choose **Create a new role for this specific resource**.
+ To use an IAM role that you created before, choose **Use existing role**.
1. Optionally, repeat steps 5-7 to add another target for this rule.
1. Choose **Configure details**. For **Rule definition**, type a name and description for the rule.
The rule name must be unique within this Region.
1. Choose **Create rule**.
For more information, see [Creating an EventBridge Rule That Triggers on an Event](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/Create-CloudWatch-Events-Rule.html) in the *Amazon CloudWatch User Guide*.
## Tutorial: Log DB instance state changes using Amazon EventBridge
In this tutorial, you create an AWS Lambda function that logs the state changes for an Amazon RDS instance. You then create a rule that runs the function whenever there is a state change of an existing RDS DB instance. The tutorial assumes that you have a small running test instance that you can shut down temporarily.
**Important**
Don't perform this tutorial on a running production DB instance.
**Topics**
+ [Step 1: Create an AWS Lambda function](#rds-create-lambda-function)
+ [Step 2: Create a rule](#rds-create-rule)
+ [Step 3: Test the rule](#rds-test-rule)
### Step 1: Create an AWS Lambda function
Create a Lambda function to log the state change events. You specify this function when you create your rule.
**To create a Lambda function**
1. Open the AWS Lambda console at [https://console.aws.amazon.com/lambda/](https://console.aws.amazon.com/lambda/).
1. If you're new to Lambda, you see a welcome page. Choose **Get Started Now**. Otherwise, choose **Create function**.
1. Choose **Author from scratch**.
1. On the **Create function** page, do the following:
1. Enter a name and description for the Lambda function. For example, name the function **RDSInstanceStateChange**.
1. In **Runtime**, select **Node.js 16x**.
1. For **Architecture**, choose **x86\$164**.
1. For **Execution role**, do either of the following:
+ Choose **Create a new role with basic Lambda permissions**.
+ For **Existing role**, choose **Use an existing role**. Choose the role that you want to use.
1. Choose **Create function**.
1. On the **RDSInstanceStateChange** page, do the following:
1. In **Code source**, select **index.js**.
1. In the **index.js** pane, delete the existing code.
1. Enter the following code:
```
console.log('Loading function');
exports.handler = async (event, context) => {
console.log('Received event:', JSON.stringify(event));
};
```
1. Choose **Deploy**.
### Step 2: Create a rule
Create a rule to run your Lambda function whenever you launch an Amazon RDS instance.
**To create the EventBridge rule**
1. Open the Amazon EventBridge console at [https://console.aws.amazon.com/events/](https://console.aws.amazon.com/events/).
1. In the navigation pane, choose **Rules**.
1. Choose **Create rule**.
1. Enter a name and description for the rule. For example, enter **RDSInstanceStateChangeRule**.
1. Choose **Rule with an event pattern**, and then choose **Next**.
1. For **Event source**, choose **AWS events or EventBridge partner events**.
1. Scroll down to the **Event pattern** section.
1. For **Event source**, choose **AWS services**.
1. For **AWS service**, choose **Relational Database Service (RDS)**.
1. For **Event type**, choose **RDS DB Instance Event**.
1. Leave the default event pattern. Then choose **Next**.
1. For **Target types**, choose **AWS service**.
1. For **Select a target**, choose **Lambda function**.
1. For **Function**, choose the Lambda function that you created. Then choose **Next**.
1. In **Configure tags**, choose **Next**.
1. Review the steps in your rule. Then choose **Create rule**.
### Step 3: Test the rule
To test your rule, shut down an RDS DB instance. After waiting a few minutes for the instance to shut down, verify that your Lambda function was invoked.
**To test your rule by stopping a DB instance**
1. Open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).
1. Stop an RDS DB instance.
1. Open the Amazon EventBridge console at [https://console.aws.amazon.com/events/](https://console.aws.amazon.com/events/).
1. In the navigation pane, choose **Rules**, choose the name of the rule that you created.
1. In **Rule details**, choose **Monitoring**.
You are redirected to the Amazon CloudWatch console. If you are not redirected, click **View the metrics in CloudWatch**.
1. In **All metrics**, choose the name of the rule that you created.
The graph should indicate that the rule was invoked.
1. In the navigation pane, choose **Log groups**.
1. Choose the name of the log group for your Lambda function (**/aws/lambda/*function-name***).
1. Choose the name of the log stream to view the data provided by the function for the instance that you launched. You should see a received event similar to the following:
```
{
"version": "0",
"id": "12a345b6-78c9-01d2-34e5-123f4ghi5j6k",
"detail-type": "RDS DB Instance Event",
"source": "aws.rds",
"account": "111111111111",
"time": "2021-03-19T19:34:09Z",
"region": "us-east-1",
"resources": [
"arn:aws:rds:us-east-1:111111111111:db:testdb"
],
"detail": {
"EventCategories": [
"notification"
],
"SourceType": "DB_INSTANCE",
"SourceArn": "arn:aws:rds:us-east-1:111111111111:db:testdb",
"Date": "2021-03-19T19:34:09.293Z",
"Message": "DB instance stopped",
"SourceIdentifier": "testdb",
"EventID": "RDS-EVENT-0087"
}
}
```
For more examples of RDS events in JSON format, see [Overview of events for Amazon RDS](working-with-events.md#rds-cloudwatch-events.sample).
1. (Optional) When you're finished, you can open the Amazon RDS console and start the instance that you stopped.
# 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.
**Topics**
+ [DB cluster events](#USER_Events.Messages.cluster)
+ [DB cluster snapshot events](#USER_Events.Messages.cluster-snapshot)
+ [DB instance events](#USER_Events.Messages.instance)
+ [DB parameter group events](#USER_Events.Messages.parameter-group)
+ [DB security group events](#USER_Events.Messages.security-group)
+ [DB snapshot events](#USER_Events.Messages.snapshot)
+ [RDS Proxy events](#USER_Events.Messages.rds-proxy)
+ [Blue/green deployment events](#USER_Events.Messages.BlueGreenDeployments)
+ [Custom engine version events](#USER_Events.Messages.CEV)
## DB cluster events
The following table shows the event category and a list of events when a DB cluster is the source type.
For more information about Multi-AZ DB cluster deployments, see [Multi-AZ DB cluster deployments for Amazon RDS](multi-az-db-clusters-concepts.md).
| Category | RDS event ID | Message | Notes |
| --- | --- | --- | --- |
| configuration change | RDS-EVENT-0016 | Reset master credentials. | None |
| creation | RDS-EVENT-0170 | DB cluster created. | 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: *name*. | None |
| failover | RDS-EVENT-0071 | Completed failover to DB instance: *name*. | None |
| failover | RDS-EVENT-0072 | Started same AZ failover to DB instance: *name*. | None |
| failover | RDS-EVENT-0073 | Started cross AZ failover to DB instance: *name*. | None |
| failure | RDS-EVENT-0354 | You can't create the DB cluster because of incompatible resources. *message*. | The *message* includes details about the failure. |
| failure | RDS-EVENT-0355 | The DB cluster can't be created because of insufficient resource limits. *message*. | The *message* includes details about the failure. |
| 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-0174 | Database cluster is in a state that cannot be upgraded. | None |
| 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\$1number* version upgrade started. Cluster remains online. | 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-0290 | Database cluster has been patched: source version *version\$1number* => *new\$1version\$1number*. | None |
| maintenance | RDS-EVENT-0410 | The pre-check started for the database cluster engine version upgrade. | None |
| maintenance | RDS-EVENT-0412 | The pre-check for the database cluster engine version upgrade failed or timed out. | None |
| maintenance | RDS-EVENT-0413 | The DB cluster pre-upgrade tasks are in progress. | None |
| maintenance | RDS-EVENT-0414 | The DB cluster post-upgrade tasks are in progress. | None |
| maintenance | RDS-EVENT-0417 | Database cluster engine version upgrade started. | None |
| notification | RDS-EVENT-0172 | Renamed cluster from *name* to *name*. | None |
| read replica | RDS-EVENT-0411 | The pre-check finished for the database cluster engine version upgrade. | None |
## 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.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.Messages.html)
## 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: *message*. | An error has occurred while restarting MySQL. |
| availability | RDS-EVENT-0221 | 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. | None |
| availability | RDS-EVENT-0222 | Free storage capacity for DB instance *name* is low at *percentage* of the allocated storage [Allocated storage: *amount*, Free storage: *amount*]. The database will be shut down to prevent corruption if free storage is lower than *amount*. You can increase the allocated storage to address this issue. | Applies only to RDS for MySQL when a DB instance consumes more than 90% of the allocated storage. Monitor the storage space for a DB instance using the Free Storage Space metric. For more information, see [Amazon RDS DB instance storage](CHAP_Storage.md). |
| availability | RDS-EVENT-0330 | The free storage capacity of the dedicated transaction log volume is too low for DB instance *name*. The log volume free storage is *percentage* of the allocated storage. [Allocated storage: *amount*, Free storage: *amount*] The database will be shut down to prevent corruption if the free storage is lower than *amount*. You can disable the dedicated transaction log volume to resolve this issue. | For more information, see [Dedicated log volume (DLV)](CHAP_Storage.md#CHAP_Storage.dlv). |
| availability | RDS-EVENT-0331 | The free storage capacity of the dedicated transaction log volume is too low for DB instance *name*. The log volume free storage is *percentage* of the provisioned storage. [Provisioned Storage: *amount*, Free Storage: *amount*] You can disable the dedicated transaction log volume to resolve this issue. | For more information, see [Dedicated log volume (DLV)](CHAP_Storage.md#CHAP_Storage.dlv). |
| availability | RDS-EVENT-0396 | Amazon RDS has scheduled a reboot for this read replica in this instance's next maintenance window after internal user password rotation. | None |
| availability | RDS-EVENT-0419 | Amazon RDS has been unable to access the KMS encryption key for database instance *name*. This database will be placed into an inaccessible state. Please refer to the troubleshooting section in the Amazon RDS documentation for further details. | None |
| backup | RDS-EVENT-0001 | Backing up DB instance. | None |
| backup | RDS-EVENT-0002 | Finished DB instance backup. | None |
| backup | RDS-EVENT-0086 | We are unable to associate the option group *name* with the database instance *name*. Confirm that option group *name* is supported on your DB instance class and configuration. If so, verify all option group settings and retry. | For more information see [Working with option groups](USER_WorkingWithOptionGroups.md). |
| configuration change | RDS-EVENT-0011 | Updated to use DBParameterGroup *name*. | 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-0016 | Reset master credentials. | None |
| configuration change | RDS-EVENT-0017 | Finished applying modification to allocated storage. | None |
| configuration change | RDS-EVENT-0018 | Applying modification to allocated storage. | None |
| configuration change | RDS-EVENT-0024 | Applying modification to convert to a Multi-AZ DB instance. | None |
| configuration change | RDS-EVENT-0025 | Finished applying modification to convert to a Multi-AZ DB instance. | None |
| configuration change | RDS-EVENT-0028 | Disabled automated backups. | None |
| configuration change | RDS-EVENT-0029 | Finished applying modification to convert to a standard (Single-AZ) DB instance. | None |
| configuration change | RDS-EVENT-0030 | Applying modification to convert to a standard (Single-AZ) DB instance. | None |
| configuration change | RDS-EVENT-0032 | Enabled automated backups. | None |
| configuration change | RDS-EVENT-0033 | There are *number* users matching the master username; only resetting the one not tied to a specific host. | None |
| configuration change | RDS-EVENT-0067 | Unable to reset your password. Error information: *message*. | None |
| configuration change | RDS-EVENT-0078 | Monitoring Interval changed to *number*. | The Enhanced Monitoring configuration has been changed. |
| configuration change | RDS-EVENT-0092 | Finished updating DB parameter group. | None |
| configuration change | RDS-EVENT-0217 | Applying autoscaling-initiated modification to allocated storage. | None |
| configuration change | RDS-EVENT-0218 | Finished applying autoscaling-initiated modification to allocated storage. | None |
| configuration change | RDS-EVENT-0295 | Storage configuration upgrade started. | None |
| configuration change | RDS-EVENT-0296 | Storage configuration upgrade completed. | None |
| configuration change | RDS-EVENT-0332 | The dedicated log volume is disabled. | For more information, see [Dedicated log volume (DLV)](CHAP_Storage.md#CHAP_Storage.dlv). |
| configuration change | RDS-EVENT-0333 | Disabling the dedicated log volume has started. | For more information, see [Dedicated log volume (DLV)](CHAP_Storage.md#CHAP_Storage.dlv). |
| configuration change | RDS-EVENT-0334 | Enabling the dedicated log volume has started. | For more information, see [Dedicated log volume (DLV)](CHAP_Storage.md#CHAP_Storage.dlv). |
| configuration change | RDS-EVENT-0335 | The dedicated log volume is enabled. | For more information, see [Dedicated log volume (DLV)](CHAP_Storage.md#CHAP_Storage.dlv). |
| configuration change | RDS-EVENT-0383 | *engine version* doesn't support the memcached plugin. RDS will continue upgrading your DB instance and remove this plugin. | Starting with MySQL 8.3.0, the memcached plugin isn't supported. For more information, see [Changes in MySQL 8.3.0 (2024-01-16, Innovation Release)](https://dev.mysql.com/doc/relnotes/mysql/8.3/en/news-8-3-0.html). |
| creation | RDS-EVENT-0005 | DB instance created. | None |
| deletion | RDS-EVENT-0003 | DB instance deleted. | None |
| failover | RDS-EVENT-0013 | Multi-AZ instance failover started. | A Multi-AZ failover that resulted in the promotion of a standby DB instance has started. |
| failover | RDS-EVENT-0015 | Multi-AZ failover to standby complete - DNS propagation may take a few minutes. | A Multi-AZ failover that resulted in the promotion of a standby DB instance is complete. It may take several minutes for the DNS to transfer to the new primary DB instance. |
| failover | RDS-EVENT-0034 | Abandoning user requested failover since a failover recently occurred on the database instance. | Amazon RDS isn't attempting a requested failover because a failover recently occurred on the DB instance. |
| failover | RDS-EVENT-0049 | Multi-AZ instance failover completed. | None |
| failover | RDS-EVENT-0050 | Multi-AZ instance activation started. | A Multi-AZ activation has started after a successful DB instance recovery. This event occurs if Amazon RDS promotes the primary DB instance to the same AZ as the previous primary DB instance. |
| failover | RDS-EVENT-0051 | Multi-AZ instance activation completed. | A Multi-AZ activation is complete. Your database should be accessible now. |
| failover | RDS-EVENT-0065 | Recovered from partial failover. | None |
| failure | RDS-EVENT-0031 | DB instance put into *name* state. RDS recommends that you initiate a point-in-time-restore. | 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 | 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 | RDS-EVENT-0036 | 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 | RDS-EVENT-0058 | The Statspack installation failed. *message*. | Error while creating Oracle Statspack user account `PERFSTAT`. Drop the account before you add the `STATSPACK` option. |
| 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](USER_Monitoring.OS.Enabling.md#USER_Monitoring.OS.IAMRole). |
| failure | RDS-EVENT-0080 | 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](USER_Monitoring.OS.Enabling.md#USER_Monitoring.OS.IAMRole). |
| failure | RDS-EVENT-0081 | Amazon RDS has been unable to create credentials for *name* option. This is due to the *name* IAM role not being configured correctly in your account. Please refer to the troubleshooting section in the Amazon RDS documentation for further details. | 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](SQLServer.Procedural.Importing.Native.Enabling.md). |
| failure | RDS-EVENT-0165 | The RDS Custom DB instance is outside the support perimeter. | It's your responsibility to fix configuration issues that put your RDS Custom DB instance into the `unsupported-configuration` state. If the issue is with the AWS infrastructure, you can use the console or the AWS CLI to fix it. If the issue is with the operating system or the database configuration, you can log in to the host to fix it.For more information, see [RDS Custom support perimeter](custom-concept.md#custom-troubleshooting.support-perimeter). |
| failure | RDS-EVENT-0188 | The DB instance is in a state that can't be upgraded. *message* | Amazon RDS was unable to upgrade a MySQL DB instance because of incompatibilities related to the data dictionary. The DB instance was rolled back to MySQL version 5.7 because an attempted upgrade to version 8.0 failed, or rolled back to MySQL version 8.0 because an attempted upgrade to version 8.4 failed. For more information, see [Rollback after failure to upgrade](USER_UpgradeDBInstance.MySQL.Major.md#USER_UpgradeDBInstance.MySQL.Major.RollbackAfterFailure). |
| failure | RDS-EVENT-0219 | DB instance is in an invalid state. No actions are necessary. Autoscaling will retry later. | None |
| failure | RDS-EVENT-0220 | DB instance is in the cooling-off period for a previous scale storage operation. We're optimizing your DB instance. This takes at least 6 hours. No actions are necessary. Autoscaling will retry after the cooling-off period. | None |
| failure | RDS-EVENT-0223 | Storage autoscaling is unable to scale the storage for the reason: *reason*. | None |
| failure | RDS-EVENT-0224 | Storage autoscaling has triggered a pending scale storage task that will reach or exceed the maximum storage threshold. Increase the maximum storage threshold. | None |
| failure | RDS-EVENT-0237 | DB instance has a storage type that's currently unavailable in the Availability Zone. Autoscaling will retry later. | None |
| 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-0278 | The DB instance creation failed. *message* | The *message* includes details about the failure. |
| failure | RDS-EVENT-0279 | The promotion of the RDS Custom read replica failed. *message* | The *message* includes details about the failure. |
| failure | RDS-EVENT-0280 | RDS Custom couldn't upgrade the DB instance because the pre-check failed. *message* | The *message* includes details about the failure. |
| failure | RDS-EVENT-0281 | RDS Custom couldn't modify the DB instance because the pre-check failed. *message* | The *message* includes details about the failure. |
| failure | RDS-EVENT-0282 | RDS Custom couldn't modify the DB instance because the Elastic IP permissions aren't correct. Please confirm the Elastic IP address is tagged with `AWSRDSCustom`. | None |
| failure | RDS-EVENT-0283 | RDS Custom couldn't modify the DB instance because the Elastic IP limit has been reached in your account. Release unused Elastic IPs or request a quota increase for your Elastic IP address limit. | None |
| failure | RDS-EVENT-0284 | RDS Custom couldn't convert the instance to high availability because the pre-check failed. *message* | The *message* includes details about the failure. |
| failure | RDS-EVENT-0285 | RDS Custom couldn't create a final snapshot for the DB instance because *message*. | The *message* includes details about the failure. |
| failure | RDS-EVENT-0421 | RDS Custom couldn't convert the DB instance to a Multi-AZ deployment: *message*. The instance will remain a Single-AZ deployment. See the RDS User Guide for information about Multi-AZ deployments for RDS Custom for Oracle. | The *message* includes details about the failure. |
| failure | RDS-EVENT-0306 | Storage configuration upgrade failed. Please retry the upgrade. | None |
| failure | RDS-EVENT-0315 | Unable to move incompatible-network database, *name*, to the available status: *message* | The database networking configuration is invalid. The database could not be moved from incompatible-network to available. |
| failure | RDS-EVENT-0328 | Failed to join a host to a domain. Domain membership status for instance *instancename* has been set to Failed. | None |
| failure | RDS-EVENT-0329 | Failed to join a host to your domain. During the domain join process, Microsoft Windows returned the error code *message*. Verify your network and permission configurations and issue a `modify-db-instance` request to re-attempt the domain join. | When using a self-managed Active Directory, see [Troubleshooting self-managed Active Directory](USER_SQLServer_SelfManagedActiveDirectory.TroubleshootingSelfManagedActiveDirectory.md). |
| failure | RDS-EVENT-0353 | The DB instance can't be created because of insufficient resource limits. *message*. | The *message* includes details about the failure. |
| failure | RDS-EVENT-0356 | RDS was unable to configure the Kerberos endpoint in your domain. This might prevent Kerberos authentication for your DB instance. Verify the network configuration between your DB instance and domain controllers. | None |
| failure | RDS-EVENT-0418 | Amazon RDS is unable to access the KMS encryption key for database instance *name*. This is likely due to the key being disabled or Amazon RDS being unable to access it. If this continues the database will be placed into an inaccessible state. Please refer to the troubleshooting section in the Amazon RDS documentation for further details. | None |
| failure | RDS-EVENT-0420 | Amazon RDS can now successfully access the KMS encryption key for database instance *name*. | None |
| 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](https://aws.amazon.com/rds/faqs). You can monitor the storage space for a DB instance using the **Free Storage Space** metric. |
| low storage | RDS-EVENT-0089 | 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 | RDS-EVENT-0227 | 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 | 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 |
| maintenance | RDS-EVENT-0264 | The pre-check started for the DB engine version upgrade. | None |
| maintenance | RDS-EVENT-0265 | The pre-check finished for the DB engine version upgrade. | None |
| maintenance | RDS-EVENT-0266 | The downtime started for the DB instance. | None |
| maintenance | RDS-EVENT-0267 | The engine version upgrade started. | None |
| maintenance | RDS-EVENT-0268 | The engine version upgrade finished. | None |
| maintenance | RDS-EVENT-0269 | The post-upgrade tasks are in progress. | None |
| maintenance | RDS-EVENT-0270 | The DB engine version upgrade failed. The engine version upgrade rollback succeeded. | None |
| maintenance | RDS-EVENT-0398 | Waiting for the DB engine version upgrade to finish on the primary DB instance. | Emitted on a read replica during a major engine version upgrade. |
| maintenance | RDS-EVENT-0399 | Waiting for the DB engine version upgrade to finish on the read replicas. | Emitted on source DB engine during a major engine version upgrade. |
| maintenance | RDS-EVENT-0422 | RDS will replace the host of DB instance *name* due to a pending maintenance action. | None |
| maintenance, failure | RDS-EVENT-0195 | *message* | The update of the Oracle time zone file failed. For more information, see [Oracle time zone file autoupgrade](Appendix.Oracle.Options.Timezone-file-autoupgrade.md). |
| maintenance, notification | RDS-EVENT-0191 | A new version of the time zone file is available for update. | If you update your RDS for Oracle DB 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](Appendix.Oracle.Options.Timezone-file-autoupgrade.md). |
| maintenance, notification | RDS-EVENT-0192 | The update of your time zone file has started. | The upgrade of your Oracle time zone file has begun. For more information, see [Oracle time zone file autoupgrade](Appendix.Oracle.Options.Timezone-file-autoupgrade.md). |
| maintenance, notification | RDS-EVENT-0193 | No update is available for the current time zone file version. | Your Oracle DB instance is using latest time zone file version, and either of the following statements is true: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.Messages.html) For more information, see [Oracle time zone file autoupgrade](Appendix.Oracle.Options.Timezone-file-autoupgrade.md). |
| maintenance, notification | RDS-EVENT-0194 | The update of your time zone file has finished. | The update of your Oracle time zone file has completed. For more information, see [Oracle time zone file autoupgrade](Appendix.Oracle.Options.Timezone-file-autoupgrade.md). |
| notification | RDS-EVENT-0044 | *message* | 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-0054 | *message* | 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 RDS for MySQL](MySQL.Concepts.FeatureSupport.md#MySQL.Concepts.Storage). |
| notification | RDS-EVENT-0055 | *message* | 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](CHAP_BestPractices.md#CHAP_BestPractices.DiskPerformance). |
| notification | RDS-EVENT-0056 | *message* | 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](CHAP_BestPractices.md#CHAP_BestPractices.DiskPerformance). |
| notification | RDS-EVENT-0064 | The TDE encryption key was rotated successfully. | For information about recommended best practices, see [Amazon RDS basic operational guidelines](CHAP_BestPractices.md#CHAP_BestPractices.DiskPerformance). |
| notification | RDS-EVENT-0084 | Unable to convert the DB instance to Multi-AZ: *message*. | 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](USER_SQLServerMultiAZ.md). |
| notification | RDS-EVENT-0087 | DB instance stopped. | None |
| notification | RDS-EVENT-0088 | DB instance started. | None |
| notification | RDS-EVENT-0154 | DB instance is being started due to it exceeding the maximum allowed time being stopped. | None |
| notification | RDS-EVENT-0157 | Unable to modify the DB instance class. *message*. | 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](CHAP_SQLServer.md#SQLServer.Concepts.General.FeatureSupport.Limits). |
| notification | RDS-EVENT-0158 | Database instance is in a state that cannot be upgraded: *message*. | None |
| notification | RDS-EVENT-0167 | *message* | The RDS Custom support perimeter configuration has changed. |
| notification | RDS-EVENT-0189 | The gp2 burst balance credits for the RDS database instance are low. To resolve this issue, reduce IOPS usage or modify your storage settings to enable higher performance. | The gp2 burst balance credits for the RDS database instance are low. To resolve this issue, reduce IOPS usage or modify your storage settings to enable higher performance. For more information, see [I/O credits and burst performance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html#EBSVolumeTypes_gp2) in the *Amazon Elastic Compute Cloud User Guide*. |
| notification | RDS-EVENT-0225 | Allocated storage size *amount* GB is approaching the maximum storage threshold *amount* GB. Increase the maximum storage threshold. | This event is invoked when the allocated storage reaches 80% of the maximum storage threshold. To avoid the event, increase the maximum storage threshold. |
| notification | RDS-EVENT-0231 | Your DB instance's storage modification encountered an internal error. The modification request is pending and will be retried later. | 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. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.Messages.html) |
| notification | RDS-EVENT-0253 | The database is using the doublewrite buffer. *message*. For more information see the RDS Optimized Writes for *name* documentation. | RDS Optimized Writes is incompatible with the instance storage configuration. For more information, see [Improving write performance with RDS Optimized Writes for MySQL](rds-optimized-writes.md) and [Improving write performance with Amazon RDS Optimized Writes for MariaDB](rds-optimized-writes-mariadb.md). You can perform storage configuration upgrade to enable Optimized Writes by [Creating a blue/green deployment](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments-creating.html). |
| notification | RDS-EVENT-0297 | The storage configuration for DB instance *name* supports a maximum size of 16384 GiB. Perform a storage configuration upgrade to support storage sizes greater than 16384 GiB. | You cannot increase the allocated storage size of the DB instance beyond 16384 GiB. To overcome this limitation, perform a storage configuration upgrade. For more information, see [Upgrading the storage file system for a DB instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIOPS.StorageTypes.html#USER_PIOPS.UpgradeFileSystem). |
| notification | RDS-EVENT-0298 | The storage configuration for DB instance *name* supports a maximum table size of 2048 GiB. Perform a storage configuration upgrade to support table sizes greater than 2048 GiB. | RDS MySQL and MariaDB instances with this limitation cannot have a table size exceeding 2048 GiB. To overcome this limitation, perform a storage configuration upgrade. For more information, see [Upgrading the storage file system for a DB instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIOPS.StorageTypes.html#USER_PIOPS.UpgradeFileSystem). |
| notification | RDS-EVENT-0327 | Amazon RDS could not find the secret *SECRET ARN*. *message.* | None |
| notification | RDS-EVENT-0365 | Timezone files were updated. Restart your RDS instance for the changes to take effect. | None |
| notification | RDS-EVENT-0385 | Cluster topology is updated. | There are DNS changes to the DB cluster for the DB instance. This includes when new DB instances are added or deleted, or there's a failover. |
| notification | RDS-EVENT-0403 | A database workload is causing the system to run critically low on memory. To help mitigate the issue, RDS automatically set the value of innodb\$1buffer\$1pool\$1size to *amount*. | Applies only to RDS for MySQL and RDS for MariaDB DB instances. |
| notification | RDS-EVENT-0404 | A database workload is causing the system to run critically low on memory. To help mitigate the issue, RDS automatically set the value of shared\$1buffers to *amount*. | Applies only to RDS for PostgreSQL DB instances. |
| read replica | RDS-EVENT-0045 | Replication has stopped. | This message appears when there is an error during replication. To determine the type of error, see [ Troubleshooting a MySQL read replica problem](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.Troubleshooting.html). |
| 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 `RDS-EVENT-0045` notification, then replication has resumed following an error or after replication was stopped. |
| read replica | RDS-EVENT-0057 | Replication streaming has been terminated. | None |
| read replica | RDS-EVENT-0062 | Replication for the Read Replica has been manually stopped. | None |
| read replica | RDS-EVENT-0063 | Replication from Non RDS instance has been reset. | None |
| read replica | RDS-EVENT-0202 | Read replica creation failed. | None |
| read replica | RDS-EVENT-0233 | The Switchover to the read replica started. | None |
| read replica | RDS-EVENT-0357 | Replication channel *name* started. | For information about replication channels, see [Configuring multi-source-replication for Amazon RDS for MySQL](mysql-multi-source-replication.md). |
| read replica | RDS-EVENT-0358 | Replication channel *name* stopped. | For information about replication channels, see [Configuring multi-source-replication for Amazon RDS for MySQL](mysql-multi-source-replication.md). |
| read replica | RDS-EVENT-0359 | Replication channel *name* was manually stopped. | For information about replication channels, see [Configuring multi-source-replication for Amazon RDS for MySQL](mysql-multi-source-replication.md). |
| read replica | RDS-EVENT-0360 | Replication channel *name* was reset. | For information about replication channels, see [Configuring multi-source-replication for Amazon RDS for MySQL](mysql-multi-source-replication.md). |
| read replica | RDS-EVENT-0415 | The upgrade process resumed replication on the read replica. | None |
| read replica | RDS-EVENT-0416 | The upgrade process stopped replication on the read replica. | 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: *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 | 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. | This message indicates that Amazon RDS has prepared your DB instance to initiate a failover to the secondary instance if necessary. |
| recovery | RDS-EVENT-0066 | Instance will be degraded while mirroring is reestablished: *message*. | 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. (: [,...])" |
| recovery | RDS-EVENT-0166 | *message* | The RDS Custom DB instance is inside the support perimeter. |
| 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 *name* to *name*. | The DB instance has been restored from a point-in-time backup. |
| security | RDS-EVENT-0068 | Decrypting hsm partition password to update instance. | RDS is decrypting the AWS CloudHSM partition password to make updates to the DB instance. For more information see [Oracle Database Transparent Data Encryption (TDE) with AWS CloudHSM](https://docs.aws.amazon.com/cloudhsm/latest/userguide/oracle-tde.html) in the *AWS CloudHSM User Guide*. |
| 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 update is available. A new, minor version, operating system update is available for your DB instance. For information about applying updates, see [Operating system updates for RDS DB instances](USER_UpgradeDBInstance.Maintenance.md#OS_Updates). |
| maintenance | RDS-EVENT-0425 | Amazon RDS can't perform the OS upgrade because there are no available IP addresses in the specified subnets. Choose subnets with available IP addresses and try again. | None |
| maintenance | RDS-EVENT-0429 | Amazon RDS can't perform the OS upgrade because of insufficient capacity available for the *type* instance type in the *zone* Availability Zone | None |
| maintenance | RDS-EVENT-0501 | Amazon RDS DB instance's server certificate requires rotation through a pending maintenance action. | DB instance's server certificate requires rotation through a pending maintenance action. Amazon RDS reboots your database during this maintenance to complete the certificate rotation. To schedule this maintenance, go to the **Maintenance & backups** tab and choose **Apply now** or **Schedule for next maintenance window**. If the change is not scheduled, Amazon RDS automatically applies it in your mainteance window on the auto apply date shown in your maintenance action. |
| maintenance | RDS-EVENT-0502 | Amazon RDS has scheduled a server certificate rotation for DB instance during the next maintenance window. This maintenance will require a database reboot. | None |
## 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 *name* to *value* with apply method *method*. | 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](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/vpc-migrate.html) in the *Amazon EC2 User Guide* and the blog [ EC2-Classic Networking is Retiring – Here’s How to Prepare](https://aws.amazon.com/blogs/aws/ec2-classic-is-retiring-heres-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 *user*. | The security group owned by *user* doesn't exist. The authorization for the security group has been revoked because it is invalid. |
## DB snapshot events
The following table shows the event category and a list of events when a DB snapshot is the source type.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.Messages.html)
## 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 *name*. | None |
| configuration change | RDS-EVENT-0207 | RDS modified the end point of the DB proxy *name*. | 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 *name*. | None |
| configuration change | RDS-EVENT-0214 | RDS detected deletion of DB instance *name* and automatically removed it from target group *name* of DB proxy *name*. | None |
| configuration change | RDS-EVENT-0215 | RDS detected deletion of DB cluster *name* and automatically removed it from target group *name* of DB proxy *name*. | None |
| creation | RDS-EVENT-0203 | RDS created DB proxy *name*. | None |
| creation | RDS-EVENT-0206 | RDS created endpoint *name* for DB proxy *name*. | None |
| deletion | RDS-EVENT-0205 | RDS deleted DB proxy *name*. | None |
| deletion | RDS-EVENT-0208 | RDS deleted endpoint *name* for DB proxy *name*. | None |
| failure | RDS-EVENT-0243 | 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](rds-proxy-network-prereqs.md#rds-proxy-network-prereqs.plan-ip-address). |
| failure | RDS-EVENT-0275 | 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 |
## 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](blue-green-deployments.md).
| 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 *reason*. | None |
| deletion | RDS-EVENT-0246 | Blue/green deployment deleted. | None |
| notification | RDS-EVENT-0247 | Switchover from *blue* to *green* started. | 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-0250 | Switchover from primary/read replica *blue* to *green* started. | None |
| notification | RDS-EVENT-0251 | Switchover from primary/read replica *blue* to *green* completed. Renamed *blue* to *blue-old* and *green* to *blue*. | None |
| failure | RDS-EVENT-0252 | Switchover from primary/read replica *blue* to *green* was canceled due to *reason*. | None |
| notification | RDS-EVENT-0307 | Sequence sync for switchover of *blue* to *green* has initiated. Switchover when using sequences may lead to extended downtime. | None |
| notification | RDS-EVENT-0308 | Sequence sync for switchover of *blue* to *green* has completed. | None |
| failure | RDS-EVENT-0310 | Sequence sync for switchover of *blue* to *green* was cancelled because sequences failed to sync. | None |
| notification | RDS-EVENT-0405 | Your storage volumes are being initialized. | None |
| notification | RDS-EVENT-0406 | Your storage volumes have been initialized. | None |
| notification | RDS-EVENT-0409 | *message* | None |
## Custom engine version events
The following table shows the event category and a list of events when a custom engine version is the source type.
| Category | Amazon RDS event ID | Message | Notes |
| --- | --- | --- | --- |
| creation | RDS-EVENT-0316 | Preparing to create custom engine version *name*. The entire creation process may take up to four hours to complete. | None |
| creation | RDS-EVENT-0317 | Creating custom engine version *name*. | None |
| creation | RDS-EVENT-0318 | Validating custom engine version *name*. | None |
| creation | RDS-EVENT-0319 | Custom engine version *name* has been created successfully. | None |
| creation | RDS-EVENT-0320 | RDS can't create custom engine version *name* because of an internal issue. We are addressing the problem and will contact you if necessary. For further assistance, contact [AWS Premium Support/](https://console.aws.amazon.com/support/). | None |
| failure | RDS-EVENT-0198 | Creation failed for custom engine version *name*. *message* | The *message* includes details about the failure, such as missing files. |
| failure | RDS-EVENT-0277 | Failure during deletion of custom engine version *name*. *message* | The *message* includes details about the failure. |
| restoring | RDS-EVENT-0352 | The maximum database count supported for point-in-time restore has changed. | The *message* includes details about the event. |