Skip to content

Commit c23c3c6

Browse files
committed
Document the existence of the IPinfo token secure setting
1 parent dcfbb13 commit c23c3c6

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/reference/ingest/apis/put-ip-location-database.asciidoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,12 @@ PUT _ingest/ip_location/database/my-database-1
2424
----
2525
// TEST[skip:we don't want to leak the enterprise-geoip-downloader task, which touching these APIs would cause. Therefore, skip this test.]
2626

27+
IMPORTANT: The IPinfo configuration shown below requires a token. Because the token is sensitive information,
28+
it is stored as a <<secure-settings,secure setting>> in {es} named `ingest.ip_location.downloader.ipinfo.token`. Only
29+
one IPinfo token is currently allowed per {es} cluster. A valid token must be in the secure settings in order
30+
to download from IPinfo. The token setting does not take effect until all nodes are restarted or a
31+
<<cluster-nodes-reload-secure-settings, `reload_secure_settings`>> request is executed.
32+
2733
[source,console]
2834
----
2935
PUT _ingest/ip_location/database/my-database-2

0 commit comments

Comments
 (0)