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

Feature request: Add Amazon EventBridge as supported destination #51

Open
otterley opened this issue Jul 14, 2023 · 4 comments
Open

Feature request: Add Amazon EventBridge as supported destination #51

otterley opened this issue Jul 14, 2023 · 4 comments

Comments

@otterley
Copy link

AWS customers would benefit from adding Amazon EventBridge as a supported destination for notifications.

Amazon EventBridge is a scalable, highly-performant, and low-cost serverless event bus. It's the default event bus provider for many AWS services, including EC2, Auto Scaling, ECS, and many more. Events can be matched using a JSON-based pattern matching, and can be delivered to many supported destinations, including Amazon SNS, AWS Lambda, Amazon API Gateway, Amazon SQS, and many more.

A typical use case would be to match a Kubernetes resource event, forward the event to EventBridge, match the event and invoke an SNS topic, then deliver the notification to the topic's email subscriber(s). Alternatively, EventBridge could deliver the event to CloudWatch Logs, then a pattern matcher could notify someone after N matched events delivered within a bounded timeframe.

@arikalon1
Copy link
Collaborator

Thanks @otterley

It does sound like a valid use case.
Are you open to contributing this enhancement?

@otterley
Copy link
Author

I have a colleague who's working on it right now - keep an eye out for a future PR.

@nikhilm-yai
Copy link

Was there a PR raised for this? I am looking for this as well.

@arikalon1
Copy link
Collaborator

hey @nikhilm-yai

We don't have a PR for this just yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants