AWS opensearch-service documentation change
Summary
Clarified network connectivity requirements for alert notifications
Security assessment
Emphasizes proper network configuration for secure alert delivery, improving documentation of security-related operational requirements.
Diff
diff --git a/opensearch-service/latest/developerguide/alerting.md b/opensearch-service/latest/developerguide/alerting.md index 70c6b09a8..7b69ae512 100644 --- a//opensearch-service/latest/developerguide/alerting.md +++ b//opensearch-service/latest/developerguide/alerting.md @@ -48 +48 @@ To create an alert, you configure a _monitor_ , which is a job that runs on a de - 4. For **Actions** , set up a notification channel for the alert. Choose between Slack, Amazon Chime, a custom webhook, or Amazon SNS. As you might imagine, notifications require connectivity to the channel. For example, your OpenSearch Service domain must be able to connect to the internet to notify a Slack channel or send a custom webhook to a third-party server. The custom webhook must have a public IP address in order for an OpenSearch Service domain to send alerts to it. + 4. For **Actions** , set up a notification channel for the alert. Choose between Slack, Amazon Chime, a custom webhook, or Amazon SNS. As you might imagine, notifications require connectivity to the channel. For example, to notify a Slack channel or send a custom webhook to a third-party server, your OpenSearch Service domain needs appropriate network connectivity. The custom webhook must have a public IP address in order for an OpenSearch Service domain to send alerts to it.