Amazon SNS Overview

Amazon SNS is the #3 ranked solution in our list of top Message Oriented Middleware tools. It is most often compared to Amazon EventBridge: Amazon SNS vs Amazon EventBridge

What is Amazon SNS?

Amazon Simple Notification Service (SNS) is a highly available, durable, secure, fully managed pub/sub messaging service that enables you to decouple microservices, distributed systems, and serverless applications. Amazon SNS provides topics for high-throughput, push-based, many-to-many messaging. Using Amazon SNS topics, your publisher systems can fan out messages to a large number of subscriber endpoints for parallel processing, including Amazon SQS queues, AWS Lambda functions, and HTTP/S webhooks. Additionally, SNS can be used to fan out notifications to end users using mobile push, SMS, and email.

You can get started with Amazon SNS in minutes by using the AWS Management Console, AWS Command Line Interface (CLI), or AWS Software Development Kit (SDK).

Buyer's Guide

Download the Message Oriented Middleware Buyer's Guide including reviews and more. Updated: May 2021

Amazon SNS Customers

PlayOn! Sports, NASA, Change Healthcare, FCBarcelona

Amazon SNS Video

Pricing Advice

What users are saying about Amazon SNS pricing:
  • "The pricing of push notifications and everything is quite fair. If you are using FCM under the hood, it is completely free. When you are using push notification on SMS, it is just a nominal price that you need to pay. SMS services are a lot more costly. It is because we don't have proper providers in India. That's why it gets a lot more costly in terms of SMS. This is the reason why we don't use SMS services from SNS itself. We use other third-party services like SMS Horizon. We use a third-party service for email services. It is almost free. It is just around $1 a month. Configuring Lambda is also quite cheap. You only pay for the Lambda usage. You don't pay for SNS itself."
  • "It is the cheapest solution in the market. It is on a monthly basis. After a month, you are build based on your usage. There are no additional costs to the standard licensing fees."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Elvis Rozario
Senior Backend Engineer at FreightBro
Real User
Top 5
Automatically scalable, very stable, and full of solid and useful features

What is our primary use case?

SNS can be used for a lot of things. There are six different subscriber types available at the moment and among them, we use the SMS, email, and push notifications. We use the SMS and Email services to notify admins whenever something goes wrong, but our primary use case is to send push notifications to our mobile devices (customers). The backend engineers work on setting it up on AWS and most of the features like SMS, Email, etc do not need any frontend intervention, but yes for push notifications, the frontend needs to use the SDK to capture and display them.

Pros and Cons

  • "The mobile push notifications are the most valuable. Previously, we used to use Firebase Cloud Messaging (FCM) for this functionality. It is a Google service for sending push notifications. Android did not have a good service for sending push notifications, but now, Amazon SNS integrates with FCM. Under the road, it is actually using FCM, but we can see all the metrics on our AW service itself, which makes it a lot easier instead of using a third-party service for this particular functionality."
  • "A major issue with AWS as a whole is that it has a lot of services that do the same thing, and people get confused about which one to use in which scenario. Previously, we used to use SNS for connecting microservices. SNS has around six types of subscribers. We can subscribe to Lambda, HTTP, HTTPS, SMS, email, and push notifications. We used to use HTTP endpoints and Lambda for connecting to microservice systems. Now we have something called EventBridge, which actually does that for you. For connecting to services, we should just use EventBridge rather than SQS, SNS. I hear a lot of complaints from people wherein they do not understand when to use EventBridge and when to use SQS, SNS. They can remove these features so that it doesn't confuse users about when to use SQS, SNS, or EventBridge."

What other advice do I have?

People should know when to use this solution. With so many AWS products out there, people are not sure which product to use in which scenario. SNS should be used only when you want a server-to-client connection, not when you need a server-to-server connection. For a server-to-server connection, you can use EventBridge. If you want a server-to-client connection and a one-to-many or many-to-many connection, you should use SNS. If you want a one-to-one connection, you should use SQS. You can go through the entire documentation and see if your particular use case requires you to use SNS or not…
AA
Senior Software Engineer at etura
Real User
Top 10
Provides reliable service, enables easy engagement of our users, and supports all devices

What is our primary use case?

I have been using Amazon SNS within my Learning Management System or LMS. I use SNS with .NET services to send push notifications to mobiles to tell parents about the progress of their kids. We send push notifications to mobile devices and emails. Amazon SNS is a pretty reliable service, and it is fully managed. We don't have to manage anything. Amazon totally manages everything for us. We just have to integrate the SNS service with our microservice or backend service and trigger an action to throw notifications or messages. We just trigger a notification to go to all subscribers. I am using… more »

Pros and Cons

  • "Push notifications are the most valuable. I have mostly used push notifications for my system. Amazon SNS supports all devices for push notification services. It supports iOS, Android, and Windows notifications. It provides reliable push notification services. We have queues, and we can track which notifications have failed or had some issues. We can then figure out the issue. We can also debug the issue because of which our push notification didn't reach the end users."
  • "I recently worked with Firebase, and it provides an option to create a marketing campaign with a title and a specific image to inform our audience about something. We just design the campaign and then use the push notifications. It would be good if Amazon also adds a similar feature."

What other advice do I have?

It is a good service. I would recommend it to my colleagues if they want to implement push notifications with SNS. Overall, I am very happy with this service. I would rate Amazon SNS a ten out of ten.
Find out what your peers are saying about Amazon, Solace, TIBCO and others in Message Oriented Middleware. Updated: May 2021.
512,711 professionals have used our research since 2012.
JA
Co-Founder at NetScapeLabs
Real User
Top 20
Enables us to build solutions for our clients

What is our primary use case?

My primary use case for Amazon SNS is for push messaging. We have a chatting application in my project library and so we have the mobile to mobile service for push notifications.

Pros and Cons

  • "Stability has been good for us. It is quite high."
  • "In terms of improvement, I would like to have better customer support for SNS. We can then manage it very easily."

What other advice do I have?

I would rate Amazon SNS an 8.5 out of ten. Not a ten because of the stability and customer support. I develop applications by using SNS and I start by using documents. There should be easier documentation with better points.
Product Categories
Message Oriented Middleware
Buyer's Guide
Download our free Message Oriented Middleware Report and find out what your peers are saying about Amazon, Solace, TIBCO, and more!