Hi, I witnessed an odd behavior when deploying an EventBus with an attached policy.
I cannot reproduce the issue, but I'm reporting it because it happened to our production system, and I have no explanation.
The issue is:
We deployed an EventBus with a valid policy attached to it via AWS CDK, and the policy existed and was shown in the AWS Console. We used this policy for cross-account access, so I know it has worked up to a certain point in the past.
After an unknown time (days/weeks), the policy "disappeared," meaning the AWS Console showed no policy attached to the resource. However, the policy resource was still listed in the CloudFormation stack.
Running a CDK diff showed no changes to the AWS::Events::EventBusPolicy object, and when running a drift check, no changes were reported. Also, no policy was listed when fetching the EventBus object via the describe API call.
All that was returned in the description API call was:
When I then updated the policy and altered a section of it, the diff correctly reported the change. On deployment, the policy was updated and shown in the AWS Console and the describe API call.
Expected Behavior
We expected the policy not to disappear.
Observed Behavior
The policy disappeared while still being listed in the CloudFormation stack.
Name of the resource
AWS::Events::EventBusPolicy
Resource Name
No response
Issue Description
Hi, I witnessed an odd behavior when deploying an EventBus with an attached policy.
I cannot reproduce the issue, but I'm reporting it because it happened to our production system, and I have no explanation.
The issue is:
Running a CDK diff showed no changes to the
AWS::Events::EventBusPolicyobject, and when running a drift check, no changes were reported. Also, no policy was listed when fetching the EventBus object via the describe API call.All that was returned in the description API call was:
When I then updated the policy and altered a section of it, the diff correctly reported the change. On deployment, the policy was updated and shown in the AWS Console and the describe API call.
Expected Behavior
We expected the policy not to disappear.
Observed Behavior
The policy disappeared while still being listed in the CloudFormation stack.
Test Cases
I'm unable to reproduce the issue.
Other Details
No response