elasticsearch/docs/reference/security/operator-privileges/operator-only-functionality.asciidoc
James Rodewig 255c9a7f95
[DOCS] Move x-pack docs to docs/reference dir (#99209)
**Problem:**
For historical reasons, source files for the Elasticsearch Guide's security, watcher, and Logstash API docs are housed in the `x-pack/docs` directory. This can confuse new contributors who expect Elasticsearch Guide docs to be located in `docs/reference`. 

**Solution:**
- Move the security, watcher, and Logstash API doc source files to the `docs/reference` directory
- Update doc snippet tests to use security

Rel: https://github.com/elastic/platform-docs-team/issues/208
2023-09-12 14:53:41 -04:00

51 lines
2 KiB
Text

[role="xpack"]
[[operator-only-functionality]]
=== Operator-only functionality
NOTE: {cloud-only}
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 {es} version.
[[operator-only-apis]]
==== Operator-only APIs
* <<voting-config-exclusions>>
* <<delete-license>>
* <<update-license>>
* <<autoscaling-put-autoscaling-policy>>
* <<autoscaling-delete-autoscaling-policy>>
* <<repo-analysis-api>>
* <<update-desired-nodes>>
* <<get-desired-nodes>>
* <<delete-desired-nodes>>
* <<get-desired-balance>>
* <<delete-desired-balance>>
[[operator-only-dynamic-cluster-settings]]
==== Operator-only dynamic cluster settings
* All <<ip-filtering,IP filtering>> settings
* The following dynamic <<ml-settings,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-disk-threshold,`cluster.routing.allocation.disk.threshold_enabled` setting>>
* The following <<recovery-settings-for-managed-services,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`