From 2b6d6fd4b81c8761a8bfb7859ec8133a76fb242d Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Fri, 26 Sep 2025 14:32:25 +0200 Subject: [PATCH 1/2] [GeoIP processor] Add clarification about using a reverse proxy endpoint --- docs/reference/enrich-processor/geoip-processor.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/enrich-processor/geoip-processor.md b/docs/reference/enrich-processor/geoip-processor.md index a474889cbee47..fbe5f82fc24d4 100644 --- a/docs/reference/enrich-processor/geoip-processor.md +++ b/docs/reference/enrich-processor/geoip-processor.md @@ -206,14 +206,14 @@ PUT my_ip_locations If you can’t [automatically update](#geoip-automatic-updates) your IP geolocation databases from the Elastic endpoint, you have a few other options: -* [Use a proxy endpoint](#use-proxy-geoip-endpoint) +* [Use a reverse proxy endpoint](#use-proxy-geoip-endpoint) * [Use a custom endpoint](#use-custom-geoip-endpoint) * [Manually update your IP geolocation databases](#manually-update-geoip-databases) $$$use-proxy-geoip-endpoint$$$ -**Use a proxy endpoint** +**Use a reverse proxy endpoint** -If you can’t connect directly to the Elastic GeoIP endpoint, consider setting up a secure proxy. You can then specify the proxy endpoint URL in the [`ingest.geoip.downloader.endpoint`](#ingest-geoip-downloader-endpoint) setting of each node’s `elasticsearch.yml` file. +If you can’t connect directly to the Elastic GeoIP endpoint, consider setting up a secure reverse proxy. You can then specify the reverse proxy endpoint URL in the [`ingest.geoip.downloader.endpoint`](#ingest-geoip-downloader-endpoint) setting of each node’s `elasticsearch.yml` file. In a strict setup the following domains may need to be added to the allowed domains list: From 7c2889691dbd8f0227b67052ce85ee0d545340fb Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Mon, 29 Sep 2025 11:30:26 +0200 Subject: [PATCH 2/2] Add note --- docs/reference/enrich-processor/geoip-processor.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/reference/enrich-processor/geoip-processor.md b/docs/reference/enrich-processor/geoip-processor.md index fbe5f82fc24d4..96b8cc9547612 100644 --- a/docs/reference/enrich-processor/geoip-processor.md +++ b/docs/reference/enrich-processor/geoip-processor.md @@ -215,6 +215,10 @@ $$$use-proxy-geoip-endpoint$$$ If you can’t connect directly to the Elastic GeoIP endpoint, consider setting up a secure reverse proxy. You can then specify the reverse proxy endpoint URL in the [`ingest.geoip.downloader.endpoint`](#ingest-geoip-downloader-endpoint) setting of each node’s `elasticsearch.yml` file. +:::{note} +True HTTP proxy support for GeoIP database downloads is not currently available in {{es}}. +::: + In a strict setup the following domains may need to be added to the allowed domains list: * `geoip.elastic.co`