Type to search.

Operator-only functionality

ECH

Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

ECK

Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

ECE

Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Indirect use only

This feature is designed for indirect use by Elastic Cloud Hosted, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported.

Operator privileges provide protection for APIs and dynamic cluster settings. Any API or cluster setting that is protected by operator privileges is known as operator-only functionality. When the operator privileges feature is enabled, operator-only APIs can be executed only by operator users. Likewise, operator-only settings can be updated only by operator users. The list of operator-only APIs and dynamic cluster settings are pre-determined in the codebase. The list may evolve in future releases but it is otherwise fixed in a given Elasticsearch version.

  • All IP filtering settings

  • The following dynamic machine learning settings:

    • xpack.ml.node_concurrent_job_allocations
    • xpack.ml.max_machine_memory_percent
    • xpack.ml.use_auto_machine_memory_percent
    • xpack.ml.max_lazy_ml_nodes
    • xpack.ml.process_connect_timeout
    • xpack.ml.nightly_maintenance_requests_per_second
    • xpack.ml.max_ml_node_size
    • xpack.ml.enable_config_migration
    • xpack.ml.persist_results_max_retries

  • The cluster.routing.allocation.disk.threshold_enabled setting

  • The following recovery settings for managed services:

    • node.bandwidth.recovery.operator.factor
    • node.bandwidth.recovery.operator.factor.read
    • node.bandwidth.recovery.operator.factor.write
    • node.bandwidth.recovery.operator.factor.max_overcommit