Amazon Web Services offers the Amazon Simple Notification Service (SNS) which provides pub/sub messaging and push notifications to iOS and Android devices. It is meant to operate in a microservices architecture and which can support event-driven contingencies and support the decoupling of applications.
$0.01
per 1 million
AWS IoT Core
Score 9.9 out of 10
N/A
AWS IoT Core is a managed cloud service that lets connected devices interact with cloud applications and other devices. It includes the Device Gateway and the Message Broker, which connect and process messages between IoT devices and the cloud. AWS IoT Core connects AWS and Amazon services like AWS Lambda, Amazon Kinesis, Amazon S3, Amazon SageMaker, Amazon DynamoDB, Amazon CloudWatch, AWS CloudTrail, Amazon QuickSight, and Alexa Voice Service to build IoT applications that gather, process,…
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is …
I worked with Adobe campaign 2 years ago and comparatively, SNS is way better and easier to integrate with. There's a lack of latency with SNS and better customer support. Easier to group with subscriptions and easier to work from the command line with the use of the SDK. All …
SNS helps in integrating with other AWS components which are used in development such as Lambda, APIGW, S3 and DynamoDb easily. If used with third party software like PagerDuty, it makes the development and integration more complex. It is used mostly for publishing and …
Amazon Simple Notification Service and PagerDuty have been used by various organizations. Amazon SNS is ideal if you're within an AWS environment. PagerDuty is used when we are working outside of Amazon Web Services. Though PagerDuty is more expensive than Amazon SNS they do …
We have looked at other service providers, including the local service providers as well, but Amazon SNS stood ahead of all in terms of service availability across the globe and cost-effective plans per notification SMS. Moreover, we can also use Amazon SNS along with other AWS …
Common confusion between SNS and SQS. SNS directs information to its subscribers without any effort on the subscribers or individuals' end. SQS gathers the information and then the individual has to almost go find it. They do similar things but in a space where information can …
We have opted ultimately for AWS SNS once configuration was set topics and subscriptions setup. Site 24 and US Monitor are considerations to this product, but incur cost outside of Amazon, so not best for starting up for our needs.
The main reason we chose Amazon SNS is for easy integration with all the workflows in AWS. The other alternatives can be (and really are) best in specific points, but the main strength of SNS is that is one service of AWS, so we don't need to complicate things in our …
Our company prioritizes using AWS offerings unless there is a strong use case for using something within Azure. SQS is a similar service that solves different problems and we are using it in conjunction with SNS.
We use EC2 instances to train ML model against a heavy volume of data. When the model is trained (i.e. loss reduces to a certain level), we push notification to all the stakeholders to notify them the new model is available. To achieve it, SNS is the most simple and cost …
Many products, including PagerDuty, can be used to notify stakeholders when alarms are triggered. SNS is only suitable for non-emergency email alerts, and integration with CloudWatch is its only advantage. If you want to be notified of an issue by email, SNS can be configured …
SNS is much more customizable compared to SES and allows for many more delivery methods. While it is better for email-based notification services, not being able to send notifications via SMS limits your app functionality considerably. Being able to switch message delivery …
As I mentioned previously, I wish we had gone with a different service such as a Mixpanel or OneSignal as they are reputable in the space and are known for their strong support and documentation. AWS SNS was the way to go for us at the time we chose it due to the fact that we …
Azure IoT is a good product but since our whole suite of tech is now set up in AWS (ec2, s3, sagemaker, cloud formation, etc.), we wanted something that could quickly adapt to our environments. Learning a new tech for IoT was simply a bottleneck that we wanted to avoid at this …
AWS iot core is a good starting point which can be utilized for a variety of enterprise solutions. Barrier to entry to experiment and try AWS iot core is less and AWS eco-system providers ensure that even startups can try a variety of solutions and build key skills and …
Azure IoT service provides more or less the same services as compared to AWS IoT core, however the costing of AWS lead us to continued usage of IoT core over Azure IoT services. Also, considering our existing technology stack is on AWS, it was a natural selection for better …
It turns out that AWS IoT Core is the most mature solution on the market with the best variety of integration tools available. On the downside, it is not the cheapest platform existing out there. Amazon IoT Core is easy to start and set up, and our prior engagement with Amazon …
For our use case, we ended up with AWS because the human resources that were planning to be resourced on this particular project happened to have prior familiarity with the AWS ecosystem. The conversation became can we justify continuing with this ecosystem rather than pivoting …
We have checked other IoT platforms such as IBM Watson IoT and Microsoft Azure IoT, but Amazon IoT Core seems reasonable in terms of pricing and overall functionalities. Amazon IoT Core is easy to start and set up and our prior engagement with Amazon for AWS was a factor to go …
AWS IoT Core is faster, easier, cheaper, and enjoyed by our employees more than Microsoft Azure. We selected AWS IoT because we saw an advertisement for it and have used it ever since. We will continue to use it as long as it is around or until we find one that is better.
We prefer Amazon storage and content delivery S3 services rather than Microsoft Blob Storage. Also, AWS IoT Core seems to be the cheaper alternative compared to Azure IoT.
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.
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)
AWS iot core is very useful if you need to scale very quickly for managing lots of devices without handling the underlying infrastructure cost. It can enable real time publishing and subscription of devices, monitoring and early stage intervention in case of unexpected issues while developing a full stack solution. However, healthcare scenarios where government intervention is needed should be developed and scaled by following the set of compliance policies of the government and the SLA requirements of the customer. Finally, it is great where you need to do data science research after anonymizing data
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.
It is useful for applications developed using event driven architecture. It helps in tracking and logging the events in a very timely and efficient manner. The dashboards are a little difficult to implement. But overall it is very easy to integrate with other AWS services like Lambda, API GW, S3 and DynamoDB. The permissions to access should be resolved before using it.
I give AWS IoT Core's overall usability this rating because it is very easy to use and is enjoyed by all of our staff. The only problem is that it sometimes glitches and it freezes a lot. So overall, the usability of AWS IoT Core is very good, and we will continue to use it.
The AWS documentation is well maintained and has lots of information which makes it easier for developers to refer to and develop applications in a fast efficient manner. It is well documented with examples which is easy to understand and implement. You can also get help by posting into forums from like-minded developers.
It covers all the aspects of IoT services required for an IoT company. It supports all the industry-wide protocols for secure data transmission and integrates powerful AL and ML technology for data analytics. For data storage, Amazon S3 is a great solution. Strong tech support and user community. Since it is widely used as compared to other products, there is an abundance of training and learning material on the web.
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is considerable number of developers who can easily build solutions using AWS SNS. So, training costs are minimal. Other solutions are emerging and we are seeing a great usage especially of Firebase notifications because of its very neat integration with open source cross platform hybrid app frameworks like ionic, xamarin. SNS needs to become better and should have plugin support for the mobile application developers using low code/no code tools too.
Azure IoT is a good product but since our whole suite of tech is now set up in AWS (ec2, s3, sagemaker, cloud formation, etc.), we wanted something that could quickly adapt to our environments. Learning a new tech for IoT was simply a bottleneck that we wanted to avoid at this point.
Cost of alert calls to the different stakeholders across different geographies have gone down since using Amazon SNS.
Amazon SNS has saved a lot of time for the employees that they used to spend to call multiple stakeholders so they can now focus more on productive tasks.
Amazon SNS usage needs prior knowledge of programming.