Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.x] [DOCS] Fleet and Endpoint Security require a Transform, appropriate configuration is needed (#693) #699

Merged
merged 1 commit into from
May 24, 2021
Merged

[7.x] [DOCS] Fleet and Endpoint Security require a Transform, appropriate configuration is needed (#693) #699

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/getting-started/sec-app-requirements.asciidoc
View file
Open in desktop
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