ConnectPath – Migration Configuration Steps image

ConnectPath Migration for existing subscribers

On December 1, 2021 the current ConnectPath dashboard will be end of life and replace with the ConnectPath dashboard.  Amazon Connect has created a new TASK router that is now incorporated into ConnectPath.  This new router is the basis of the omni-channel architecture that ConnectPathintroduced almost 3 years ago.   It is a significant new functionality for Amazon Connect and will now be the foundation of our “bring your own channel” feature set.   Today we support Chat, Email, SMS, MMS, Fax and all future feature additions. If you are an existing subscriber to the ConnectPath dashboard, you can easily migrate to the new ConnectPath dashboard!   The migration steps are simple, but specific, so we have published this simple guide to walk you through the modifications to your current configurations to support  ConnectPath.  

Step Summary:

1 – log in to your AWS Management Console and find Lambda functions;

2 – Search for ConnectPath and you will find four function;

3 – Each function has an environmental variable named STAGE, change that value from master to flex (case sensitive) save;

4 – Configure event steam per video ;

5 – Find the S3 bucket that hosts your reports and look at the CORS permissions.  

6 – Login to ConnectPath and go to settings, instance details and verify that your recording bucket is correctly listed;

Let us know if you need assistance opening a ticket on this website!


Use the new event bridge data to keep the LiveLook widget 100% accurate. Amazon Connect announced a new feature to stream Contact related events and Flex can consume this data to greatly improve the accuracy of the Live Look widget. Follow the steps outlined in the link below and use the streamHandler function as the destination. (Optional)

This video walks you through that change.

Sample Code for Event Bridge modification


“source”: [“aws.connect”],

“detail-type”: [“Amazon Connect Contact Event”, “Contact Lens Analysis State Change”],

“detail”: { “instanceArn”: [“arn:aws:connect:us-east-1:123456789instance/fdb6ef6e-3671-417e-a0eb-1e9217f7475b”]



(remember to change the instanceARN to the corrected ARN to reflect your instance ID)