Error when edit notification.core.http.host_deny_list configuration

OpenSearch
1

Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
Amazon Opensearch Service 2.11
Service software version OpenSearch_2_11_R20240502

Describe the issue:

Hello everyone, i’m trying to setup a new notification channel with a custom webhook. When i send a test message i receive this error from my Opensearch

[status_exception] {"event_status_list": [{"config_id":"******","config_type":"webhook","config_name":"Grafana - Test","email_recipient_status":[],"delivery_status":{"status_code":"400","status_text":"Webhook message creation failed with status:Host of url is denied, based on plugin setting [notification.core.http.host_deny_list]"}}]}

So when i my getting notification.core.http.host_deny_list from the API and i see IPs like theres are banned

[
      "127.0.0.0/8",
      "169.254.0.0/16",
      "10.0.0.0/8",
      "172.16.0.0/12",
      "192.168.0.0/16",
      "0.0.0.0/8",
      "100.64.0.0/10",
      "192.0.0.0/24",
      "192.0.2.0/24",
      "198.18.0.0/15",
      "192.88.99.0/24",
      "198.51.100.0/24",
      "203.0.113.0/24",
      "224.0.0.0/4",
      "240.0.0.0/4",
      "255.255.255.255/32"
]

My grafana is in private network with ip inside range 10.0.0.0/8 . I would like to delete this value from the array by using the API. In the Opensearch blog i found this issue How do I edit the notification.core.http.host_deny_list in aws but when i am sending an API request i received this message.

{
  "Message": "Your request: '/_cluster/settings' payload is not allowed."
}

So does anyone get this problem ?

Configuration:

Relevant Logs or Screenshots:

2

@sacha-wmx I understand that you’re using AWS OpenSearch managed service. Have you tried contacting AWS support?

1 Like
3

Yeah finally i contacted AWS support and they confirmed what i was thinking. It’s not possible to send notification to private endpoint you must use a public endpoint.

1 Like