-
Notifications
You must be signed in to change notification settings - Fork 784
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
[🔌 Provider]: AWS SQS #2963
Comments
hey @lohrm-stabl, thanks for opening this issue :) would love to learn about how you want to get alerts from SQS:
in general, it will help me to get something like:
|
Hey @shahargl sure,
so we actually have two use cases: Notify about alerts via SQS: As a keep user, I want to connect our AWS SQS queue where we submit alerts in a given format to raise them in keep. The second one: Get processed alerts via SQS. Similar to how you notify telegram channels or send out emails for events, I would like to get an event submitted to our SQS queue, so we can further process it. Without to deep keep knowledge, I think a possible workaround would be to create a public API, set that up as a webhook, and configure an AWS Lambda behind that API to parse the request and submit it to an AWS queue. As a keep user, I want to connect an AWS SQS queue to receive and react to alerts raised in keep. |
Amazing! Let me draft something you can test 👌 |
@shahargl I'd love to work on this :) |
@35C4n0r assigned! |
Describe the provider you want to add
As a developer, I want to receive and send alerts from and to SQS.
Describe your use case
This will enable us to use and integrate keep into our cloud architecture.
With that we can call a lambda from that queue and execute custom code for integration in our platform.
It will also be a lot cheaper for us to use keep, because instead of keep querying our database all the time, we can simply check critical values during preprocessing and notify keep.
Are you already using Keep?
No
Additional context
Add any other context or screenshots about the provider request here.
The text was updated successfully, but these errors were encountered: