Inspiration
As more and more infrastructures are deployed in the cloud, there's a need to receive notification in case our cloud infrastructures experience some changes e.g. CPU utilization almost full, Virtual Machine changes status to Stopped, etc. While this notification feature is provided by Cloud Provider out of the box, we may need to subscribe the notification to various channels that we use individually. Also, message coming from cloud provider by default is not user-friendly and we need to convert it.
What it does
Using Courier, we can solve this issue. We can create notification template and integrate providers such as Email, SMS, and Slack in Courier, which then can be used by Cloud Provider serverless such as AWS Lambda or GCP Cloud Function to call and send notification to multi-channel. See git repository for more detail.
How we built it
See git repository for more detail.
Challenges we ran into
No challenge worthy to mention, all things imagined before creating the solution can be done.
Accomplishments that we're proud of
In short time (approx. 1-2 days), we can create a notification engine using courier and serverless function that can be used to send multi-channel notification messages.
What we learned
Courier, Slack, Twilio, AWS Event Bridge (incl. Transformer), Lambda deployment.
What's next for Lambda Courier Notification
See git repository for more detail.
Built With
- amazon-web-services
- courier
- python
Log in or sign up for Devpost to join the conversation.