This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
Index management settings
editIndex management settings
editYou can use the following cluster settings to enable or disable index management features.
-
action.auto_create_index
-
(Dynamic)
Automatically create an index if it doesn’t already exist and apply any configured index templates. Defaults to
true
.
-
action.destructive_requires_name
-
(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
-
(Dynamic) Enables closing of open indices in Elasticsearch. If
false
, you cannot close open indices. Defaults totrue
.Closed indices still consume a significant amount of disk space.
-
reindex.remote.whitelist
-
(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. Elastic Agent uses these templates to create data streams. Iffalse
, Elasticsearch disables these index and component templates. Defaults totrue
.This setting affects the following built-in index templates:
-
logs-*-*
-
metrics-*-*
-
synthetics-*-*
-
profiling-*
-
security_solution-*-*
This setting also affects the following built-in component templates:
-
logs@mappings
-
logs@settings
-
metrics@mappings
-
metrics@settings
-
metrics@tsdb-settings
-
synthetics@mapping
-
synthetics@settings
-