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.
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.
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.
