Amazon SNS Reviews

We use this solution for the communication lines between departments in our organization.

There are 300 people using SNS in my organization. They are mostly developers.

It's a simple communication service that allows us to communicate with customers.

There could be more integration with other solutions. Right now, I can communicate in five different ways within a minute. I would like there to be more options for integration, like with Slack or Microsoft Teams for example.

I have been using this solution for three years.

It's stable.

It's scalable.

I would rate their technical support three out of five.

The initial setup was very easy. I would rate the setup four out of five.

The implementation was done in-house.

Their pricing is competitive. I would rate the cost four out of five.

I would rate this solution nine out of ten.

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 the latest version of this solution in my current product, which has .NET code. This solution is deployed on the cloud. We are using Elastic Beanstalk for .NET deployment and Amazon SNS for our server. We then send notifications to subscribed users or specific devices that are interested in or have subscribed to our topic.

It enables easy engagement of our users with our product. We often track users' interest to find out how they have been performing with our app or the system. Based on the performance, we recommend or send push notifications. Based on these notifications, users open our app and spend some time on our system. If we use it properly, it increases our growth exponentially.

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.

I have been developing products for five to six years. I have been working with Amazon SNS for four years.

It is the most stable product in the market.

It is scalable. If you are a startup, they provide a free quota, and after that, they start charging. It is scalable for our needs. We pay based on our usage. The more users we add on, the more we pay.

We have been using this notification system for four years. Currently, we don't have any plans to expand our usage.

I have not used their technical support.

I have been using Google Firebase for two years. In one application, I was using Firebase Realtime Database, so we preferred to use their real-time notification as well. Firebase does the same thing and sends notifications to subscribed devices.

With Firebase, we use real-time messages for push notifications, whereas with Amazon, we use Amazon SNS. I found Amazon SNS to be more stable than Firebase. Firebase provides only push notifications, whereas Amazon SNS provides emails, mobile messages, and push notifications. It is a hub of many things. Therefore, it is good to use one solution for multiple things.

You can easily create services. It is a very simple process.

It was a quick deployment. We bought a service that we can consume within our service. We can have a microservice and put our credentials on a server, and then we can send notifications to our subscribers by using that specific key. I also manage or maintain it on my own.

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.

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.

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.

We build solutions for our clients, they ask us to implement all the documents and features for them.

I am a mobile front-end developer so Amazon SNS has most of the features for the backend. I only need to transfer for the front-end push services.

In terms of improvement, I would like to have better customer support for SNS. We can then manage it very easily.

Stability has been good for us. It is quite high.

We have two to three guys on the server who handle it and we have six to 10 guys who are the backend developers. The backend developers and server guys, primarily use SNS and Amazon Security. 

Four people are responsible for maintenance, two senior backend guys and two server guys.

SNS is not extensively. It's usually used when we get a client's request. We don't have plans to increase usage.

We have also used Google Cloud. We switched to SNS because our developers were more used to it. They can easily adapt it. 

We have also used Amazon Lex for the chatbots. We have to give the entitlements entities and some other things that I take and recognize. We can make Amazon Alexa apps for Amazon Lex which is quite different from SNS.

The initial setup is not very complex. We have two full-time employees we require for the deployment and we get help from Amazon server guys who help us for initial setups.

The deployment can take one to two hours. 

We see ROI because we use the features that help us and make our product work better. Investing in these features is a good return.

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.

The solution provides us with notifications on the jobs of the different services that we run on AWS. 

Amazon SNS has SMS notifications as well. Most of the other solutions have only email notifications. 

The tool needs to have direct integration with AvPro. 

I have been working with the solution for five to six years. 

I would rate Amazon SNS' stability a nine out of ten. 

I would rate Amazon SNS' scalability a nine out of ten. My company has 10 users for the product. 

The tool has good technical support. 

Positive

I would rate Amazon SNS' setup an eight out of ten and we have deployed it on the cloud. We can complete the deployment in a couple of minutes. 

Amazon SNS is cheap and I would rate it a three out of ten. The pricing is usage-based. 

I would rate the product an eight out of ten.