Issue Summary

Deployment of serverless-component fails with error CloudFrontOriginAccessIdentityAlreadyExists with both serverless@2.72.x and serverless@3.x.x

Actual behavior

For about a month the deployments of serverless-component@3.7.0 with serverless@2.72.2 are failing with error:
CloudFrontOriginAccessIdentityAlreadyExists: The caller reference you are using to create the CloudFront origin access identity is associated with another identity.
We tried several serverless version 3.x.x but we get the same error.

Expected behavior

No Cloudfront related errors

Steps to reproduce

CloudFrontOriginAccessIdentityAlreadyExists: The caller reference you are using to create the CloudFront origin access identity is associated with another identity.

Screenshots/Code/Configuration/Logs

Versions

serverless@3.0.0
serverless@2.72.2
serverless-component@3.7.0

Additional context

Checklist

• You have reviewed the README and FAQs, which answers several common questions.
• You have reviewed our DEBUGGING wiki and have tried your best to include complete information and reproduction steps (including your configuration) as is possible. As there is only one maintainer (who maintains this in his free time) and thus very limited resources, if you have time, please try to debug the issue a bit yourself if possible.
• You have first tried using the most recent latest or alpha @sls-next/serverless-component release version, which may have already fixed your issue or implemented the feature you are trying to use. Note that the old serverless-next.js component and the serverless-next.js plugin are deprecated and no longer maintained.