You can use the following cluster settings to enable or disable index management features.
action.auto_create_index
{ess-icon}-
(Dynamic) Automatically create an index if it doesn’t already exist and apply any configured index templates. Defaults to
true
.
action.destructive_requires_name
{ess-icon}-
(Dynamic) When set to
true
, you must specify the index name to delete an index. It is not possible to delete all indices with_all
or use wildcards. Defaults totrue
.
cluster.indices.close.enable
{ess-icon}-
(Dynamic) Enables closing of open indices in {es}. If
false
, you cannot close open indices. Defaults totrue
.NoteClosed indices still consume a significant amount of disk space.
reindex.remote.whitelist
{ess-icon}-
(Static) Specifies the hosts that can be reindexed from remotely. Expects a YAML array of
host:port
strings. Consists of a comma-delimited list ofhost:port
entries. Defaults to["*.io:*", "*.com:*"]
.
stack.templates.enabled
-
(Dynamic) If
true
, enables built-in index and component templates. {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create data streams. Iffalse
, {es} disables these index and component templates. Defaults totrue
.This setting affects the following built-in index templates:
This setting also affects the following built-in component templates: