Event bus: UPDATE_FAILED: Unsupported Operation
All of a sudden we started to get UPDATE_FAILED errors with "Unsupported Operation" error message for the event bus.
We use infra-as-code (CDK) approach and I am tracking the changes, and there were NO infra changes, other than tags changing (e.g. build ID, git sha).
I am also doing a cdk diff and it produces no meaningful changes, other than tags.
Yet, CloudFormation has been failing for days with the aforementioned message.
We most definitely did not make any changes to event bridge (bus) itself or anything surrounding that.
Any ideas?
- Newest
- Most votes
- Most comments
Got a response from the Amazon support team:
To begin with I would like to inform you that this is a known issue by our CloudFormation service team, and they are already working on a fix for this issue. The issue is caused by updating stack-level tags(not resource level tags i.e., even without specifically having made changes to the resource) on “AWS::Events::EventBus” resource type. The current workaround is to not make any changes to the stack-level tags used by any stacks containing an “AWS::Events::EventBridge“ resource. This will result in this resource not being updated thus allowing you to resume with update of your stacks without facing this error.
Also, we were able to replicate the scenario at our end. We created a stack with an "AWS::Events::EventBus" resource with Resource Level Tags and no error was shown after multiple updates requested. However, when we tried to add Stack Level Tags, we encountered the same error you are facing. Hence, it is confirmed that the issue is with the "Stack level tags".
Unfortunately, I’m not able to provide ETA on when this issue might be fixed since AWS Support Engineers are not privy to development road-maps. I would like to apologize for the inconvenience caused.
Rest assured, I will keep the case in Pending Amazon Action and I will keep you updated on the resolution of this issue as soon as I have an update from the internal Team.
I got the same support response as you and while they haven't yet reported that it is fixed it worked fine for me now and all my production deployments are now completed with no issues. So it seems their internal team has already made the change to resolve the issue.
Relevant content
- asked a year ago
- asked 6 months ago
- asked 2 months ago
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated 3 months ago
You are not alone as this same thing happened with our CDK deployed event bus deployments. Yesterday when we went to release latest fixes to production it failed with this same "Unsupported Operation" error with no further detail and this is now happening on all updates when tested on multiple previously deployable versions and on multiple AWS accounts.
That is super annoying! Thanks for the confirmation. Have you reached out to support yet?
Same issue on a standard AWS stack, using SAM, any solution / workaround ? It's getting very problematic
Same issue using SAM: I have to first manually delete my stack every time I need to update it, which is absolutely not feasible on production environments.
Same issue with CDK, I'm currently unable to deploy anything as my Stack containing the EventBus has a tag with my commit sha, so anything I deploy is seen as a change and is failing.