What is EventBridge and what value does it provide?
EventBridge is an AWS integration that provides a reliable way to receive events without the added complexity of managing WebSockets. It also allows orgs to receive all events for high-level topics without having to manage subscriptions to a limited list of fine-grained topics. Genesys Cloud supports an integration with Amazon EventBridge that delivers notifications to a variety of AWS services including Lambda, Kinesis, SQS, SNS, and more. See the AWS overview of EventBridge features.
Is there a cost associated with EventBridge?
At this time, in us-east-1, AWS charges $1 per million events. More information here: Amazon EventBridge Pricing | Event Bus | Amazon Web Services
How do I set up the EventBridge integration in Genesys Cloud?
Documentation here: About the Amazon EventBridge integration - Genesys Cloud Resource Center
When will Analytics Detail Events (the replacement for conversation events) be released to the beta?
We are currently targeting beta release on 27 October, 2021.
When will EventBridge and ADEs be released to GA?
We are targeting GA release in December 2021.
What happens if an event isn't delivered successfully? What retry capabilities do Genesys and AWS provide?
-
Should an event fail to delver to AWS, Genesys Cloud will retry event delivery for 4 days.
-
AWS EventBridge retries sending the event to its designated target for 24 hours and up to 185 times. If an event isn't delivered after all retry attempts are exhausted, the event is dropped and EventBridge doesn't continue to process it. To avoid losing events after they fail to be delivered to a target, you can configure a dead-letter queue (DLQ) and send all failed events to it for processing later. Event retry policy and using dead-letter queues - Amazon EventBridge
Where can I find the list of Genesys Cloud events that are supported in EventBridge?
Currently, the Notifications API and EventBridge have 1:1 parity in terms of supported events with the exception of conversation events, which are only supported in the Notifications API, and Analytics Detail Events (ADEs), which will only be supported in EventBridge.
What is the expected latency of events that pass through the EventBridge integration, compared to receiving via your notifications service websocket? Is it milliseconds, minutes, an hour?
It’s typically a few hundred milliseconds in our testing but can fluctuate up to multiple seconds. The bottleneck is usually EventBridge itself or the AWS service that is configured to process the event. For example, a lambda can take several seconds to spin up from a cold start.
How many EventBridge integrations can be supported in a single Genesys Cloud org?
Genesys Cloud supports up to three EventBridge integrations in a single org.
What is the difference between the Event Orchestration feature and the EventBridge integration?
These features are properly thought of as opposite sides of the same coin; similar functionality but for very different use cases. Event Orchestration is intended to invoke workflows within Genesys Cloud in order to react to events that occur within Genesys Cloud; EventBridge is a high throughput messaging bus with specific service level guarantees for archiving information in an external system or the creation of your own process automation flows within your AWS infrastructure. Triggers do not have the same level of service level guarantees, message retries, etc. that are crucial for something like a BI pipeline, while EventBridge was specifically built to service that sort of use case.
What is the event schema?
EventBridge requires all events to be in JSON format and enforces a top-level schema. The Genesys Cloud event payload can be found in the detail attribute. The eventBody will match the schema found in Available Topics. Analytics Detail Event schemas can be found here.
When should I use EventBridge rather than Analytics or Notifications APIs?
Genesys offers customers different options for querying and synchronizing data from Genesys Cloud back to their own applications or data stores. The timeliness of your data needs, the sensitivity to message loss, and the amount of data queried or synchronized are the driving factors in determining which data integration type is appropriate for your use case. Please reference our Data Integration Guide for more information.
How does Genesys Cloud ensure that event data is transferred only to the AWS account provided by the customer?
When you create the EventBridge integration, Genesys Cloud maps the org ID to the unique Partner Event Source name. Every event we process has an associated org ID, and we will only send events for a given org to Partner Event Sources created by that org. AWS will only allow applications authenticated with the AWS account that creates a Partner Event Source to publish to that event source.