Best Practices To Manage Apps On Amazon SNS

Amazon SNS is a service provided by AWS and also fully managed by AWS only. It is used for sending notifications to people, machines and devices. You may have configured billing alerts or Cloud watch alarm notifications on AWS accounts. Amazon SNS is responsible for delivery of notifications. This service consists of Topics and subscribers. One topic can have multiple subscribers and when a message publish for a topic then the message will receive by all the subscribers. Before this if we wanted to send certain messages to only a set of subscribers then we need to create separate topic for each set of subscribers.

Some Of The Key Features Of Amazon SNS :

1. It is a method with cost efficiency and easy to push notifications to mobile users, email recipients or even other distributed platforms.
2. Platforms supported for SNS service are with variety such as iOS, Android, Java, Python, PHP, NodeJS from AWS.
3. You can get the delivery status information via AWS CloudWatch on success and failure rates for mobile sent messages as well as their deliveries to SMS, SQS, HTTP, and Lambda destinations.
4. Use SNS as a message bus to send alarms, messages and notifications from AWS services such as CloudWatch, RDS and S3 to other AWS services such as SQS and Lambda.

Best Practices To Manage Apps On Amazon SNS :

• The tokens are responsible for identification of device and particular app on respective device.
• It is good to understand how to manage the applications you write for Amazon SNS. The tokens are managed by AWS on behalf of its clients. When a publisher publishes to a device, it must have the client’s credentials and the device token.
• The tokens are responsible for identification of device and particular app on respective device. Publisher must be able to access the identification, so that publishers can publish the info on device.
• When a user registers his device on Amazon SNS, the token number is recorded which is unique for the user.
• Generated token is combined with some other data and same is used to publish info on the user's device and this token along with the additional data is called as "PlatformEndpoint".

SNS Supports Transport Protocols :

• HTTP, HTTPS – Specify a Subscribers URL as part of the subscription registration; notifications will deliver through an HTTP POST to the specified URL.
• Email-JSON, Email – Messages as email are sent to registered addresses. Email-JSON send notification as a JSON object, as Email sends text-based email.
• SQS – We can specify an SQS queue as endpoint; SNS will enqueue a notification message to the specified queue.
• SMS – Messages are sent to registered phone numbers as SMS text messages.

SNS Supported Endpoint :

• Email Notifications : SNS provide the ability to send Email notifications.
• SMS Notifications : SNS provides the ability to send and receive Short Message Service (SMS) notifications to SMS-enabled mobile phones and smartphones.
• Mobile Push Notifications : SNS provides an ability to send push notification messages directly to the app on mobile devices. Push notification message sent to mobile endpoint can appear in mobile app as message alerts, badge updates, or even sound alert.

Supported Push Notification Services :

• Amazon Device Messaging (ADM)
• Apple Push Notification Service (APNS)
• Google Cloud Messaging (GCM)
• Windows Push Notification Service (WNS) for Windows 8+ and Windows Phone 8.1+
• Microsoft Push Notification Service (MPNS) for Windows Phone 7+
• Baidu Cloud Push for Android devices in China