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 AWS 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.
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 AWS 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
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 AWS 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-1 or
my-snapshot-20130823. The ID must be for a resource in the
same region as the event subscription.
-
Event category, the values are Configuration, Management, Monitoring, and
Security.
-
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 AWS 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 AWS 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 AWS 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 section lists 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 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
AWS 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 AWS 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 AWS 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 EC2 Network Interface
(ENI) limit. Please delete up to [maximum number of ENIs] ENIs or
request a limit increase of the number of network interfaces per
region with 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 AWS 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 be
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 region] to [destination 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 insufficient_capacity.
|
|
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 wihile we transfer data. Some queries may take
longer to finish until data transfer is complete.
|
| 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.
|
| Security |
REDSHIFT-EVENT-4000 |
INFO |
Your master 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 AWS 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.
|
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
|
Amazon Redshift Category
|
Event ID |
Event Severity |
Description
|
|
Configuration
|
REDSHIFT-EVENT-1002 |
INFO |
The parameter [parameter name] was updated from [value] to [value]
at [time].
|
|
Configuration
|
REDSHIFT-EVENT-1003 |
INFO |
Cluster parameter group [group name] was created.
|
|
Configuration
|
REDSHIFT-EVENT-1004 |
INFO |
Cluster parameter group [group name] was deleted.
|
|
Configuration
|
REDSHIFT-EVENT-1005 |
INFO |
Cluster 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.
|
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
|
Amazon Redshift Category
|
Event ID |
Event Severity |
Description
|
|
Security
|
REDSHIFT-EVENT-4002 |
INFO |
Cluster security group [group name] was created.
|
|
Security
|
REDSHIFT-EVENT-4003 |
INFO |
Cluster security group [group name] was deleted.
|
|
Security
|
REDSHIFT-EVENT-4004 |
INFO |
Cluster security group [group name] was changed at [time]. Changes
will be automatically applied to all associated clusters.
|
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
|
Amazon Redshift Category
|
Event ID |
Event Severity |
Description
|
|
Management
|
REDSHIFT-EVENT-2009 |
INFO |
A user snapshot [snapshot name] for Amazon Redshift Cluster [cluster
name] started at [time]. To monitor snapshot progress, please visit
the AWS Management Console.
|
|
Management
|
REDSHIFT-EVENT-2010 |
INFO |
The user snapshot [snapshot name] for your Amazon Redshift cluster
[cluster name] was cancelled at [time].
|
|
Management
|
REDSHIFT-EVENT-2011 |
INFO |
The user snapshot [snapshot name] for Amazon Redshift cluster [cluster
name] was deleted at [time].
|
|
Management
|
REDSHIFT-EVENT-2012 |
INFO |
The final snapshot [snapshot name] for Amazon Redshift cluster [cluster
name] was started at [time].
|
|
Monitoring
|
REDSHIFT-EVENT-3004 |
INFO |
The user snapshot [snapshot name] for your Amazon Redshift cluster
[cluster name] completed successfully at [time].
|
|
Monitoring
|
REDSHIFT-EVENT-3005 |
INFO |
The final snapshot [name] for Amazon Redshift cluster [name] completed
successfully at [time].
|
|
Monitoring
|
REDSHIFT-EVENT-3006 |
INFO |
The final snapshot [snapshot name] for Amazon Redshift cluster [cluster
name] was cancelled at [time].
|
|
Monitoring
|
REDSHIFT-EVENT-3502 |
ERROR |
The final snapshot [snapshot name] for Amazon Redshift cluster [cluster
name] failed at [time]. The team is investigating the issue. Please
visit the AWS Management Console to retry the operation.
|
|
Monitoring
|
REDSHIFT-EVENT-3503 |
ERROR |
The user snapshot [snapshot name] for your Amazon Redshift cluster
[cluster name] failed at [time]. The team is investigating the
issue. Please visit the AWS Management Console to retry the operation.
|
