Skip to main content
Operata’s Amazon Connect integration uses two AWS Identity and Access Management (IAM) roles: the Amazon EventBridge Pipe execution role and the Lambda service role. The default AWS CloudFormation template creates and wires both. This page lists every trust policy, attached policy, and the administrator policy you need when deploying manually.
The default CloudFormation template creates and attaches every role and policy on this page. Read it only if you need to audit, modify, or deploy the integration manually outside CloudFormation.

Roles

EventBridge Pipe execution role

Trust policy

Kinesis source policy

Reads Contact Trace Records (CTRs) from the Amazon Connect Kinesis stream.

Lambda invocation policy

Invokes the redactor Lambda for enrichment and redaction.

API destination policy

Sends processed events to the Operata API destination. CloudFormation names the destination ARN operataEndpointGroup-{Operata-Group-ID}.

Lambda service role

Trust policy

Managed policy

Attach the AWS managed policy AWSLambdaBasicExecutionRole. It grants the Lambda permission to write to CloudWatch Logs.

Secrets Manager access policy

Reads the Operata API token from Secrets Manager. The secret name follows the pattern cloud-collector-v3/ctr/{Operata Group ID}/apiToken.

EC2 network interface policy

Required only when the Lambda runs in a VPC. Lets it create and manage the network interfaces in the deployment subnets.

S3 access policy

Required only when CTR upsert is enabled. Lets the Lambda read agent data files from your S3 bucket.

Administrator deployment policy

For manual installs outside CloudFormation, attach the following policy to your deploying principal. It covers the minimum permissions to create every resource the integration uses.

Manual deployment order

For manual installs, create resources in this order. Each step assumes you have attached the administrator policy above to your deploying principal.
  1. Create the Secrets Manager secret cloud-collector-v3/ctr/{Operata Group ID}/apiToken with your Operata API token as the value.
  2. Create the Lambda service role with the lambda.amazonaws.com trust policy. Attach AWSLambdaBasicExecutionRole, the Secrets Manager policy, the EC2 ENI policy (VPC only), and the S3 policy (upsert only).
  3. Create the EventBridge Pipe execution role with the pipes.amazonaws.com trust policy. Attach the Kinesis source, Lambda invocation, and API destination policies.
  4. Deploy the redactor Lambda. Name pattern CloudCollectorV3Stack-cloudcollectorv3redactor-{unique-id}, runtime provided.al2, handler bootstrap, timeout 60 seconds.
  5. Create the EventBridge connection operataAPIgroup-{Operata Group ID} with API_KEY authentication and header Operata-API-Key.
  6. Create the EventBridge API destination operataEndpointGroup-{Operata Group ID}. Endpoint https://api.operata.io/v2/aws/events/contact-record, method POST.
  7. Create the EventBridge Pipe operataEventsPipe-{Instance Name}-amazonConnect. Source: the Kinesis CTR stream. Enrichment: the redactor Lambda. Target: the API destination. Filter: { "data": { "Channel": ["VOICE"] } }.
Verify the pipe status is RUNNING and watch CloudWatch Logs for the Lambda function. Place a test contact through Amazon Connect and follow Verify the integration on the installation guide.

Common deployment errors