Site Reliability Engineer at a tech services company with 51-200 employees
Real User
Jan 3, 2023
We use this SNS for sending out notifications to the endpoints. The endpoints could be the email address or distribution lists or another channel. In my company, I use the SNS notifications for a Slack channel, as well as an email distribution list. It is an ETL tool. It's used for data extraction, loading and getting an output. It's also used for data analytics and data engineering. We have configured the SNS in such a way that the developers can work on the Matillion tool run multiple jobs in their language. Whenever there's any success in the job which they run, a notification will be triggered for which SNS is used on the cloud.
We use this solution because the integration between the features is excellent. The production level services can communicate with each other easily. For example, we can implement a Dynamo DV and a couple of different triggers to communicate with Lambda. We implemented SNS modules into Lambda and Lambda communicated with SNS.
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.
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.
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.
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.
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...
It is a notification service for the device. If we need to notify anybody from your mobile or data form.
The solution provides us with notifications on the jobs of the different services that we run on AWS.
We use this solution for its notification service alert functionality.
We use this SNS for sending out notifications to the endpoints. The endpoints could be the email address or distribution lists or another channel. In my company, I use the SNS notifications for a Slack channel, as well as an email distribution list. It is an ETL tool. It's used for data extraction, loading and getting an output. It's also used for data analytics and data engineering. We have configured the SNS in such a way that the developers can work on the Matillion tool run multiple jobs in their language. Whenever there's any success in the job which they run, a notification will be triggered for which SNS is used on the cloud.
We use this solution because the integration between the features is excellent. The production level services can communicate with each other easily. For example, we can implement a Dynamo DV and a couple of different triggers to communicate with Lambda. We implemented SNS modules into Lambda and Lambda communicated with SNS.
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.
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.
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.
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.