At this point, you have properly configured your Salesforce instance. The next step is to whitelist your Salesforce domain within your Amazon Connect Application integration. This is required from a security perspective to ensure you are allowing cross-domain access to your Amazon Connect instance.
To whitelist your pages:
•Login to your AWS Account, then navigate to the Amazon Connect console
•Click the instance name of the instance for which you would like to white list pages to load the settings page for your instance
•Click the "Application integration" link on the left
•Click "+ Add Origin", then enter a domain URL, e.g. "https://example.com", or "https://example.com:9595" if your website is hosted on a non-standard port.
•All below listed domains have to be added for the Salesforce whitelisting - Classic, Lightning and mydomain name. Even if you are not using Classic, you should add the URL
If you know your My Domain name and instance ID you can build the URL automatically
Example: My Domain is mycompany - Instance ID is EU17
•https://mycompany--mirage.EU17.visual.force.com
•https://mycompany--mirage.visualforce.com
•https://mycompany.my.salesforce.com
•https://mycompany.lightning.force.com
For a developer instance you have to add -dev-ed to the My Domain name and build the URL without instance ID
•https://mycompany-dev-ed--mirage.visualforce.com
•https://mycompany-dev-ed.my.salesforce.com
•https://mycompany-dev-ed.lightning.force.com
You can also manually retrieve all URLS
Switch to lightning in Salesforce. Copy the entire URL of this page and past it to a text document and add the domain part in the Amazon Connect application integration origin
If you’re unsure of the Salesforce Visualforce domain, you can find it by previewing the URL of the Amazon Connect Visualforce page within your Salesforce instance.
Click on Preview button in front of page name to load the visual force page in new tab.
The application integration screen after adding all the three domains of Salesforce.
•Whitelisted domains must be HTTPS.
•Using multiple browsers at the same time for the same connect instance is not supported, and causes issues with the RTC communication.