Skip to main content
Bind the Operata partner event source to an Amazon EventBridge bus in your AWS account, so Operata events land on the bus ready for you to attach rules and targets.

​
Before you start

  • An Operata account with the Group Admin role on the group you want events for.
  • An AWS account where you can administer EventBridge — permission to associate a partner event source and create rules in the target region.
  • Your 12-digit AWS account number and the AWS region that should receive the events.
The partner event source is bound to one AWS account and region. Operata cannot move it after creation. Confirm the destination before you raise the request.

​
Steps

​
1. Request the partner event source from Operata

Email Operata Support with:
  • The 12-digit AWS account number that receives the events.
  • The AWS region the event source must live in.
  • The Operata group the events are for.
Operata creates the partner event source and replies with the Event Source Name — a string of the form aws.partner/operata.com/<operata-group-id>/<event-bus-name>. The source appears in your AWS console under Amazon EventBridge → Partner event sources in the requested region, in the Pending state.

​
2. Associate the partner event source with an event bus

In the AWS console, open EventBridge → Partner event sources in the region Operata provisioned, then:
  1. Select the event source Operata created.
  2. Choose Associate with event bus.
  3. Accept the suggested bus name (it matches the event source name) or set your own.
The state changes from Pending to Active. EventBridge creates a custom event bus under EventBridge → Event buses with the name you accepted.

​
3. Create at least one EventBridge rule

Without a rule, events arrive on the bus and are discarded. Create a rule that matches the event types you care about and routes them to a target:
Common targets: CloudWatch Logs (for inspection), Lambda (for transformation), SQS or Kinesis (for fan-out), or another EventBridge bus in a different account. See the event catalog for the full list of detail-type values.

​
Result

Place a test contact through the Amazon Connect instance Operata is observing, then wait up to 5 minutes for post-contact enrichment. In CloudWatch Logs (or the target you wired up), look for a CallSummary event whose detail.contact.id.current matches the contact ID from the CCP. If no event arrives within 5 minutes:
  • Confirm the partner event source is Active, not Pending.
  • Confirm the rule matches on the source exactly as Operata sent it.
  • Confirm the target has permission to receive events from EventBridge.
  • Event catalog — every detail-type, its payload, and when it fires.
  • Webhooks overview — the delivery model and example consumers.
  • Versioning — how Operata ships additive and breaking changes to event payloads.