[I Made This]: Serverless multi-channel alerting solution based on user preferences #4804
Closed
1 task done
Labels
community-content
Community content to feature in the documentation
content
Content related tasks, e.g., blog posts, video, reusable artefact etc
revisit
Maintainer to provide update or revisit prioritization in the next cycle
Link to your material
https://github.com/aws-samples/multichannel-app-to-person-alerting
Description
Implemented idempotency into my multi-channel alerting solution, using the message ID sent with the API request as the idempotency token/key.
Preferred contact
Orsolya B
(Optional) Social Network
No response
(Optional) Additional notes
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: