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 ARNoperataEndpointGroup-{Operata-Group-ID}.
Lambda service role
Trust policy
Managed policy
Attach the AWS managed policyAWSLambdaBasicExecutionRole. 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 patterncloud-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.- Create the Secrets Manager secret
cloud-collector-v3/ctr/{Operata Group ID}/apiTokenwith your Operata API token as the value. - Create the Lambda service role with the
lambda.amazonaws.comtrust policy. AttachAWSLambdaBasicExecutionRole, the Secrets Manager policy, the EC2 ENI policy (VPC only), and the S3 policy (upsert only). - Create the EventBridge Pipe execution role with the
pipes.amazonaws.comtrust policy. Attach the Kinesis source, Lambda invocation, and API destination policies. - Deploy the redactor Lambda. Name pattern
CloudCollectorV3Stack-cloudcollectorv3redactor-{unique-id}, runtimeprovided.al2, handlerbootstrap, timeout 60 seconds. - Create the EventBridge connection
operataAPIgroup-{Operata Group ID}withAPI_KEYauthentication and headerOperata-API-Key. - Create the EventBridge API destination
operataEndpointGroup-{Operata Group ID}. Endpointhttps://api.operata.io/v2/aws/events/contact-record, methodPOST. - 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"] } }.
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
Related
- Concept: Cloud Collector — the data path these roles serve.
- Install CTR collection — the default CloudFormation deploy.
- KMS encryption — adds CMK access to the EventBridge Pipe role.
- Troubleshoot the AWS integration — covers Secrets Manager rotation and connection failures.