Amazon Redshift event notifications - Amazon Redshift

Amazon Redshift event notifications

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

VPC security groups for cluster [cluster name] updated at [time in UTC].

Management

REDSHIFT-EVENT-2003 INFO

Maintenance started on cluster [cluster name] at [time in UTC].

Management

REDSHIFT-EVENT-2004 INFO

Maintenance on cluster [cluster name] completed at [time in UTC].

Management

REDSHIFT-EVENT-2006 INFO

Cluster [cluster name] resize started at [time in UTC]. Cluster is in read-only mode.

Management

REDSHIFT-EVENT-2007 INFO

A resize request for cluster [cluster name] has been acknowledged.

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 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 AWS Region] to [destination AWS 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].

Management

REDSHIFT-EVENT-3666 INFO

Amazon Redshift Multi-AZ cluster [cluster name] has detected a failure at [time in UTC] and triggered an automatic recovery.

Management

REDSHIFT-EVENT-3667 INFO

Amazon Redshift Multi-AZ cluster [cluster name] successfully recovered at [time in UTC] and is available for use in [first availability zone]. Secondary compute in another AZ will be available shortly.

Monitoring

REDSHIFT-EVENT-3668 ERROR

Amazon Redshift Multi-AZ cluster [cluster name] has failed to recover at [time in UTC].

Management

REDSHIFT-EVENT-3669 INFO

Amazon Redshift Multi-AZ cluster [cluster name] successfully recovered at [time in UTC] and is available for use with compute resources from both [first availability zone] and [second availability-zone].

Management

REDSHIFT-EVENT-3670 INFO

Maintenance on Amazon Redshift cluster [cluster name] completed at [time in UTC] and is available for use with compute resources in [first availability zone]. Secondary compute in another AZ will be available shortly.

Management

REDSHIFT-EVENT-3671 INFO

Resize on Amazon Redshift cluster [cluster name] completed at [time in UTC] and is available for use in [first availability zone]. Secondary compute in another AZ will be available shortly.

Management

REDSHIFT-EVENT-3672 INFO

Amazon Redshift Multi-AZ cluster [cluster name] has detected a failure in [second availability-zone] at [time in UTC] and triggered an automatic recovery.

Management

REDSHIFT-EVENT-3673 INFO

The operation to enable Multi-AZ for Amazon Redshift cluster [cluster name] has started at [time in UTC].

Management

REDSHIFT-EVENT-3674 INFO

The operation to enable Multi-AZ for Amazon Redshift cluster [cluster name] has successfully completed at [time in UTC].

Monitoring

REDSHIFT-EVENT-3675 ERROR

The operation to enable Multi-AZ for Amazon Redshift cluster [cluster name] has failed at [time in UTC].

Management

REDSHIFT-EVENT-3676 INFO

The operation to disable Multi-AZ for your Amazon Redshift Multi-AZ cluster [cluster name] has started at [time in UTC].

Management

REDSHIFT-EVENT-3677 INFO

The operation to disable Multi-AZ for your Amazon Redshift cluster [cluster name] has successfully completed at [time in UTC].

Monitoring

REDSHIFT-EVENT-3678 ERROR

The operation to disable Multi-AZ for your Amazon Redshift cluster [cluster name] has failed at [time in UTC].

Confguration

REDSHIFT-EVENT-3679 INFO

The port of Amazon Redshift cluster [cluster name] modified successfully.

Configuration

REDSHIFT-EVENT-3680 ERROR

Amazon Redshift couldn't create cluster [cluster name] because the Service Linked Role (SLR) necessary for this operation is inaccessible. Try creating it again from the Amazon Redshift console. Amazon Redshift will create the SLR automatically.

Monitoring

REDSHIFT-EVENT-3684 ERROR

Your Amazon S3 bucket [bucket name] has been encrypted with an unknown or inaccessible AWS KMS key. Modify the encryption of your Amazon S3 bucket.

Management

REDSHIFT-EVENT-3685 ERROR

The restore operation on the cluster [cluster name] failed because it doesn't have enough disk space available. The operation is being rolled back. Try restoring to a cluster with a different configuration.

Management

REDSHIFT-EVENT-3686 ERROR

The resize operation on the cluster [cluster name] failed because it doesn't have enough disk space available. The operation is being rolled back. Try resizing to a cluster with a different configuration.

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

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.

Security

REDSHIFT-EVENT-4503 ERROR

Amazon Redshift can't access the secret for your cluster [cluster name].

Security

REDSHIFT-EVENT-4504 ERROR

Amazon Redshift can't access the KMS key [KMS key] that was used to encrypt the admin credentials secret for your cluster [cluster name].

Security

REDSHIFT-EVENT-4505 ERROR

Amazon Redshift can't rotate the secret for your cluster [cluster name] because there's an ongoing operation on the cluster.

Security

REDSHIFT-EVENT-4506 ERROR

Your Amazon Redshift cluster [cluster name] is paused. Amazon Redshift can't rotate the secrets of paused clusters.

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.