Skip to content

Commit

Permalink
[DOCS] Fleet and Endpoint Security require a Transform, appropriate c…
Browse files Browse the repository at this point in the history
…onfiguration is needed (elastic#693) (elastic#700)

* Adding section for required node roles.

* Adding missing article.

* Added Janeen's feedback.
  • Loading branch information
nastasha-solomon authored May 24, 2021
1 parent 864599a commit c5dc3dd
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions docs/getting-started/sec-app-requirements.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,13 @@ https://www.elastic.co/cloud/elasticsearch-service[cloud deployment],
available on Azure, AWS, and GCP. You can {ess-trial}[try it out for free].
==============

[discrete]
[[node-role-requirements]]
== Node role requirements
To use Elastic Security, at least one node in your Elasticsearch cluster must have the {ref}/transform-settings.html[`transform` role]. Nodes are automatically given this role when they’re created, so changes are not required if default role settings remain the same. This applies to on-premise and cloud deployments.

Changes might be required if your nodes have customized roles. When updating node roles, nodes are only assigned the roles you specify, and default roles are removed. If you need to reassign the `transform` role to a node, {ref}/modules-node.html#transform-node[create a dedicated transform node].

[discrete]
== {kib} space and index privileges

Expand Down

0 comments on commit c5dc3dd

Please sign in to comment.