> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/aws/sns.md).

# AWS Simple Notification System (SNS)

Discover more about the AWS SNS connector and how to use it on the Digibee Integration Platform.

**AWS SNS** allows pipelines to instantly publish messages to the AWS cloud using the [Simple Notification Service API](https://docs.aws.amazon.com/sns/latest/api/API_Publish.html). Learn more about [SNS in the Amazon documentation](https://docs.aws.amazon.com/sns/).

## **Parameters**

Take a look at the configuration parameters of the connector. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.

### **General tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Account</strong></td><td>The account used to connect the pipeline to the SNS Publish API.</td><td>N/A</td><td>BASIC, AWS-V4</td></tr><tr><td><strong>Region</strong></td><td>The AWS Region where the SNS client needs to work.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Topic Name or Arn</strong> <code>(DB)</code></td><td>The name or ARN of the topic to which the message is to be sent.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Subject</strong> <code>(DB)</code></td><td>The subject of the message being published.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Message Body</strong> <code>(DB)</code></td><td>The content of the message.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Advanced tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Message Deduplication Id Strategy</strong></td><td>The strategy for deduplicating messages when the topic is FIFO. Options are: <strong>Use Content Based Deduplication</strong> and <strong>Use Exchange Id</strong>.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Message Group Id Strategy</strong></td><td>The strategy for grouping messages when the topic is FIFO. Options are: <strong>Use Constant</strong>, <strong>Use Exchange Id</strong>, and <strong>Use Property Value</strong>.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Message Group Id</strong> <code>(DB)</code></td><td>Identifier of the group of messages. Within a group, all messages with the same <strong>Message Group Id</strong> are processed and sent in sequence.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Message Structure</strong> <code>(DB)</code></td><td>The message structure to be used.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Kms Master Key Id</strong> <code>(DB)</code></td><td>The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Policy</strong> <code>(DB)</code></td><td>The policy for this topic. Loaded by default from classpath, but you can prefix with <code>classpath:</code>, <code>file:</code>, or <code>http:</code> to load the resource from different systems.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Queue Url</strong> <code>(DB)</code></td><td>The URL of the queue to subscribe to.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Auto Create Topic</strong></td><td>Specifies whether to automatically create the topic.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Server Side Encryption Enabled</strong></td><td>Specifies whether Server Side Encryption is enabled for the topic.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Subscribe SNS to SQS</strong></td><td>Specifies whether the subscription between SNS Topic and SQS is enabled.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/aws/sns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.