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

New Pattern: aws-events-rule-kinesisstream #59

Closed
aijunpeng opened this issue Sep 10, 2020 · 1 comment
Closed

New Pattern: aws-events-rule-kinesisstream #59

aijunpeng opened this issue Sep 10, 2020 · 1 comment
Assignees
Labels
feature-request A feature should be added or improved

Comments

@aijunpeng
Copy link
Contributor

Build a new pattern to send data to kinesis stream when a cloudwatch event rule is triggered

Use Case

Need this pattern to send data to kinesis stream when a cloudwatch event rule is triggered

Proposed Solution

Build an aws-events-rule-kinesisstream pattern:
Create a CloudWatch Events Rule, kinesis data stream and relevant roles/permissions
Set kinesis data stream as the target of the cw event rule
Enable server-side kms encryption for kinesis data stream

Other

I am implementing this feature request and will submit a PR when it is done.

@aijunpeng aijunpeng added feature-request A feature should be added or improved needs-triage The issue or PR still needs to be triaged labels Sep 10, 2020
@hnishar hnishar removed the needs-triage The issue or PR still needs to be triaged label Sep 10, 2020
@hnishar hnishar added the in-progress This issue is being actively worked on label Sep 18, 2020
@hnishar hnishar removed the in-progress This issue is being actively worked on label Oct 27, 2020
@hnishar
Copy link
Contributor

hnishar commented Oct 27, 2020

This pattern has been published in the latest release v1.70.0

@hnishar hnishar closed this as completed Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved
Projects
None yet
Development

No branches or pull requests

2 participants