aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::Events::Rule] - [Enhancement] - Add support for CfnRule
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::Events::Rule
### Resource name
_No response_
### Description
I have a use case where we integrate MSK cluster with EventBridge Pipes with an Event Bus as a target and enrichment step.
I need to set detail-type dynamically based on the JSONPath. We've tried to achieve that by adding an EventRule in the target (event bus) that listens to the kafka event. Then we've tried to set detail-type with the JSONPath.
Currently EventRule doesn't support set of input, inputPath and inputTransformers for when the target is an event bus (regardless it's in the same or different account).
The [docs ](https://constructs.dev/packages/@aws-cdk/aws-events/v/1.177.0/api/CfnRule?lang=typescript)only mention that it's not possible to use those properties for when event bus is in a different account.
But the feature is not supported for both use cases.
This limitation for setting detail-type dynamically either in EventBridge Pipes or CfnRule (with target = event bus), caused us needing to do a lot of customisation. We had to use a lambda as a target (as opposed to event bus) plus adding a EventBridge client with SDK, besides additional unit tests.
Would there be a way for adding this feature in future releases? I've opened a [request](https://github.com/aws/aws-cdk/issues/30587) with the aws-cdk team but they've pointed me to your team
I appreciate your support and help.
Thanks
### Other Details
_No response_
Contributor guide
Research direction
Begin with the AWS::Events::Rule CfnRule documentation linked in the issue and compare target behavior for same- and cross-account event buses. Done means the supported input, inputPath, and inputTransformer behavior can set detail-type dynamically for the described EventBridge Pipes and MSK use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kafka
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100