We are attempting to establish a real-time event streaming pipeline from our Genesys Cloud organization to AWS EventBridge. The objective is to capture specific routing queue events for downstream processing in our data warehouse. We have configured the integration via the Genesys Cloud admin console and generated the necessary IAM role ARN for EventBridge to assume. The connection test passes successfully, indicating that the basic trust relationship is valid.
The issue arises when we attempt to define the event filter. We are trying to subscribe only to routing.queue.member.status events where the status changes to available. When we apply the following filter configuration in the Genesys Cloud UI, the save operation returns a 400 Bad Request error. The error message is generic: “Invalid event filter configuration.”
We have verified that the event type is supported by checking the documentation for EventBridge-compatible events. Here is the JSON payload we are attempting to use for the filter definition:
{
"source": ["genesys.cloud"],
"detail-type": ["routing.queue.member.status"],
"detail": {
"status": ["available"]
}
}
We have also tried removing the detail block entirely to capture all events of that type, which works without error. However, filtering on the status field consistently fails. We suspect there might be a mismatch in the field naming convention between the Genesys Cloud event schema and what EventBridge expects for the filter syntax. We have checked the event structure by subscribing to all events and inspecting a sample payload in CloudWatch Logs. The status field appears as detail.status in the raw event.
Has anyone encountered this specific validation error? Are there known restrictions on filtering nested attributes within the detail object for Genesys Cloud EventBridge integrations? We are using the latest version of the Genesys Cloud platform and are not using any custom transformers at this stage.