Update : Now you can schedule queries using Query Editor V2.

Here is the Document.

Based on the information available, it appears that the "Redshift Data Statement Status Change" event should indeed trigger for scheduled queries in Amazon Redshift Query Editor v2, but there are a few things to consider: 1. The "Redshift Data Statement Status Change" event is generated when the ExecuteStatement or BatchExecuteStatement API operation is used with the WithEvent option set to true. Scheduled queries in Query Editor v2 should use these API operations internally, but you may need to ensure that the WithEvent option is enabled for your scheduled query. 2. The event pattern you've set up in EventBridge looks correct, matching the source, detail-type, and specific state and statement name. However, make sure that the statementName "QS2-Refresh_materialized_views" exactly matches the name of your scheduled query. 3. It's possible that the SNS topic subscription you mentioned might be interfering with the EventBridge rule. You should let the EventBridge rule handle the event routing to your Lambda function, rather than subscribing the scheduled query directly to the SNS topic. 4. Double-check that your Lambda function has the necessary permissions to be invoked by both EventBridge and SNS, and that it can publish to the SNS topic. 5. Verify that your scheduled query is actually completing successfully and reaching the FINISHED state. If you've confirmed all of these points and the rule still isn't triggering, you may want to consider the following troubleshooting steps: 1. Use CloudWatch Logs to check if the events are being emitted at all. 2. Temporarily broaden your EventBridge rule pattern to capture all events from aws.redshift-data to see if you're receiving any events. 3. Contact AWS support for further assistance, as there might be an issue with the event emission for scheduled queries that isn't documented. Regarding your observation about the lack of comprehensive documentation for aws.redshift-data events and EventBridge in general, this is a valid concern. AWS services are constantly evolving, and sometimes documentation lags behind. In such cases, it can be helpful to experiment with broader event patterns and use CloudWatch Logs to understand what events are actually being emitted. **Sources** Monitoring events for the Amazon Redshift Data API in Amazon EventBridge - Amazon Redshift Monitoring the scheduled query - Amazon Redshift