Error while deploying multiple VoD projects within the same environment

[nathanagez]

Describe the bug When we try to deploy multiple VoD projects within the same environment with signed urls, CloudFormation returns an error concerning the public key:

Following resources failed

Resource Name: rCloudFrontPublicKeyXXXXXX (AWS::CloudFront::PublicKey)
Event Type: create
Reason: Resource of type 'AWS::CloudFront::PublicKey' with identifier 'projectName-env-publickey-XXXXXX' already exists.

To Reproduce Steps to reproduce the behavior:

Firstly, create a basic VoD project with signed urls and without a GraphQL API for the CMS. Then do an amplify push, it should deploy everything correctly.

After doing that, add a new VoD project to the same environment with the same settings (signed urls and no GraphQL API for the CMS). Then do an amplify push, the error should happen during the deployment.

Expected behavior The new project should be deployed inside the Cloud and the buckets should not be created if it fails.

Screenshots

If you do a new amplify push just after the fail:

Desktop (please complete the following information):

• OS: macOS 11.1 (20C69)
• amplify-video version: amplify-category-video@3.2.1
• amplify-cli: 4.41.2
• node: v12.16.3

[sak360]

I am seeing the same error when trying to create a second environment (and not adding two VoDs to the same environment)

[o-gi]

Same here.My use case is that I need a bucket that requires a login protected by a signed URL to play VOD (protected) and a bucket that can be played without a login (public). I don't know how to do this.

[djsjr]

Any update here? Same issue. Trying to create a separate bucket for audio only.

[djsjr]

@wizage Anything on this? I still cannot create two separate buckets successfully. Regarding the first error message I receive (same as OP), why would pushing a new video resource result in attempting to create a 'CloudFront::PublicKey' with the same identifier as the first video resource?

Would be great to see a solution for this