Deployment Failed - SolutionHelperFunction

[RDurkin-GitHub]

Hi

When deploying the Cloudformation template. I am getting the following error with the logical ID SolutionHelperFunction.

Resource handler returned message: "Error occurred while GetObject. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist. (Service: Lambda, Status Code: 400, Request ID: e09e4840-b9ca-4905-a71b-5a3e39c7bc86)" (RequestToken: 5308925e-dee0-76bf-e35e-0969aec20026, HandlerErrorCode: InvalidRequest)

Regards Richard

[davelemons]

Can you let us know how your are deploying the solution. Are you using the Main branch or Development branch? Based on the info below we recommend using the updated templates found here

Starting in April 2023 Amazon S3 made a change to set the Bucket Owner Enforced Setting to be enabled for any newly completed buckets which disables ACLs. Since this solution uses Default ACLs, this new default will prevent the CloudFormation stack from deploying. More Information....

The main and development branches have been updated to account for the recent S3 changes. Updated CloudFormation Templates and deployment instructions can be found here

[RDurkin-GitHub]

Hi

I had AWS to have a look as to why it is failing and they said that it was looking for the following file: "aws-connect-vm. zip"

[RDurkin-GitHub]

you need to ensure that the right s3 file( aws-connect-vm. zip) is added as part of the prefix deployment/aws-connect-vm-serverless/) in order to resolve the issue

[RDurkin-GitHub]

[RDurkin-GitHub]

I can not find this file that it is referencing

[virtualgill]

Hi Richard,

Are you by any chance attempting to deploy the cloudformation templates in https://github.com/amazon-connect/voicemail-for-amazon-connect/blob/master/deployment directly? The file you are missing is created as part of the build process, so if you are wanting to deploy from your own S3 bucket make sure to follow the instructions here: https://github.com/amazon-connect/voicemail-for-amazon-connect/blob/master/README.md#building-distributable-for-customization

Alternatively, as Dave as referenced, you can download and use the templates here: https://aws-contact-center-blog.s3.us-west-2.amazonaws.com/voicemail-s3-default-acl-issue/vmv1s3fix.zip which has alternate cloudformation files and updated README.

Let me know if using one of those methods fixes your issue.

[karl-mentzer]

@virtualgill @davelemons - I have previously discussed this solution with Luke W extensively before his departure so pretty familiar with it, and I tested this myself tonight as part of an upgrade for a client (to change the Bucket versioning for the logging bucket as its generating unnecessary data) as well as adding a retention policy to the recording bucket and removing versioning there also.

I found that both the aws-connect-vm.zip and the voicemail-for-amazon-connect.template file were not generated / uploaded to the bucket during the build process so it does appear to be an issue. Suggest testing with a fresh build.

[RDurkin-GitHub]

Hi

When I build it (https://github.com/amazon-connect/voicemail-for-amazon-connect/blob/master/README.md#building-distributable-for-customization), it doesn't have both files mentioned above.
When I try with the link https://aws-contact-center-blog.s3.us-west-2.amazonaws.com/voicemail-s3-default-acl-issue/vmv1s3fix.zip, it fails as well with the aws-connect-vm.zip error.