> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelblue.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Amazon SNS Notifications in USM Anywhere

After you [set up the Amazon SNS topic](setup-sns-topic) and [create the access key for Amazon Web Services (AWS)](create-aws-key), you can configure Amazon SNS notifications in USM Anywhere.

**To configure Amazon SNS Credentials for notifications**

1. Go to **Settings > Notifications**.
2. In the left navigation panel, click **Amazon SNS**.
3. Select the AWS **Region name**.
4. Enter the **Access key** and **Secret key**. See [Create an AWS Access Key](create-aws-key) for more information.

   <Frame>
     <img src="https://mintcdn.com/levelblue-5324744e/xOkkFcWcXtj_Ev_v/images/usm-anywhere/deployment-guide/notifications/sns-config.webp?fit=max&auto=format&n=xOkkFcWcXtj_Ev_v&q=85&s=a4a763523c1398c3c2a523b761763726" alt="" width="775" height="404" data-path="images/usm-anywhere/deployment-guide/notifications/sns-config.webp" />
   </Frame>
5. Click **Save Credentials**.

**To create an orchestration rule for sending a notification request to Amazon SNS**

1. Go to **Activity > Alarms** or **Activity > Events**.
2. Click the alarm or event to open the details.
3. Click **Create Rule** and select **Create Notification Rule**.

   <Frame>
     <img src="https://mintcdn.com/levelblue-5324744e/xOkkFcWcXtj_Ev_v/images/usm-anywhere/deployment-guide/notifications/alarmdetailscreaterule.webp?fit=max&auto=format&n=xOkkFcWcXtj_Ev_v&q=85&s=da7b47a01605543300784c444dfa2944" alt="" width="580" height="287" data-path="images/usm-anywhere/deployment-guide/notifications/alarmdetailscreaterule.webp" />
   </Frame>
4. There are suggested property values to create a matching condition. However, if you want to add new property values, click **Add Condition**.

   <Note>
     **Note:** If the field is related to the name of a country, you should use the country code defined by the [ISO 3166](https://www.iso.org/iso-3166-country-codes.html).
   </Note>

   <Note>
     **Note:** The **Sources or Destinations** field needs to match the universally unique identifier (UUID) of the event or alarm. You can also use the **Source Name** or **Destination Name** field.
   </Note>

   <Warning>
     **Important:** Instead of using the `equals` and `equals`, `case insensitive` operators for array fields, LevelBlue recommends the use of the `in` or `contains` operators.
   </Warning>

   <Note>
     **Note:** If you need to add a property value that maps with a property key, you need to know the mapping of the field. See [Determining the Mapping of a Field](../../user-guide/rules-management/mapping-field) for more information.
   </Note>
5. **(OPTIONAL)** Click **Add Group** to group your conditions.

   <Note>
     **Note:** See [Operators in the Orchestration Rules](../../user-guide/rules-management/orchestration-rules-operators) for more information.
   </Note>
6. In the **Occurrences** text box, enter the number of event occurrences that you want to produce a match on the conditional expression to trigger the rule.

   You can enter the number of occurrences or use the arrows to scroll the value up or down. You can enter a number between 1 and 100.

   <Warning>
     **Note:** The current rule box shows you the syntax of your rule, and the rule verification box reviews that syntax before saving the rule.
   </Warning>
7. Click **Next**.

   <Frame>
     <img src="https://mintcdn.com/levelblue-5324744e/LRsr4s1iGr_CM6ff/images/usm-anywhere/user-guide/rules-management/ruleverification.webp?fit=max&auto=format&n=LRsr4s1iGr_CM6ff&q=85&s=52719fcab619098656679ab0756735fa" alt="" width="358" height="234" data-path="images/usm-anywhere/user-guide/rules-management/ruleverification.webp" />
   </Frame>

   <Warning>
     **Important:** A dialog box opens if there are warning messages. Click **Cancel** to review the warning messages, or click **Accept** to continue creating the rule.
   </Warning>
8. Enter a **Rule Name**.
9. **(OPTIONAL)** Enter a **Description** to identify this rule.
10. For **Notification Method**, select the **Amazon SNS** option.
11. Enter the **SNS Topic Name** you have created in the AWS console. See [Set Up an Amazon SNS Topic](setup-sns-topic) for more information.

<Frame>
  <img src="https://mintcdn.com/levelblue-5324744e/xOkkFcWcXtj_Ev_v/images/usm-anywhere/deployment-guide/notifications/sns-rule-settings.webp?fit=max&auto=format&n=xOkkFcWcXtj_Ev_v&q=85&s=a94b4a2d7996604a61d9bbd9fa0f7083" alt="" width="787" height="286" data-path="images/usm-anywhere/deployment-guide/notifications/sns-rule-settings.webp" />
</Frame>

12. In the **Length** text box, specify the timespan that you want to use to identify a match for multiple occurrences. Enter the number in the text box, and then use the drop-down menu to select a value of seconds, minutes, or hours.

    This duration identifies the amount of time that transpires from the beginning to the end of the occurrence. If the number of occurrences is not met within this period, the rule is not a match.

    <Note>
      **Note:** Your defined length and occurrences function together to specify the number of occurrences within a time period that will produce a match for the rule. For example, you can define a rule to trigger an <Tooltip tip="Alarms provide notification of an event or sequence of events that require attention or investigation.">alarm</Tooltip> for an <Tooltip tip="An incident-type categorization that may be a precursor to other actions or stages of an attack.">unauthorized access</Tooltip> attempt when a failed <Tooltip tip="Log in (verb): Process in which an individual gains access to a computer system after providing sufficient credentials to authenticate their unique identity.Login (noun): User credentials, typically a username and matching password.">SSH login</Tooltip> occurs three times within a five-minute window.
    </Note>
13. Click **Save**.

    The created rule displays the list of rules. You can see it from **Settings > Rules > Orchestration Rules**. See [Orchestration Rules](../../user-guide/rules-management/orchestration-rules) for more information.

    <Warning>
      **Important:** It takes a few minutes for an orchestration rule to become active.
    </Warning>