Skip to main content
The Cloud Collector on Amazon Connect fails in four common ways: CTR delivery gaps, CloudFormation failures, integration monitoring gaps, and stale Operata secrets. Start at the section that matches your symptom.

​
Before you start

  • Admin access to the AWS account hosting the Cloud Collector.
  • The Operata Group ID for the integration.
  • AWS CLI configured with permissions for CloudWatch, Secrets Manager, and Amazon EventBridge.

​
Contact Trace Records are not appearing in Operata

​
Wait at least five minutes

Contact Trace Records (CTRs) only emit when the contact is fully closed. Allow up to five minutes between the contact ending and the record appearing in Operata. Check the basics:
  • The Agent Collector is installed in the agent’s browser.
  • The CCP URL matches the Amazon Connect instance the stack was deployed against.
  • The agent closed the contact (set status to After Contact Work → Available or similar).

​
Check the source Kinesis stream for KMS encryption

If the Kinesis CTR stream uses a customer-managed AWS Key Management Service (KMS) key, the Amazon EventBridge Pipe execution role needs decrypt permission. Follow Grant KMS access to the EventBridge Pipe.

​
Check the EventBridge Pipe status

In the AWS console, open EventBridge → Pipes and find operataEventsPipe-{instance}-amazonConnect. The status should be RUNNING. Click into the pipe and check Monitoring for delivery failures. The most common failures are KMS access denied (see above), Lambda timeouts (raise the Lambda’s memory or VPC routing), and API destination 4xx responses (regenerate the Operata API token).

​
Check the redactor Lambda logs

In the AWS console, open CloudWatch → Log groups and find /aws/lambda/CloudCollectorV3Stack-cloudcollectorv3redactor-…. Look for ERROR or Task timed out. Forward the relevant log lines to Operata Support.

​
CloudFormation deployment fails

​
Verify the deploying principal’s IAM permissions

The stack creates IAM roles, Secrets Manager secrets, Amazon EventBridge resources, and a Lambda. Confirm the deploying principal has the administrator deployment policy attached, or equivalent permissions.

​
Check for leftover resources from a prior install

If CloudFormation reports ResourceAlreadyExists on Secrets Manager or the EventBridge connection, an earlier install left state behind. Follow Rotate or delete Operata secrets below, then re-run the stack.

​
Send the failure to Operata Support

If the deploy still fails, take a screenshot of the Events tab of the failed CloudFormation stack and send it to Operata Support.

​
Monitor the integration

The Amazon EventBridge Pipe and the redactor Lambda emit CloudTrail events and CloudWatch metrics. Operata recommends:
  • CloudWatch alarm on Invocations failing for the redactor Lambda (above zero over five minutes).
  • CloudWatch alarm on EventBridge Pipe delivery failures (above zero over five minutes).
  • CloudTrail trail for all events, pipes, and lambda API calls in the integration region.
For details on Pipe-specific monitoring, see Monitoring EventBridge Pipes in the AWS documentation.

​
Rotate or delete Operata secrets

The Cloud Collector stores credentials in two places:
  1. cloud-collector-v3/ctr/{Operata Group ID}/apiToken in Secrets Manager — the Operata API token the Lambda uses to authenticate.
  2. events!connection/operataAPIgroup-{Operata Group ID}/… in Secrets Manager — created by EventBridge when the API destination was registered. Holds the API destination connection credentials.
Rotate or delete them when you rotate the Operata API token, decommission the integration, or hit a ResourceAlreadyExists error on redeploy.
Deleting the API token secret immediately stops CTR delivery.The Lambda can’t authenticate with Operata while the secret is gone. No CTRs reach the Operata API until you create a new secret with a valid token.

​
Delete the Secrets Manager API token

​
Delete the EventBridge connection secret

Deleting the EventBridge connection deletes the associated secret.

​
Console alternative

In the AWS console, open Secrets Manager, filter on cloud-collector-v3, select the secret, and choose Actions → Delete. To delete the EventBridge connection, open EventBridge → API destinations → Connections and delete operataAPIgroup-{Group ID}.

​
Restore the integration after deletion

  1. If you used the default recovery window, wait it out, or restore the secret in the console.
  2. Update the CloudFormation stack — re-running it with a valid API token recreates both secrets.
  3. Verify the pipe status returns to RUNNING and CTRs flow again under Contact Trace Records are not appearing in Operata.

​
Verify

Place a test contact through Amazon Connect. Within five minutes of contact end, the contact appears in Get the Details in the Operata console. If it doesn’t, the EventBridge Pipe monitoring panel shows the failure reason.

​
What next