(aws-s3): (cdk calls DeleteBucketPolicy and PutBucketNotification at the same time causes an conflicting operation error.)

[hulu-xu]

Describe the bug

We often get these occasional errors in our smoke tests deployed by aws cdk.

By digging through the event logs in cloudtrail, we found that if cdk calls DeleteBucketPolicy and PutBucketNotification at the same time. One of these operations will raise an error for a conflicting operation.

Expected Behavior

The operations on the bucket can be performed in sequence.

Current Behavior

cdk calls DeleteBucketPolicy and PutBucketNotification at the same time causes an conflicting operation error.

Reproduction Steps

This error is uncontrollable. It is sometimes absent and sometimes too frequent. It always occurs when deleting a bucket stack with a bucket policy and bucket notifications.

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.59.0

Framework Version

No response

Node.js Version

16

OS

linux

Language

Python

Language Version

3.10

Other information

No response

[peterwoodworth]

Could you please detail more information regarding your setup, which constructs are producing this error and how you've configured them (reproduction code), how often this is occurring, etc.

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[hulu-xu]

Hi @peterwoodworth , we use both of these methods to add configurations to the bucket and then deploy it via cdk deploy. When running cdk destroy, a conflicts operation error sometimes occur.
https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_s3/IBucket.html#aws_cdk.aws_s3.IBucket.add_event_notification
https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_s3/IBucket.html#aws_cdk.aws_s3.IBucket.add_to_resource_policy

[hulu-xu]

same issue 16811

[peterwoodworth]

It looks like we can close this as a duplicate then 🙂 Thanks for reporting

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.