Amazon Redshift provisioned cluster event notifications

Configuration

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

Your Amazon Redshift cluster [cluster name] was modified to use parameter group [parameter group name] at [time].

Configuration

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

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

Subnets in cluster subnet group [subnet group name] have no available IP addresses. Cluster [cluster name] could not be created.

Configuration

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

The HSM for cluster [cluster name] is unreachable.

Configuration

The HSM for cluster [cluster name] cannot be registered. Try a different configuration.

Configuration

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

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

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

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

Your Amazon Redshift cluster: [cluster name] has been created and is ready for use.

Management

Your Amazon Redshift cluster [cluster name] was deleted at [time]. A final snapshot [was / was not] saved.

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

Management

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

Management

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

Management

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

Management

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

Management

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

Your Amazon Redshift cluster [cluster name] was renamed at [time].

Management

A table restore request for Amazon Redshift cluster [cluster name] has been received.

Management

Table restore was cancelled for Amazon Redshift cluster [cluster name] at [time].

Management

Replacement of your Amazon Redshift cluster [cluster name] was started at [time].

Management

Customer initiated maintenance started on your Amazon Redshift cluster [cluster name] at [time]. The cluster may not be available during maintenance.

Management

Customer initiated maintenance completed on your Amazon Redshift cluster [cluster name] at [time].

Management

Customer initiated maintenance failed on your Amazon Redshift cluster [cluster name] at [time]. Returning the cluster back to its original state.

Management

Your Amazon Redshift cluster [cluster name]'s track has been modified from [from track] to [to track].

Management

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

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

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

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.

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.

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

Your database for cluster [cluster name] will be updated between [start time] and [end time]. Your cluster will not be accessible. Plan accordingly.

Pending

Your cluster [cluster name] will be updated between [start time] and [end time]. Your cluster will not be accessible. Plan accordingly.

Monitoring

A hardware issue was detected on Amazon Redshift cluster [cluster name]. A replacement request was initiated at [time].

Monitoring

Your Amazon Redshift cluster [cluster name] was rebooted at [time].

Monitoring

A node on your Amazon Redshift cluster: [cluster name] was automatically replaced at [time], and your cluster is operating normally.

Monitoring

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

Amazon Redshift cluster [cluster name] was successfully created from snapshot [snapshot name] and is available for use.

Monitoring

Your Amazon Redshift snapshot [snapshot name] was copied successfully from [source Amazon Region] to [destination Amazon Region] at [time].

Monitoring

Table restore started for Amazon Redshift cluster [cluster name] at [time].

Monitoring

Table restore completed successfully for Amazon Redshift cluster [cluster name] at [time].

Monitoring

Table restore failed for Amazon Redshift cluster [cluster name] at [time].

Monitoring

The requested elastic resize operation for Amazon Redshift cluster [cluster name] failed at [time] due to [reason].

Monitoring

Amazon Redshift rebooted cluster [cluster name] at [time].

Pending

We have scheduled a reboot for your cluster [cluster name] for maintenance between [start time in UTC] and [end time in UTC]. Your cluster won't be accessible during this time. We recommend that you plan for the outage to avoid any setbacks.

Monitoring

Cluster will be rebooted.

Monitoring

The resize for your Amazon Redshift cluster [cluster name] failed. The resize will be automatically retried in a few minutes.

Monitoring

Your restore operation to create Amazon Redshift cluster [cluster name] from snapshot [snapshot name] failed at [time]. Please retry your operation.

Monitoring

The Amazon S3 bucket [bucket name] is not valid for logging for cluster [cluster name].

Monitoring

The Amazon S3 bucket [bucket name] does not have the correct IAM policies for cluster [cluster name].

Monitoring

The Amazon S3 bucket [bucket name] does not exist. Logging cannot continue for cluster [cluster name].

Monitoring

The Amazon Redshift cluster [cluster name] cannot be created using EIP [IP address]. This EIP is already in use.

Monitoring

The Amazon Redshift cluster [cluster name] cannot be created using EIP [IP address]. The EIP cannot be found.

Monitoring

Cross-region snapshot copy is not enabled for cluster [cluster name].

Monitoring

Table restore failed to start for Amazon Redshift cluster [cluster name] at [time]. Reason: [reason].

Monitoring

Table restore failed for Amazon Redshift cluster [cluster name] at [time].

Monitoring

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

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

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

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

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

Cluster [cluster name] began restart at [time].

Monitoring

Cluster [cluster name] completed restart at [time].

Monitoring

We detected a connectivity issue on the cluster '[cluster name]'. An automated diagnostics check has been initiated at [time].

Monitoring

Recovery action on '[cluster name]' cluster failed at [time]. The Amazon Redshift team is working on a solution.

Cluster resize on '[cluster name]' was cancelled at [time]. The operation was cancelled because [reason]. [action needed].

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.

Cluster '[cluster name]' data transfer completed at [time in UTC].

The requested resize operation for Amazon Redshift cluster '[cluster name]' was cancelled in the past. Rollback was completed at [time].

Pending

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

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

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

The scheduled action [scheduled action name] was created at [time in UTC]. The first invocation is scheduled at [time in UTC].

Management

The scheduled action [scheduled action name] is scheduled at [time in UTC].

Monitoring

The scheduled action [scheduled action name] at [time in UTC] finished with 'SUCCEEDED' status.

Monitoring

The scheduled action [scheduled action name] was skipped at [time in UTC] due to delay.

Monitoring

The cluster [cluster name] pause operation started at [UTC time]. Pause Started

Monitoring

Amazon Redshift cluster [cluster name] was successfully paused at [UTC time].

Management

The scheduled action [scheduled action name] was modified at [time in UTC]. The first invocation is scheduled at [time in UTC].

Management

The scheduled action [scheduled action name] was deleted at [time in UTC].

Monitoring

The scheduled action [scheduled action name] at [time in UTC] finished with 'FAILED' status.

Monitoring

An internal failover request for cluster [cluster name] has been initiated.

Monitoring

Amazon Redshift successfully relocated your Amazon Redshift cluster [cluster name] from [availability-zone] to [availability-zone] for recovery.

Management

Amazon Redshift [cluster name] received your relocation request. When Availability Zone relocation completes, Amazon Redshift sends an event notification.

Monitoring

Amazon Redshift cluster [cluster name] was successfully relocated from [availability-zone] to [availability-zone]. You can use the cluster now.

Monitoring

EC2-Classic to EC2-VPC migration failed for Redshift cluster [cluster id].

Monitoring

EC2-Classic to EC2-VPC migration succeeded for Redshift cluster [cluster id].

Monitoring

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

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

Management

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

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

Management

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

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

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

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

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

Management

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

Monitoring

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

Management

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

Management

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

Monitoring

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

Configuration

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

Configuration

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

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

Management

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

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.

Management

The requested resize operation for Amazon Redshift cluster [cluster name] completed at [time in UTC].

Security

The encryption key rotation for your Amazon Redshift cluster [cluster name] was not able to complete.

DataSharing

The operation to register your Amazon Redshift namespace >cluster name< to Glue Data Catalog account >account id< was started at >time in UTC<.

DataSharing

The operation to register your Amazon Redshift namespace >cluster name< to Glue Data Catalog account >account id< has successfully completed at >time in UTC<.

DataSharing

The operation to register your Amazon Redshift namespace >cluster name< to Glue Data Catalog account >account id< has failed at >time in UTC<.

DataSharing

The operation to deregister your Amazon Redshift namespace >cluster name< from Glue Data Catalog account >account id< was started at >time in UTC<.

DataSharing

The operation to deregister your Amazon Redshift namespace >cluster name< from Glue Data Catalog account >account id< has successfully completed at >time in UTC<.

DataSharing

The operation to deregister your Amazon Redshift namespace >cluster name< from Glue Data Catalog account >account id< has failed at >time in UTC<.

Your admin credentials for your Amazon Redshift cluster: [cluster name] were updated at [time].

The security group [security group name] was modified at [time]. The changes will take place for all associated clusters automatically.

Security

One or more of the security groups you provided for the Amazon Redshift cluster [cluster name] could not be found. If there were any valid security groups, they were applied to the cluster. Any invalid security groups were not applied. If you were modifying an existing cluster and no security groups were valid, the cluster kept its original security groups. If you were creating a new cluster and no security groups were valid, the cluster creation failed. In either case, please retry the request with valid security groups. For more information on managing security groups in Amazon Redshift, go to VPC security groups in the Amazon Redshift Management Guide.

Security

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

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

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

Security

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

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

Security

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

Configuration

The parameter [parameter name] was updated from [value] to [value] at [time].

Configuration

Cluster parameter group [group name] was created.

Configuration

Cluster parameter group [group name] was deleted.

Configuration

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.

Security

Cluster security group [group name] was created.

Security

Cluster security group [group name] was deleted.

Security

Cluster security group [group name] was changed at [time]. Changes will be automatically applied to all associated clusters.

Management

A user snapshot [snapshot name] for Amazon Redshift Cluster [cluster name] started at [time]. To monitor snapshot progress, please visit the Amazon Web Services Management Console.

Management

The user snapshot [snapshot name] for your Amazon Redshift cluster [cluster name] was cancelled at [time].

Management

The user snapshot [snapshot name] for Amazon Redshift cluster [cluster name] was deleted at [time].

Management

The final snapshot [snapshot name] for Amazon Redshift cluster [cluster name] was started at [time].

Monitoring

The user snapshot [snapshot name] for your Amazon Redshift cluster [cluster name] completed successfully at [time].

Monitoring

The final snapshot [name] for Amazon Redshift cluster [name] completed successfully at [time].

Monitoring

The final snapshot [snapshot name] for Amazon Redshift cluster [cluster name] was cancelled at [time].

Monitoring

The final snapshot [snapshot name] for Amazon Redshift cluster [cluster name] failed at [time]. The team is investigating the issue. Please visit the Amazon Web Services Management Console to retry the operation.

Monitoring

The user snapshot [snapshot name] for your Amazon Redshift cluster [cluster name] failed at [time]. The team is investigating the issue. Please visit the Amazon Web Services Management Console to retry the operation.