Amazon Redshift event notifications
Overview
Amazon Redshift uses the Amazon Simple Notification Service (Amazon SNS) to communicate notifications of Amazon Redshift events. You enable notifications by creating an Amazon Redshift event subscription. In the Amazon Redshift subscription, you specify a set of filters for Amazon Redshift events and an Amazon SNS topic. Whenever an event occurs that matches the filter criteria, Amazon Redshift publishes a notification message to the Amazon SNS topic. Amazon SNS then transmits the message to any Amazon SNS consumers that have an Amazon SNS subscription to the topic. The messages sent to the Amazon SNS consumers can be in any form supported by Amazon SNS for an Amazon Region, such as an email, a text message, or a call to an HTTP endpoint. For example, all regions support email notifications, but SMS notifications can only be created in the US East (N. Virginia) Region.
Currently, you can only create an event subscription to an Amazon SNS standard topic (not to an Amazon SNS FIFO topic). For more information, see Amazon SNS event sources in the Amazon Simple Notification Service Developer Guide.
When you create an event notification subscription, you specify one or more event filters. Amazon Redshift sends notifications through the subscription any time an event occurs that matches all of the filter criteria. The filter criteria include source type (such as cluster or snapshot), source ID (such as the name of a cluster or snapshot), event category (such as Monitoring or Security), and event severity (such as INFO or ERROR).
You can easily turn off notification without deleting a subscription by setting the
Enabled radio button to No in the Amazon Web Services Management Console or by
setting the Enabled parameter to false using the Amazon Redshift CLI
or API.
Billing for Amazon Redshift 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, go to Amazon Simple Notification Service pricing
You can also view Amazon Redshift events that have occurred by using the management console. For more information, see Amazon Redshift events.
Subscribing to Amazon Redshift cluster event notifications
You can create an Amazon Redshift event notification subscription so you can be notified when an event occurs for a given cluster, snapshot, security group, or parameter group. The simplest way to create a subscription is with the Amazon SNS console. For information on creating an Amazon SNS topic and subscribing to it, see Getting started with Amazon SNS.
You can create an Amazon Redshift event notification subscription so you can be notified when an event occurs for a given cluster, snapshot, security group, or parameter group. The simplest way to create a subscription is with the Amazon Web Services Management 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 Amazon SNS topic and subscribing to it, see Getting started with Amazon SNS.
An Amazon Redshift event subscription can specify these event criteria:
-
Source type, the values are cluster, snapshot, parameter-groups, and security-groups.
-
Source ID of a resource, such as
my-cluster-1ormy-snapshot-20130823. The ID must be for a resource in the same Amazon Region as the event subscription. -
Event category, the values are Configuration, Management, Monitoring, Security, and Pending
-
Event severity, the values are INFO or ERROR.
The event criteria can be specified independently, except that you must specify a source type before you can specify source IDs in the console. For example, you can specify an event category without having to specify a source type, source ID, or severity. While you can specify source IDs for resources that are not of the type specified in source type, no notifications will be sent for events from those resources. For example, if you specify a source type of cluster and the ID of a security group, none of the events raised by that security group would match the source type filter criteria, so no notifications would be sent for those events.
Amazon Redshift sends a notification for any event that matches all criteria specified in a subscription. Some examples of the sets of events returned:
-
Subscription specifies a source type of cluster, a source ID of my-cluster-1, a category of Monitoring, and a severity of ERROR. The subscription will send notifications for only monitoring events with a severity of ERROR from my-cluster-1.
-
Subscription specifies a source type of cluster, a category of Configuration, and a severity of INFO. The subscription will send notifications for configuration events with a severity of INFO from any Amazon Redshift cluster in the Amazon account.
-
Subscription specifies a category of Configuration, and a severity of INFO. The subscription will send notifications for configuration events with a severity of INFO from any Amazon Redshift resource in the Amazon account.
-
Subscription specifies a severity of ERROR. The subscription will send notifications for all events with a severity of ERROR from any Amazon Redshift resource in the Amazon account.
If you delete or rename an object whose name is referenced as a source ID in an existing subscription, the subscription will remain active, but will have no events to forward from that object. If you later create a new object with the same name as is referenced in the subscription source ID, the subscription will start sending notifications for events from the new object.
Amazon Redshift publishes event notifications to an Amazon SNS topic, which is identified by its Amazon Resource Name (ARN). When you create an event subscription using the Amazon Redshift console, you can either specify an existing Amazon SNS topic, or request that the console create the topic when it creates the subscription. All Amazon Redshift event notifications sent to the Amazon SNS topic are in turn transmitted to all Amazon SNS consumers that are subscribed to that topic. Use the Amazon SNS console to make changes to the Amazon SNS topic, such as adding or removing consumer subscriptions to the topic. For more information about creating and subscribing to Amazon SNS topics, go to Getting started with Amazon Simple Notification Service.
The following sections list all categories and events that you can be notified of. It also provides information about subscribing to and working with Amazon Redshift event subscriptions.
Amazon Redshift Serverless event notifications with Amazon EventBridge
Amazon Redshift Serverless uses Amazon EventBridge to manage event notifications to keep you up-to-date regarding changes in your data warehouse. Amazon EventBridge is a serverless event bus service that you can use to connect your applications with data from a variety of sources. In this case, the event source is Amazon Redshift. Events, which are monitored changes in an environment, are sent to EventBridge from your Amazon Redshift data warehouse automatically. Events are delivered in near-real time.
Capabilities of EventBridge include providing an environment for you to write event rules, which can specify actions to take for specific events. You can also set up targets, which are resources that EventBridge can send an event to. A target can include an API destination, an Amazon CloudWatch log group, and others. For more information about rules, see Amazon EventBridge rules. For more information about targets, see Amazon EventBridge targets.
Events can be classified into severities and categories. The following filters are available:
Resource filtering – Receive messages based on the resource the events are associated with. Resources include a workgroup, a snapshot, and so on.
Time window filtering – Scope events in a specific time period.
Category filtering – Receive event notifications for all events in specified categories.
The following table includes Amazon Redshift Serverless events, with additional metadata:
| Amazon Redshift Category | External Event ID | Event Severity | Message Description |
|---|---|---|---|
|
RateChange |
REDSHIFT-SERVERLESS-EVENT-1001 | INFO | Workgroup base RPU change completed successfully at <time in UTC>. |
|
RateChange |
REDSHIFT-SERVERLESS-EVENT-1002 | ERROR | Workgroup base RPU change failed to complete at <time in UTC>. |
|
Monitoring |
REDSHIFT-SERVERLESS-EVENT-1003 | INFO | The software was updated on your Amazon Redshift Data Warehouse <endpoint name> at <time in UTC>. |
|
Monitoring |
REDSHIFT-SERVERLESS-EVENT-1500 | ERROR | Workgroup <workgroup name> cannot be created or updated because you exceeded your account's limit of Elastic IP addresses. Delete unused Elastic IP addresses or request a limit increase with Amazon EC2. |
|
Monitoring |
REDSHIFT-SERVERLESS-EVENT-1501 | ERROR | Subnet <subnet id> has no available IP addresses. This will prevent the following query types from running successfully on workgroup <workgroup name>: EMR, federated queries, COPY/UNLOAD from Amazon EC2. To correct the issue, free up IPs in your subnet by deleting ENIs. |
|
Monitoring |
REDSHIFT-SERVERLESS-EVENT-1502 | ERROR | Subnet <subnet id> has no available IP addresses. This will prevent the Amazon EMR, Redshift federated queries, Redshift COPY/UNLOAD, Redshift ML query types from running successfully in workgroup <workgroup name>. To correct the issue, free up IPs in your subnet by deleting unused elastic network interfaces (ENIs). |
|
Management |
REDSHIFT-SERVERLESS-EVENT-1008 | INFO | Your Amazon Redshift workgroup <workgroup name> has been created and is ready for use. |
|
Management |
REDSHIFT-SERVERLESS-EVENT-1009 | INFO | Your Amazon Redshift workgroup <workgroup name> was deleted at <time in UTC>. |
|
Monitoring |
REDSHIFT-SERVERLESS-EVENT-1000 | INFO | Snapshot <snapshot name> completed successfully at <time in UTC>. |
|
Management |
REDSHIFT-SERVERLESS-EVENT-1004 | INFO | Restore from snapshot on namespace <namespace name> completed successfully at <time in UTC>. |
|
Management |
REDSHIFT-SERVERLESS-EVENT-1005 | ERROR | Restore from snapshot on namespace <namespace name> failed at <time in UTC>. |
|
Management |
REDSHIFT-SERVERLESS-EVENT-1006 | INFO | Restore from recovery point on namespace <namespace name> completed successfully at <time in UTC>. |
|
Management |
REDSHIFT-SERVERLESS-EVENT-1007 | INFO | Restore from recovery point on namespace <namespace name> failed at <time in UTC>. |
Amazon Redshift event categories and event messages
This section shows the event IDs and categories for each Amazon Redshift source type.
The following table shows the event category and a list of events when a cluster is the source type.
| Amazon Redshift category | Event ID | Event severity | Description |
|---|---|---|---|
|
Configuration |
REDSHIFT-EVENT-1000 | INFO |
The parameter group [parameter group name] was updated at [time]. If you changed only dynamic parameters, associated clusters are being modified now. If you changed static parameters, all updates, including dynamic parameters, will be applied when you reboot the associated clusters. |
|
Configuration |
REDSHIFT-EVENT-1001 | INFO |
Your Amazon Redshift cluster [cluster name] was modified to use parameter group [parameter group name] at [time]. |
|
Configuration |
REDSHIFT-EVENT-1500 | ERROR |
The Amazon VPC [VPC name] does not exist. Your configuration changes for cluster [cluster name] were not applied. Please visit the Amazon Web Services Management Console to correct the issue. |
|
Configuration |
REDSHIFT-EVENT-1501 | ERROR |
The customer subnets [subnet name] you specified for Amazon VPC [VPC name] do not exist or are invalid. Your configuration changes for cluster [cluster name] were not applied. Please visit the Amazon Web Services Management Console to correct the issue. |
|
Configuration |
REDSHIFT-EVENT-1502 | ERROR |
Subnets in cluster subnet group [subnet group name] have no available IP addresses. Cluster [cluster name] could not be created. |
|
Configuration |
REDSHIFT-EVENT-1503 | ERROR |
The Amazon VPC [VPC name] has no internet gateway attached to it. Your configuration changes for cluster [cluster name] were not applied. Please visit the Amazon Web Services Management Console to correct the issue. |
|
Configuration |
REDSHIFT-EVENT-1504 | ERROR |
The HSM for cluster [cluster name] is unreachable. |
|
Configuration |
REDSHIFT-EVENT-1505 | ERROR |
The HSM for cluster [cluster name] cannot be registered. Try a different configuration. |
|
Configuration |
REDSHIFT-EVENT-1506 | ERROR |
Amazon Redshift exceeded your account's elastic network interface limit. Delete up to [maximum number of elastic network interfaces] elastic network interfaces or request a limit increase of the number of network interfaces per Amazon Region with EC2. |
|
Configuration |
REDSHIFT-EVENT-1509 | ERROR |
The Amazon Redshift cluster [cluster name] can't be created because your account's VPC endpoint limit has been reached. Delete unused VPC endpoints or request an increase in the limit of VPC endpoints. For more information, see VPC endpoints in the Amazon VPC User Guide. |
|
Configuration |
REDSHIFT-EVENT-1510 | ERROR |
We have detected that the attempt to load sample data on your Amazon Redshift cluster [cluster name] didn't succeed. To load sample data, first configure your VPC to have access to Amazon S3 buckets, then create a new cluster and load sample data. For more information, see see Enabling enhanced VPC routing in the Amazon Redshift Management Guide. |
|
Configuration |
REDSHIFT-EVENT-1511 | ERROR |
Amazon Redshift cluster [cluster name] cannot be created because you exceeded your account's limit of Elastic IP addresses. Delete unused Elastic IP addresses or request a limit increase with Amazon EC2. |
|
Management |
REDSHIFT-EVENT-2000 | INFO |
Your Amazon Redshift cluster: [cluster name] has been created and is ready for use. |
|
Management |
REDSHIFT-EVENT-2001 | INFO |
Your Amazon Redshift cluster [cluster name] was deleted at [time]. A final snapshot [was / was not] saved. |
| Management | REDSHIFT-EVENT-2002 | INFO |
Your VPC security group [security group name] was updated at [time]. |
|
Management |
REDSHIFT-EVENT-2003 | INFO |
Maintenance started on your Amazon Redshift cluster [cluster name] at [time]. The cluster may not be available during maintenance. |
|
Management |
REDSHIFT-EVENT-2004 | INFO |
Maintenance completed on your Amazon Redshift cluster [cluster name] at [time]. |
|
Management |
REDSHIFT-EVENT-2006 | INFO |
A resize for your Amazon Redshift cluster [cluster name] was started at [time]. Your cluster will be in read-only mode during the resize operation. |
|
Management |
REDSHIFT-EVENT-2007 | INFO |
The resize for your Amazon Redshift cluster [cluster name] is in progress. Your cluster is in read-only mode. |
|
Management |
REDSHIFT-EVENT-2008 | INFO |
Your restore operation to create a new Amazon Redshift cluster [cluster name] snapshot [snapshot name] was started at [time]. To monitor restore progress, please visit the Amazon Web Services Management Console. |
|
Management |
REDSHIFT-EVENT-2013 | INFO |
Your Amazon Redshift cluster [cluster name] was renamed at [time]. |
|
Management |
REDSHIFT-EVENT-2014 | INFO |
A table restore request for Amazon Redshift cluster [cluster name] has been received. |
|
Management |
REDSHIFT-EVENT-2015 | INFO |
Table restore was cancelled for Amazon Redshift cluster [cluster name] at [time]. |
|
Management |
REDSHIFT-EVENT-2016 | INFO |
Replacement of your Amazon Redshift cluster [cluster name] was started at [time]. |
|
Management |
REDSHIFT-EVENT-2017 | INFO |
Customer initiated maintenance started on your Amazon Redshift cluster [cluster name] at [time]. The cluster may not be available during maintenance. |
|
Management |
REDSHIFT-EVENT-2018 | INFO |
Customer initiated maintenance completed on your Amazon Redshift cluster [cluster name] at [time]. |
|
Management |
REDSHIFT-EVENT-2019 | ERROR |
Customer initiated maintenance failed on your Amazon Redshift cluster [cluster name] at [time]. Returning the cluster back to its original state. |
|
Management |
REDSHIFT-EVENT-2020 | INFO |
Your Amazon Redshift cluster [cluster name]'s track has been modified from [from track] to [to track]. |
|
Management |
REDSHIFT-EVENT-2021 | ERROR | The [operation] of Amazon Redshift cluster [cluster name] did not succeed while acquiring capacity from our capacity pool. We are working to acquire capacity but for now, we have cancelled your request. Delete this cluster and retry later. |
|
Management |
REDSHIFT-EVENT-2022 | ERROR | The [operation] of Amazon Redshift cluster [cluster name] did not succeed while acquiring capacity from our capacity pool. We are working to acquire capacity but for now, we have cancelled your request. Capacity is available in [alternative Availability Zones]. Delete this cluster and retry in an alternative Availability Zone. |
|
Management |
REDSHIFT-EVENT-2023 | ERROR | We have detected hardware failure on your single node Amazon Redshift cluster [cluster name], which may have resulted in failed queries or intermittent availability of the cluster. Replacing the cluster did not succeed while acquiring capacity from our capacity pool. You will need to restore a new cluster from a snapshot. Delete this cluster, select the latest available snapshot, and restore a new cluster from that snapshot. This will automatically provision you on healthy hardware. |
|
Management |
REDSHIFT-EVENT-2024 | ERROR | We have detected hardware failure on your single node Amazon Redshift cluster [cluster name], which may have resulted in failed queries or intermittent availability of the cluster. Replacing cluster did not succeed while acquiring capacity from our capacity pool. Capacity is available in Availability Zone: [alternative Availability Zones]. Delete this cluster, select the latest available snapshot, and restore a new cluster from that snapshot. This will automatically provision you on healthy hardware. |
| Management | REDSHIFT-EVENT-3011 | INFO | Elastic resize for Amazon Redshift cluster '[cluster name]' started at [time]. We will hold the database connections during resize. Some queries and connections may be terminated or timed out during this operation. |
| Management | REDSHIFT-EVENT-3012 | INFO | We have received an elastic resize request for the cluster '[cluster name]' started at [time]. We will provide an event notification when resize begins. |
|
Pending |
REDSHIFT-EVENT-2025 | INFO |
Your database for cluster <cluster name> will be updated between <start time> and <end time>. Your cluster will not be accessible. Plan accordingly. |
|
Pending |
REDSHIFT-EVENT-2026 | INFO |
Your cluster <cluster name> will be updated between <start time> and <end time>. Your cluster will not be accessible. Plan accordingly. |
|
Monitoring |
REDSHIFT-EVENT-2050 | INFO |
A hardware issue was detected on Amazon Redshift cluster [cluster name]. A replacement request was initiated at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3000 | INFO |
Your Amazon Redshift cluster [cluster name] was rebooted at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3001 | INFO |
A node on your Amazon Redshift cluster: [cluster name] was automatically replaced at [time], and your cluster is operating normally. |
|
Monitoring |
REDSHIFT-EVENT-3002 | INFO |
The resize for your Amazon Redshift cluster [cluster name] is complete and your cluster is available for reads and writes. The resize was initiated at [time] and took [hours] hours to complete. |
|
Monitoring |
REDSHIFT-EVENT-3003 | INFO |
Amazon Redshift cluster [cluster name] was successfully created from snapshot [snapshot name] and is available for use. |
|
Monitoring |
REDSHIFT-EVENT-3007 | INFO |
Your Amazon Redshift snapshot [snapshot name] was copied successfully from [source Amazon Region] to [destination Amazon Region] at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3008 | INFO |
Table restore started for Amazon Redshift cluster [cluster name] at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3009 | INFO |
Table restore completed successfully for Amazon Redshift cluster [cluster name] at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3010 | ERROR |
Table restore failed for Amazon Redshift cluster [cluster name] at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3013 | ERROR |
The requested elastic resize operation for Amazon Redshift cluster [cluster name] failed at [time] due to [reason]. |
|
Monitoring |
REDSHIFT-EVENT-3014 | INFO |
Amazon Redshift rebooted cluster [cluster name] at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3500 | ERROR |
The resize for your Amazon Redshift cluster [cluster name] failed. The resize will be automatically retried in a few minutes. |
|
Monitoring |
REDSHIFT-EVENT-3501 | ERROR |
Your restore operation to create Amazon Redshift cluster [cluster name] from snapshot [snapshot name] failed at [time]. Please retry your operation. |
|
Monitoring |
REDSHIFT-EVENT-3504 | ERROR |
The Amazon S3 bucket [bucket name] is not valid for logging for cluster [cluster name]. |
|
Monitoring |
REDSHIFT-EVENT-3505 | ERROR |
The Amazon S3 bucket [bucket name] does not have the correct IAM policies for cluster [cluster name]. |
|
Monitoring |
REDSHIFT-EVENT-3506 | ERROR |
The Amazon S3 bucket [bucket name] does not exist. Logging cannot continue for cluster [cluster name]. |
|
Monitoring |
REDSHIFT-EVENT-3507 | ERROR |
The Amazon Redshift cluster [cluster name] cannot be created using EIP [IP address]. This EIP is already in use. |
|
Monitoring |
REDSHIFT-EVENT-3508 | ERROR |
The Amazon Redshift cluster [cluster name] cannot be created using EIP [IP address]. The EIP cannot be found. |
|
Monitoring |
REDSHIFT-EVENT-3509 | ERROR |
Cross-region snapshot copy is not enabled for cluster [cluster name]. |
|
Monitoring |
REDSHIFT-EVENT-3510 | ERROR |
Table restore failed to start for Amazon Redshift cluster [cluster name] at [time]. Reason: [reason]. |
|
Monitoring |
REDSHIFT-EVENT-3511 | ERROR |
Table restore failed for Amazon Redshift cluster [cluster name] at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3512 | ERROR |
Amazon Redshift cluster [cluster name] has failed due to a hardware issue. The cluster is being automatically restored from the latest snapshot [snapshot name] created at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3513 | ERROR |
Amazon Redshift cluster [cluster name] has failed due to a hardware issue. The cluster is being automatically restored from the latest snapshot [snapshot name] created at [time]. Any database changes made after this time will need to be resubmitted. |
|
Monitoring |
REDSHIFT-EVENT-3514 | ERROR |
Amazon Redshift cluster [cluster name] has failed due to a hardware issue. The cluster is being placed in hardware failure status. Please delete the cluster and restore from the latest snapshot [snapshot name] created at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3515 | ERROR |
Amazon Redshift cluster [cluster name] has failed due to a hardware issue. The cluster is being placed in hardware failure status. Please delete the cluster and restore from the latest snapshot [snapshot name] created at [time]. Any database changes made after this time will need to be resubmitted. |
|
Monitoring |
REDSHIFT-EVENT-3516 | ERROR |
Amazon Redshift cluster [cluster name] has failed due to a hardware issue and there are no backups for the cluster. The cluster is being placed in hardware failure status and can be deleted. |
|
Monitoring |
REDSHIFT-EVENT-3519 | INFO |
Cluster [cluster name] began restart at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3520 | INFO |
Cluster [cluster name] completed restart at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3521 | INFO |
We detected a connectivity issue on the cluster '[cluster name]'. An automated diagnostics check has been initiated at [time]. |
|
Monitoring |
REDSHIFT-EVENT-3522 | INFO |
Recovery action on '[cluster name]' cluster failed at [time]. The Amazon Redshift team is working on a solution. |
| Monitoring | REDSHIFT-EVENT-3533 | ERROR | Cluster resize on '[cluster name]' was cancelled at [time]. The operation was cancelled because [reason]. [action needed]. |
| Monitoring | REDSHIFT-EVENT-3534 | INFO | The elastic resize for Amazon Redshift cluster '[cluster name]' completed at [time]. The cluster is now available for read and write operations while we transfer data. Some queries may take longer to finish until data transfer is complete. |
| Monitoring | REDSHIFT-EVENT-3537 | INFO | Cluster '[cluster name]' data transfer completed at [time in UTC]. |
| Monitoring | REDSHIFT-EVENT-3600 | INFO | The requested resize operation for Amazon Redshift cluster '[cluster name]' was cancelled in the past. Rollback was completed at [time]. |
|
Pending |
REDSHIFT-EVENT-3601 | INFO | A node on your cluster <cluster name> will be replaced between <start time> and <end time>. You can't defer this maintenance. Plan accordingly. |
|
Pending |
REDSHIFT-EVENT-3602 | INFO | A node on your cluster <cluster name> is scheduled to be replaced between <start time> and <end time>. Your cluster will not be accessible. Plan accordingly. |
|
Management |
REDSHIFT-EVENT-3603 | INFO | The restore operation to create cluster [cluster name] from snapshot [snapshot name] failed due to an internal error. The cluster is being placed in incompatible restore status and can be deleted. Try to restore the snapshot into a cluster with a different configuration. |
|
Management |
REDSHIFT-EVENT-3614 | INFO | The scheduled action [scheduled action name] was created at [time in UTC]. The first invocation is scheduled at [time in UTC]. |
|
Management |
REDSHIFT-EVENT-3615 | INFO | The scheduled action [scheduled action name] is scheduled at [time in UTC]. |
|
Monitoring |
REDSHIFT-EVENT-3616 | INFO | The scheduled action [scheduled action name] at [time in UTC] finished with 'SUCCEEDED' status. |
|
Monitoring |
REDSHIFT-EVENT-3617 | ERROR | The scheduled action [scheduled action name] was skipped at [time in UTC] due to delay. |
|
Monitoring |
REDSHIFT-EVENT-3618 | INFO | The cluster [cluster name] pause operation started at [UTC time]. Pause Started |
|
Monitoring |
REDSHIFT-EVENT-3619 | INFO | Amazon Redshift cluster [cluster name] was successfully paused at [UTC time]. |
|
Management |
REDSHIFT-EVENT-3626 | INFO | The scheduled action [scheduled action name] was modified at [time in UTC]. The first invocation is scheduled at [time in UTC]. |
|
Management |
REDSHIFT-EVENT-3627 | INFO | The scheduled action [scheduled action name] was deleted at [time in UTC]. |
|
Monitoring |
REDSHIFT-EVENT-3628 | ERROR | The scheduled action [scheduled action name] at [time in UTC] finished with 'FAILED' status. |
|
Management |
REDSHIFT-EVENT-3629 | INFO | Amazon Redshift [cluster name] has received your relocation request. When Availability Zone relocation completes, Amazon Redshift sends an event notification. |
|
Management |
REDSHIFT-EVENT-3630 | INFO | Amazon Redshift cluster [cluster name] was successfully relocated from [availability zone] to [availability zone]. You can use the cluster now. |
|
Management |
REDSHIFT-EVENT-3631 | INFO | Amazon Redshift successfully relocated your Amazon Redshift cluster [cluster name] from [availability zone] to [availability zone] for recovery. |
|
Management |
REDSHIFT-EVENT-3632 | INFO | Amazon Redshift has temporarily disabled cluster relocation for your Amazon Redshift cluster [cluster name] due to configuration changes. Try cluster relocation again later. |
|
Monitoring |
REDSHIFT-EVENT-3658 | ERROR | EC2-Classic to EC2-VPC migration failed for Redshift cluster [cluster id]. |
|
Monitoring |
REDSHIFT-EVENT-3659 | INFO | EC2-Classic to EC2-VPC migration succeeded for Redshift cluster [cluster id]. |
|
Monitoring |
REDSHIFT-EVENT-3660 | INFO | The cluster is being placed in hardware failure status. Please delete the EC2-Classic cluster and restore to a EC2-VPC cluster from the latest snapshot [snapshot name] created at [time in UTC]. |
| Security | REDSHIFT-EVENT-4000 | INFO |
Your admin credentials for your Amazon Redshift cluster: [cluster name] were updated at [time]. |
| Security | REDSHIFT-EVENT-4001 | INFO |
The security group [security group name] was modified at [time]. The changes will take place for all associated clusters automatically. |
|
Security |
REDSHIFT-EVENT-4500 | ERROR |
The security group [security group name] you provided is invalid. Your configuration changes for cluster [cluster name] were not applied. Please visit the Amazon Web Services Management Console to correct the issue. |
|
Security |
REDSHIFT-EVENT-4501 | ERROR |
The security group [security group name] specified in Cluster Security Group [cluster security group name] could not be found. The authorization cannot be completed. |
|
Security |
REDSHIFT-EVENT-4502 | ERROR |
The admin credentials for Amazon Redshift cluster [cluster name] failed to update at [time] due to concurrent activity. Allow the current workload to complete or reduce the active workload and then retry the operation. |
The following table shows the event category and a list of events when a parameter group is the source type.
Categories and events for the parameter group source type
The following tables shows the event category and a list of events when a security group is the source type.
Categories and events for the security group source type
The following tables shows the event category and a list of events when a snapshot is the source type.
Categories and events for the snapshot source type