Currently we use SNS to deliver notifications across our infrastructure, including receiving email, email delivery responses, alarm notifications, etc.
Pros
Ability to define multiple subscriptions / topics
Dynamically subscribe and publish to topics
Widely integrated with AWS and third party components
Cons
Visibility into delivery, sampling, etc, for troubleshooting
Likelihood to Recommend
<div>Using SNS for any notification use case where available is the default and defacto solution. It directly integrates with SES to configure both incoming email and email delivery responses.</div><div>
</div><div>Additionally, any notifications, such as CloudWatch alarms, are a good use case for SNS topics and allow us to fan out delivery as needed (pagerduty, email, etc)
We use SNS to send out emails and text notifications. The majority of our uses are to send out One Time Passwords through our online application process. SNS is an inexpensive and safe way to send out a high volume of these codes. SNS was also very straightforward to implement.
Pros
Sending Text messages
Ensuring test message compliance with 10 digit numbers.
Cons
Notifying us when certain providers are down.
Likelihood to Recommend
It is well suited for transactional messages like OTPs. It's probably not well suited for a two-way messaging thread.
The Amazon SNS service provides support to a wide variety of needs including critical events notification, monitoring hybrid mobile applications both on ios and android, time-sensitive information updates. We are in the process of scaling our projects to include Amazon SNS in business workflow systems to relay events among apps, move data between data stores or update records in billing systems.
The product is very useful in managing key event notifications. We also plan to use it for our customers to update them about our new features and critical outages. The scope of our use case is both for managing AWS backend events within the organizational workflows and also for notifications to our customers.
Pros
Event updates and notifications concerning validation, approval are immediately delivered to relevant system components as well as end-users.
Move data between data stores or update records in billing systems
SNS is very useful in workflow systems to relay events among distributed applications
Event notification, monitoring applications, workflow systems, time-sensitive information updates in billing and ledgering systems.
Very useful to developers who build applications that rely on real-time events.
Cons
Interoperability with other cloud vendors and shared hosting systems
Better support and integration with low code/no code platforms to enable developers to integrate faster
Ease of developer experience especially in managing real time database events for hybrid mobile and tablet apps
Availability of plugins for open source cross platform developer tools like ionic framework.
Likelihood to Recommend
The Amazon SNS service is well suited to support event notifications, monitoring applications, workflow systems, time-sensitive information updates, and mobile applications that generates or consumes notifications. It can be used to relay time-critical events to mobile applications and devices. It provides significant advantages to developers who build mobile applications that rely on real-time events.
It is not well suited for hybrid cross platform mobile application frameworks at this juncture. An optimal version to meet the needs of a cross platform mobile developer is needed as generally the frameworks are not meant to manage real-time events. It is also not suited for cases where the queue management needs improvement or requires special workflows/tooling.
Amazon Simple Notification Service (SNS) is a very versatile tool useful for both small and large-scale Amazon estates.
Our first use case was for applications monitoring and system alerts based on notifications triggered by predefined
thresholds. Amazon Simple Notification Service (SNS) sent these notifications to specific users via email. It was
great for our initial foray into DevOps way back in 2010. Amazon Simple Notification Service (SNS) is now a lot better and can be used for a variety of use cases – one that we now use very widely is fanout where we use Amazon Simple Notification Service (SNS) to replicate Production data into staging and training environments for AI/ML model training.
Pros
Messaging
Ease of use
Pricing
Cons
Troubleshooting
Likelihood to Recommend
Amazon Simple Notification Service (SNS) is incredible for setting up monitoring and alerting for your AWS estate when you are starting out. However, it has now grown significantly and is a feature complete messaging platform that can operate securely at scale. We use Amazon Simple Notification Service (SNS) now significantly for clickstream analytics and training AI/ML models via fanout - a method to replicate Production data and send it directly into staging environments where new ML models can get trained.
I used to use AWS SNS for sending text messages for transactional messages. Now I use SNS for sending alerts from our dashboards. SNS is very versatile and there are a lot of features you can use as well as benefits of setting up the subscriptions from the back end. We use Terragrunt to easily upload all our data
Pros
Easy GUI to use
Integration with automation
Integration with third party platforms
Daily reports
Ability to have subscriptions and topics
Ability to connect to third party applications
Cons
Errors are hard to debug
Lack of verbose errors
Likelihood to Recommend
I think that SNS is very well suited if you need to send emails or text messages in response to events. Whether you use lambda or Grafana or other alerting platforms where you can have an event trigger a message to go out to your team. I also have used SNS as a marketing platform tool where we simply use it to send text messages based on event-driven actions and also for batch messages
VU
Verified User
Analyst in Information Technology (10,001+ employees)
We use it for many purposes : Mainly to do monitoring and alerting. For instance we use it to send alerts via Microsoft teams using Webhooks. For others scenarios we use it to send messages to some specific APIs we have.
Pros
Very easy to setup
Scale very well
Covers a wide range of protocols and services
Cons
It would be useful to have more information regarding the origin of a message (ie its source)
It would be nice to configure HTTP-related stuff (such as header) when interacting with a HTTP target
Likelihood to Recommend
Very useful when you need to setup http webhooks for some alerting or build more complex architectures using services like Lambda. The product will scale pretty well !
VU
Verified User
Engineer in Information Technology (10,001+ employees)
We use it as part of our mobile learning app to send transactional messages to learners to start a module. It allows us to reach learners without an email address and reduces user friction of needing to remember a login and password, or 'not getting round' to the email notification to begin their learning.
Pros
Relatively simple to integrate in-app.
Fuss-free for user once implemented.
Pay-per-use
Cons
No clear indication that transactional messages are sent as multiple SMSs (increased cost).
No 'dashboard' to easily see metrics at a glance or deep-dive if more info required.
Likelihood to Recommend
Great for transactional messaging. Easy-enough to integrate. Seamless to run. Would love for SNS to also support OTT messaging platforms to reduce cost to us, and provide greater flexibility for our learners.
We have used Amazon Simple Notification Service (SNS) for creating applications which make use of events. With help of SNS it is easy to track events with their timestamp when they originated and how they were used. It is very essential and it makes it easy to use as SNS can help in logging the inbound and outbound events.
Pros
Improved Logging
Easy to use
Helps to keep track of events
Cons
Pricing
If permissions are not configured properly it will give access denied
Dashboards are difficult to implement
Likelihood to Recommend
Amazon Simple Notification Service (SNS) is well suited for applications built on event driven architecture. It makes it easy to log and track events in real time from the source to the destination. The permissions should be configured properly in order to use SNS else while implementing you can come across Access Denied errors. The dashboards are difficult to maintain to track the utilization.
VU
Verified User
Engineer in Information Technology (5001-10,000 employees)
We use Amazon SNS to push notifications to customers for previously searched hotels through email and messages.
Pros
Scheduling and sending messages is very easy
Subscription and One-on-One option
Booked Hotel Details are sent very fast
Cons
First time setup can take a lot of time.
Sometimes there is high latency in sending messages, leading to less impact against expected.
Likelihood to Recommend
We have been able to implement Amazon SNS very easily for our push notifications and solve our purpose pretty well. Scheduling various bursts is also very easy and works like a charm. We are not facing any issue with the product.
Amazon SNS is being used to deliver notifications to users. We started with custom software where users could subscribe to certain topics and get information in a timely manner. It solved the problem of trying to keep track of everything that is going on around using different forms of communication. This way, we centralized it.
Pros
Easy to use
Easy to set up
Easy to integrate
Cons
We didn't really find a place where it wasn't useful.
Likelihood to Recommend
Amazon Simple Notification Service (SNS) is well suited where you want to allow the user to subscribe to a topic and unsubscribe at their own will and they can choose how information is delivered to them.
VU
Verified User
Administrator in Information Technology (501-1000 employees)