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>. |
|
Configuration |
REDSHIFT-SERVERLESS-EVENT-1011 | ERROR | Amazon Redshift Serverless couldn't create workgroup [workgroup name] because the Service Linked Role (SLR) necessary for this operation is inaccessible. Try creating it again on the Amazon Redshift console. Amazon Redshift will create the SLR automatically. |
|
Monitoring |
REDSHIFT-SERVERLESS-EVENT-1029 | ERROR | Workgroup base RPU change failed to complete at [time in UTC] because it doesn't have enough disk space available. Try again with a different configuration. |
|
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>. |
|
Security |
REDSHIFT-SERVERLESS-EVENT-1012 | ERROR | Amazon Redshift can't access the secret for your namespace <namespace name>. |
|
Security |
REDSHIFT-SERVERLESS-EVENT-1013 | ERROR | Amazon Redshift can't access the KMS key that was used to encrypt the admin credentials secret for your namespace <namespace name>. |
|
Security |
REDSHIFT-SERVERLESS-EVENT-1014 | ERROR | Amazon Redshift can't rotate the secret for your namespace <namespace name> because there's an ongoing operation on the workgroup. |
|
Security |
REDSHIFT-SERVERLESS-EVENT-1015 | ERROR | Your namespace <namespace name> doesn't have a workgroup attached to it. Amazon Redshift can only rotate secrets for namespaces with workgroups attached to them. |
|
Security |
REDSHIFT-SERVERLESS-EVENT-1016 | INFO | Admin credentials updated for your namespace <namespace name> at <time in UTC>. |