Use of AWS components and infrastructure

This article describes how the Amazon Connect for Zendesk app and its add-ons use AWS SDK and Amazon Connect Streams API for integration. This pertains to version numbers specified in the table below and is updated with future releases.

Application	Version	Amazon Connect Stream API	AWS SDK
Core app	2.3.1	Version 1.7.5, minified .js lib embedded in the app	When Pause/Resume add-on is enabled: AWS SDK for JavaScript v2, using Connect service for `suspendContactRecording`, `resumeContactRecording`, and `updateContactAttributes` API methods. It uses temporary credentials obtained via STS `assumeRole`, generated via a lambda triggered from from within the Amazon Connect contact flow.
Pause/Resume add-on	1.0.2	N/A	Lambda triggered from Connect contact flow. AWS SDK for JavaScript v2, calls STS service to issue temporary credentials. IAM role is created via CloudFormation deployment from SAR and includes `AWSLambdaBasicExecutionRole` policy and a customer managed policy with permissions for STS
Zendesk Search add-on	1.0.3	N/A	Lambda triggered from Connect contact flow. No AWS services used (only 3rd party APIs). IAM role is created via CloudFormation deployment from SAR and includes `AWSLambdaBasicExecutionRole` policy only.
Contact Lens add-on	1.0.4	N/A	Lambda triggered from an S3 bucket with Contact Lens records on “PUT” event. AWS SDK for JavaScript v2, optionally calls DynamoDB service to store failed Zendesk searches to retry at a later time. IAM role is created via CloudFormation deployment from SAR and includes `AWSLambdaBasicExecutionRole` policy and customer managed policy to read from S3, decrypt with KMS and perform CRUD operations on DynamoDB table.