Log group "already exists" error after CDK/L3 construct upgrade

[ananththangaraj]

I'm encountering an error stating that a log group already exists. After investigation, I discovered that the log group was originally created implicitly by Lambda on first invocation. However, with the upgrade to cdk-ecr-deployment v2.5.0 and above, the log group is now explicitly created and managed by CloudFormation with a specific LogGroupName.

This issue surfaced after upgrading packages in our L3 constructs:

aws-cdk: from 2.179.0 to 2.1017.1
aws-cdk-lib: from 2.187.0 to 2.200.0
Is there a way to resolve this without downgrading the package or manually deleting the existing log group
Any guidance or best practices for handling this scenario would be appreciated.

Error:

Resource handler returned message: "Resource of type 'AWS::Logs::LogGroup' with identifier '{"/properties/LogGroupName":"/aws/lambda/xxxxxxxxxx"}' already exists." (RequestToken: 4ae3269b-6f5e-87d3-1d55-922d4f418ddb, HandlerErrorCode: AlreadyExists)

[aemada-aws]

See #34612

You need to upgrade aws-cdk-lib v2.200.1 or later.