Teams hand-wire missing build and issue alerts into Slack
Teams using AWS Amplify and Sentry want operational events in Slack, but the desired events or destinations are not readily available through the built-in alert setup described here. Amplify users report having to configure SNS, Lambda, or EventBridge—sometimes separately for each app—while a Sentry user could not select team assignment as an alert trigger. These workarounds add setup and maintenance instead of giving teams a straightforward way to route the events they need.
For developer teams using AWS Amplify or Sentry. Mentioned from Nov 2019 to Mar 2024 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 5.2/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I think having native chatbot support is nicer - no need for an extra lambda to manage, Chatbot can handle nicely formatting the build notification slack message, etc
The EventBridge thing requires doing it separately for each app that is deployed
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks