Lambda functions reference the the aws-quickstart bucket directly. We should migrate to the CopyZips pattern

onnect-integration-aspect-wfm    master ❯ egrep -i 'S3Key' -B1 -R *                4245   22:26:29
templates/aspect-wfm-rta.template-        S3Bucket: aws-quickstart
templates/aspect-wfm-rta.template:        S3Key: connect-integration-aspect-wfm/functions/packages/real-time-adherence/AspectKinesisLambda.zip
--
templates/aspect-wfm-ap-kda.template-        S3Bucket: aws-quickstart
templates/aspect-wfm-ap-kda.template:        S3Key: connect-integration-aspect-wfm/functions/packages/agent-productivity/lambda.zip

The Lambda function created by the 'Real Time Adherence' Stack seems to intermittently error out when attempting to write agent states into DynamoDB. Once the error occurs, the Lambda function is unable to update DynamoDB. The Lambda function is then continuously called by the Kinesis Data Stream with the same payload that produces the error. This stops within about 2 days, after which the Lambda function resumes working as normal.

I do not have a precise method to reproduce the error but I have not been able to conduct testing sessions (where I'm moving an agent within Amazon Connect through various states) for more than about 20 minutes before it occurs.

In a nutshell, if you:

• deploy a working (agent able to log in and change states) instance of Amazon Connect
• deploy this quickstart selecting the option to 'Deploy for real-time adherence' OR 'Deploy for both options'
• monitor either the Lambda function or DynamoDB objects created by the quickstart
• login to Amazon Connect as your agent and continue to change states

This error (message from Lambda > Cloudwatch logs below) should rear its head at some point.

One or more errors occurred. (Unable to convert hash key value for property AgentARN): AggregateException
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at lambda_method(Closure , Stream , Stream , LambdaContextInternal )

at Amazon.DynamoDBv2.DataModel.DynamoDBContext.MakeKey(Object hashKey, Object rangeKey, ItemStorageConfig storageConfig, DynamoDBFlatConfig flatConfig)
at Amazon.DynamoDBv2.DataModel.DynamoDBContext.LoadHelperAsync[T](Object hashKey, Object rangeKey, DynamoDBOperationConfig operationConfig, CancellationToken cancellationToken)
at Amazon.DynamoDBv2.DataModel.DynamoDBContext.LoadAsync[T](Object hashKey, CancellationToken cancellationToken)
at AspectKinesisLamda.ProcessKinesisEvents.ProcessEventToTable(ConnectKinesisEventRecord streamRecord)
at AspectKinesisLamda.ProcessKinesisEvents.ProcessEventRecord(KinesisEventRecord record, Boolean writeEventsToQueue)
at AspectKinesisLamda.ProcessKinesisEvents.AspectKinesisHandler(KinesisEvent kinesisEvent, ILambdaContext context)

Python 2.7 is EOL in January 2020. We need to upgrade the CopyZips function prior to then.

@andrew-glenn can you merge the changes from the develop branch back to the master branch for this repo and push those changes out to the aws-quickstart S3 bucket(s)? One of Aspect's customers is about to deploy this integration, so we'd like to take advantage of these enhancements.

I get the following error in CloudFormation if I try to create a stack using any of the CloudFormation templates of this integration.

The CloudFormation template filenames for this QuickStart were renamed recently. The template extensions were changed from .template to .template.yaml. Most of the links on the AWS QuickStart page were updated, but one was missed. It looks like the link under the left column (For a new Kinesis data stream) for Deploy real-time adherence is missing the .yaml.