Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s3: S3 object notifications managed from multiple stacks interfere with each other #28120

Open
rix0rrr opened this issue Nov 23, 2023 · 0 comments
Labels
@aws-cdk/aws-s3 Related to Amazon S3 bug This issue is a bug. effort/medium Medium work item – several days of effort p1

Comments

@rix0rrr
Copy link
Contributor

rix0rrr commented Nov 23, 2023

Describe the bug

When S3 object notifications are added to referenced bucket from 2 or more different stacks, changes to the notification prefix on one of the stacks can delete the notifications of the other stack.

Probable bug in the custom resource.

Internal reference P103121314

Expected Behavior

The notifications to be updated as expected.

Current Behavior

There is some interference between stacks.

Reproduction Steps

Create 3 stacks:

  • One a with a bucket
  • Reference that bucket from the other 2 stacks and create object notifications on them
  • Deploy
  • Change the prefix on one of the stacks
  • Observe what happens

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

Framework Version

No response

Node.js Version

OS

Language

TypeScript

Language Version

No response

Other information

No response

@rix0rrr rix0rrr added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Nov 23, 2023
@github-actions github-actions bot added the @aws-cdk/aws-s3 Related to Amazon S3 label Nov 23, 2023
@rix0rrr rix0rrr added the p1 label Nov 23, 2023
@pahud pahud added effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-s3 Related to Amazon S3 bug This issue is a bug. effort/medium Medium work item – several days of effort p1
Projects
None yet
Development

No branches or pull requests

2 participants