# SNS

* &#x20;SNS follow push mechanism to deliver the notification to the client, it eliminates the need of periodically check or poll new information and update.&#x20;
* SNS can push notifications to mobile devices, email, or any http endpoint.
* &#x20;To prevent the messages from being lost all messages published to SNS are stored redundantly across multiple AZ.&#x20;
* SNS allows you to group multiple recipients using topics. A topic is an “access point” for allowing recipients to dynamically subscribe for identical copies of the same notification.

#### &#x20;One topic can support deliveries to multiple endpoints

#### &#x20;Benefits

1. Instantaneous, push based delivery
2. . Simple api and easy integration with applications.&#x20;
3. &#x20;flexible message delivery over multiple transport protocol.&#x20;
4. &#x20;Inexpensive, pay-as-you-go model with no up-front costs. $ 0.50 per 1 million SNS request


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gyansetu-aws.gitbook.io/aws-cloud/sns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
