Prompt
I'm unhappy with AWS SNS for sending user notifications
Latest observation
Oct 13, 2026
OpenAI APIWeb search: off
Fair—SNS is often fine for internal/pub-sub plumbing, but it can be awkward if your goal is user-facing notifications.
Common pain points with SNS for that use case:
- Too low-level: you often end up building a lot around it yourself.
- Delivery complexity: push, email, SMS each have different quirks.
- Harder to manage templates, preferences, and retries cleanly.
- Fanout isn’t the same as product notifications: user notification systems usually need orchestration, personalization, deduping, and per-user preferences.
- Debugging can be annoying when you need to trace one notification across channels.
Better fits depend on what you mean by “notifications”:
If you want a user notification system
Consider a dedicated notification platform or building a small notification service around:
- queue + worker architecture
- notification templates
- per-user preferences
- retry/backoff
- audit logs
- channel-specific providers
If you want AWS-native alternatives
- Amazon Pinpoint: better for customer communications, segmentation, campaigns, and channels like email/SMS/push.
- EventBridge + Lambda/SQS: better if you want to own the logic and keep it modular.
- SES for email specifically.
- Amazon Connect / Pinpoint if you need customer outreach at scale.
If you want a simpler managed product
Possible options depending on channel:
- Twilio for SMS/WhatsApp/voice
- SendGrid / Postmark for email
- OneSignal / Firebase Cloud Messaging for push
- Or a unified notification service like Courier, Knock, Novu, etc.
If you want, I can help you pick the best replacement based on:
- channels you need,
- AWS-only vs third-party, and
- whether this is transactional alerts or marketing-style messaging.