Why are we doing this?
AWS periodically deprecates Lambda runtime version support.
Operata has new CloudFormation templates that update your Operata Stack Lambdas to supported versions: Python 3.13 and Amazon Linux 2023.
β
βWhat you need to know before starting:
β± The update takes approximately 5β10 minutes per stack.
π This update does change the data being collected.
How to apply each update:
Follow the steps below for each stack you need to update.
Log in to the AWS Management Console and navigate to CloudFormation.
Select the relevant stack from the list (typically contains the word Operata in the name).
Click Update stack (top right) β select Make a direct update.
Under Prepare template, select Replace existing template.
Under Specify template, select Amazon S3 URL.
βPaste the template URL for your stack (see URLs listed below) into the Amazon S3 URL field and click Next.
Step through the remaining wizard pages, leaving all parameters unchanged unless advised by Operata.
Submit the update and monitor the Events tab until the stack shows
UPDATE_COMPLETE.
Stacks to update
You'll need to update up to three stacks for each Operata Group, depending on your Operata configuration.
1. Contact Trace Records (CTR)
Use this template URL when updating your CTR stack:
2. Contact Lens Data (CLD)
Use this template URL when updating your Contact Lens Data (CLD) stack:
β
β οΈ Additional step required: VPC-configured installations only (Show Steps)
β οΈ Additional step required: VPC-configured installations only (Show Steps)
The Contact Lens Data stack creates ENI (Elastic Network Interface) resources that must be manually deleted during the update so it can complete successfully. Skipping this step may cause the stack update to stall or fail.
To find and delete ENI resources:
In the AWS Management Console, navigate to EC2 β Network Interfaces (under Network & Security).
Click the Search bar at the top of the list.
Select Security group name from the dropdown filter options.
Type the partial name (e.g.
operata-contactlens) and hit Enter.
This will show all ENIs associated with that Security Group.
β
5. Copy the Network Interface IDs from the results.
6. Update the ENI IDs in the script below with the values you copied.
Template Bash Script:
β
for ENI_ID in \
eni-0a1b2c3d4e5f67890 \
eni-0b2c3d4e5f6a78901 \
eni-0c3d4e5f6a7b89012; do
echo "=== Processing $ENI_ID ==="
aws ec2 describe-network-interfaces \
--network-interface-ids $ENI_ID \
--query "NetworkInterfaces[0].{Status:Status,AttachID:Attachment.AttachmentId}" \
--output table \
--region ap-southeast-2
ATTACH_ID=$(aws ec2 describe-network-interfaces \
--network-interface-ids $ENI_ID \
--query "NetworkInterfaces[0].Attachment.AttachmentId" \
--output text --region ap-southeast-2)
if [ "$ATTACH_ID" != "None" ] && [ -n "$ATTACH_ID" ]; then
echo "Detaching $ATTACH_ID..."
aws ec2 detach-network-interface \
--attachment-id $ATTACH_ID \
--force \
--region ap-southeast-2
sleep 5
fi
echo "Deleting $ENI_ID..."
aws ec2 delete-network-interface \
--network-interface-id $ENI_ID \
--region ap-southeast-2
done
7. Run the updated script in AWS CloudShell, replacing the placeholder ENI IDs with the values from in step 5.
3. Contact Lens Rules (CLR)
The Contact Lens Rules stack cannot be updated in place.
You must uninstall the current stack and then install the new one.
Use this template URL when installing your Contact Lens Rules stack:
https://s3.ap-southeast-2.amazonaws.com/operata-customer-assets/contact-lens-operata-rules.yaml
β
βStep 1: Uninstall the existing CLR stack
In CloudFormation, select your existing Contact Lens Rules stack (typically contains "ContactLensRules" or similar).
Click Delete.
Confirm deletion and wait until the stack status shows DELETE_COMPLETE before proceeding.
Step 2: Install the new CLR stack
In CloudFormation, click Create stack β With new resources (standard).
Under Prepare template, select Template is ready.
Under Specify template, select Amazon S3 URL and paste:
https://s3.ap-southeast-2.amazonaws.com/operata-customer-assets/contact-lens-operata-rules.yamlClick Next and provide a stack name (e.g.
OperataContactLensRules).Step through the remaining wizard pages, leaving parameters at their defaults unless advised by Operata.
Submit and monitor the Events tab until the stack shows CREATE_COMPLETE.
How to verify Lambda runtime versions
Confirm the update applied correctly by checking your Lambda functions:
In the AWS Console, go to Lambda β Functions.
Search for
operataor sort by Last Modified.Confirm each function shows the updated runtime listed in the table below:
Stack | Lambda Resource Name | Original Runtime | Updated Runtime |
Contact Trace Records | OperataAWSIntegration-CTR-cloudcollectorv3redactor | Amazon Linux 2 | Amazon Linux 2023 |
Contact Lens Data | OperataAWSIntegration-CLD-BucketNotificationsHandl | Python 3.9 | Python 3.13 |
Contact Lens Data | OperataAWSIntegration-CLD-ccv3s3kinesisintegrator | Amazon Linux 2 | Amazon Linux 2023 |
How to verify it's working
Place or receive a short test call on your Amazon Connect instance, then verify data appears in the following locations:
Test call data may take up to 5 minutes to appear in Operata. Remember to Close Contact if testing for inbound call data.
1. Check API activity
Go to Group Settings β Integrations β API Management and confirm the API Key shows a recent "Last Used" timestamp. This confirms your stack is actively sending data to Operata.
2. Check CTR Data
3. Check Contact Lens Data
Contact Lens Data (CLD) stack β Dashboards β Conversational Analytics
Filter by the test agent name, or sort by most recent call.
Allow up to 5 minutes for the call to appear.
If it doesn't show after 10 minutes, proceed to the troubleshooting steps below.
β
If data isn't appearing after 10 minutes
Work through the checklist below before contacting Operata support:
ENIs not deleted (CLD stack only)
If you skipped the ENI deletion step, the Contact Lens Data stack may have stalled or rolled back. Check CloudFormation β Events for errors, then re-attempt the ENI cleanup and update.Stack didn't complete successfully
In CloudFormation, confirm each stack shows UPDATE_COMPLETE. If any show UPDATE_ROLLBACK_COMPLETE or UPDATE_FAILED, do not retry without contacting Operata first.Wrong template URL used
Double-check that the S3 URL you pasted matches the correct stack type (CTR, CLD, or CLR). Using the wrong template for a stack is a common cause of unexpected errors.Parameters were changed during the update
The update wizard prompts you to review existing parameters. If any values were modified, they may need to be restored. Re-check against your original stack configuration.Lambda runtimes haven't changed
If the functions still show the original runtime after the update, the stack change may not have applied. Verify the stack status and re-check the Last Modified timestamp on the Lambda functions.API Key shows no recent activity
If Group Settings β Integrations β API Management shows no recent usage, your stack may not be sending data. This usually points to a failed or incomplete stack update.
Need help?
If you run into any issues or aren't sure which stacks apply to your setup, we're here to help.
β
π§ Email us at help@operata.com
π¬ Or send a message directly from within the Operata application















