aws / aws/aws-cdk

AWS::CloudFront::KeyValueStore: Invalid Tags property being written since 2.235.0

Open
#36,765 4 comments 2 reactions 0 assignees View on GitHub
aws-cdk-lib bug needs-cfn p1 potential-regression
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
2d 3h
Merged PRs (30d)
83

Description

### Describe the bug

In version 2.234.1, no Tags are written, can deploy.

In version 2.235.0 and 2.235.1, Tags are written, get error deploying.
> First failed resource , Type:AWS::CloudFront::KeyValueStore, StatusReason:Properties validation failed for resource with message: [#: extraneous key [Tags] is not permitted]

### Regression Issue

- [x] Select this option if this issue appears to be a regression.

### Last Known Working CDK Library Version

2.234.1

### Expected Behavior

I can deploy

### Current Behavior

I can't deploy

### Reproduction Steps

Will come back to this if needed.

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### AWS CDK Library version (aws-cdk-lib)

-- (empty)

### AWS CDK CLI version

2.1027.0

### Node.js Version

22.11.0

### OS

Windows

### Language

.NET

### Language Version

_No response_

### Other information

I've given versions on my local machine, but I'm using the .NET nuget package and it's failing in CI too (whatever latest github runner versions are).

Contributor guide

Open the contributing guide

Research direction

Start by comparing AWS::CloudFront::KeyValueStore handling between CDK versions 2.234.1 and 2.235.0, using the reported .NET deployment scenario and CLI version as context. Reproduce the deployment failure and verify that the completed change no longer emits the unsupported Tags property and allows deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.