[[index-management-settings]] === Index management settings You can use the following cluster settings to enable or disable index management features. [[auto-create-index]] // tag::auto-create-index-tag[] `action.auto_create_index` {ess-icon}:: (<>) <> if it doesn't already exist and apply any configured index templates. Defaults to `true`. // end::auto-create-index-tag[] [[action-destructive-requires-name]] // tag::action-destructive-requires-name-tag[] `action.destructive_requires_name` {ess-icon}:: (<>) When set to `true`, you must specify the index name to <>. It is not possible to delete all indices with `_all` or use wildcards. // end::action-destructive-requires-name-tag[] [[cluster-indices-close-enable]] // tag::cluster-indices-close-enable-tag[] `cluster.indices.close.enable` {ess-icon}:: (<>) Enables <> in {es}. If `false`, you cannot close open indices. Defaults to `true`. + NOTE: Closed indices still consume a significant amount of disk space. [[reindex-remote-whitelist]] // tag::reindex-remote-whitelist[] `reindex.remote.whitelist` {ess-icon}:: (<>) Specifies the hosts that can be <>. Expects a YAML array of `host:port` strings. Consists of a comma-delimited list of `host:port` entries. Defaults to `["\*.io:*", "\*.com:*"]`. // end::reindex-remote-whitelist[] [[stack-templates-enabled]] `stack.templates.enabled`:: + -- (<>) If `true`, enables built-in index and component templates. {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create data streams. If `false`, {es} disables these index and component templates. Defaults to `true`. This setting affects the following built-in index templates: include::{es-repo-dir}/indices/index-templates.asciidoc[tag=built-in-index-template-patterns] This setting also affects the following built-in component templates: include::{es-repo-dir}/indices/put-component-template.asciidoc[tag=built-in-component-templates] --