Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Amazon SNS, and make your voice heard!
API Requests & Payload Data
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
- Tech Details
|Deployment Types||Software as a Service (SaaS), Cloud, or Web-Based|
- Sending Text messages
- Ensuring test message compliance with 10 digit numbers.
- Notifying us when certain providers are down.
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.
- 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.
- 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.
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.
- Ease of use
- 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
- Errors are hard to debug
- Lack of verbose errors
- Very easy to setup
- Scale very well
- Covers a wide range of protocols and services
- 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
- Relatively simple to integrate in-app.
- Fuss-free for user once implemented.
- 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.
- Improved Logging
- Easy to use
- Helps to keep track of events
- If permissions are not configured properly it will give access denied
- Dashboards are difficult to implement
- Scheduling and sending messages is very easy
- Subscription and One-on-One option
- Booked Hotel Details are sent very fast
- First time setup can take a lot of time.
- Sometimes there is high latency in sending messages, leading to less impact against expected.
- Easy to use
- Easy to set up
- Easy to integrate
- We didn't really find a place where it wasn't useful.
- View and manage topics.
- Allow product inter-communication.
- Easy to get up and running.
- Bridge between different technologies/stacks used.
- Reporting available is good, but there are always room to grow.
- Analytics on message origin would be beneficial.
- Message size limit increase.
- Push Notifications
- Simple API
- Push Notifications due to multiple providers
- Notification delivery to different geographies via multiple providers.
- Cost effective as compared to other vendors.
- You can track delivery of notifications as well.
- Can provide a more advanced user intuitive system to be used for notification delivery.
- Language options could be extended.
- Within transaction messages further classification option should be given.
- Filtration of information.
- Streamlines messages and important information.
- Order information notification typically for clients sold products.
- At times you receive access denied errors which are annoying.
- Rarely do you receive internal failure errors where you can't access the information. It is rare but it does happen.
- You are required to add an MWS Authentication Token every so often. I wish it would pull that information automatically for you so you don't have to go searching for it.
- Built in for quicker setup within AWS ecosystem.
- Trusted as you control the users and configuration via IAM and easy access controls.
- Can be sent to S3 simple storage or for long term storage if required.
- Can be used in many regions, same configs.
- Add more console support for better graphical support.
- Can be hard to configure and may take many test example to even out alerts.
- Limitation on how many relays so may need external sms or other provider to save a bit more.
- Good Integration
- Hard to debug
- Email format
- Weak dashboard
- Proprietary API
- SNS is extremely reliable.
- SNS with SQS provides a safe place for messages in the event our services are ever down.
- SNS is easy to configure and subscribe to.
- For our use cases SNS completely fills our needs.
- Simple to use
- Easy to integrate
- AWS integration difficult for naive users
- Not Open Source
- Integrates with Lambda and SQS to allow for sophisticated serverless applications.
- It can be used to support any combination of email, push, or even SMS notifications.
- E-mail and SMS notifications aren't all that customizable, meaning this won't be a good solution for consumer-facing notifications.
- The opt-in process for e-mail and SMS notifications is cumbersome.
- To notify the stack holder when build and deployment is completed.
- To check and report environment health.
- Call consumers when all async producers finish their jobs.
- To send Push notifications.
- It is extremely easy and powerful service to send message across different Amazon services. To create the topic, subscriber and post notification is just natural. It requires almost zero learning curve.
- It is a managed services. So there is no need to worry about scaling. It can work with extreme heavy volume easily without taking any special care.
- It allows 256KB for published notification. Also this is divided into 4 chunks of 64 KB. Each 64KB chunk is considered as 1 request and full payload with 256KN is considered as 4 requests. This keeps your bill lower.
- It does not have sufficient debug options. The only way is to subscribe for email to receive errors.
- It is difficult to format email. To support dynamic formatting, developer needs to write extra code which can be simplified.
The only scenario where SNS is little less appropriate is heavy data volume. Sometimes you may get delayed notification.
- Multiple mediums for notifications like email, HTTP, Lambda etc
- Easy to set up the pub sub model
- Debugging is difficult
- Easy to integrate with other AWS solutions.
- Relatively easy setup.
- Better UI design.
- The AWS Lambda SNS trigger is great. Subscribing multiple Lambda functions to an SNS topic is a nice way to decouple features.
- SNS is fully-managed. Our team is too small to manage our own pub/sub infrastructure.
- Subscribing email endpoints to SNS topics and integrating topics with CloudWatch alerts is very easy; we create more non-emergency notifications than we would without SNS.
- The SNS Console has not been updated in a long time, and it was confusing to begin with.
- Testing systems that use SNS end-to-end can be tricky; LocalStack somewhat ameliorates this problem.
- Debugging is difficult.
- Super simple setup and deployment. You can have a new service set up within minutes and in a serverless environment as well
- Well documented and incredibly easy to use. There are available APIs in almost every relevant language and are all well documented by AWS. Getting any team up to date on their new Notification architecture shouldn't take longer than a day.
- Being managed by AWS themselves makes the service highly available in every possible way. Your SNS deployment is almost guaranteed to never go down without you ever lifting a finger to make it so.
- The AWS website UI could use some definite improvement. The website itself is very clunky and hard to navigate and always seems to have the wrong information in the wrong places. It is a monstrous task trying to make a website as complicated as AWS look simple and easy to navigate but even with some minor improvements it would become much more user and beginner friendly.
- Troubleshooting can be very difficult when encountering an issue with SNS and often many AWS services. By having all of your infrastructure in the cloud, it makes troubleshooting networking problems quite complicated. On top of this, aws provides little return information when a message fails to send, leaving a lot of guesswork to be done on your part to fix the issue.
- Allows you to send test push notification messages from console easily
- Straightforward integration into the codebase
- Easy integration/easy to maintain if already part of AWS ecosystem
- Testing on different environments was a challenge to setup. Unclear how it's really supposed to work.
- Mobile device tokens get disabled easily during testing making the push notification testing process fail silently.
- SMS Delivery setup procedures not as straightforward.