Describe the bug

Upgrading from v2.204.0 to v2.205.0 of the aws-cdk-lib package causes our deployments to fail as they require the same tags as the ones we apply to our stack resources via an aspect. We have an SCP policy that enforces this tagging. Reverting to 2.204.0 works but the issue remains in the latest 2.208.0.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Library Version

2.204.0

Expected Behavior

CloudFormation changesets created by the CDK deploy role should be tagged in the same way as the stack resources.

Current Behavior

No tags are being applied and the deployment fails because our SCP requires those tags to be present for the changeset.

Reproduction Steps

Create a new CDK app - will have a dependency on v2.205.0 or higher. Perform any kind of deployment with either an SCP requiring tags on changeset or IAM boundary attached to the CDK deploy role requiring the same.

Possible Solution

Check the change and rollback that aspect of it to be consistent with v2.204.0.

Additional Information/Context

No response

AWS CDK Library version (aws-cdk-lib)

2.205.0

AWS CDK CLI version

2.1022.0

Node.js Version

20.11.1

OS

Ubuntu

Language

TypeScript

Language Version

5.6.3

Other information

No response