setup.asciidoc 1.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. [role="xpack"]
  2. [[transform-setup]]
  3. === Set up {transforms}
  4. ++++
  5. <titleabbrev>Setup</titleabbrev>
  6. ++++
  7. To use the {transforms}, you must have the
  8. {subscriptions}[appropriate license] and at least one
  9. <<transform-setup-nodes,{transform} node>> in your {es} cluster. If {stack}
  10. {security-features} are enabled, you must also ensure your users have the
  11. <<transform-privileges,necessary privileges>>.
  12. [discrete]
  13. [[transform-setup-nodes]]
  14. ==== {transform-cap} nodes
  15. To use {transforms}, there must be at least one node in your cluster with
  16. `xpack.transform.enabled` and `node.transform` set to `true`. By default, all
  17. nodes are {transform} nodes unless you explicitly change these settings or set
  18. `node.data` to `false`.
  19. If you want to control which nodes run {transforms}, set `node.transform` to
  20. `false` on some nodes.
  21. For more information, see <<transform-settings>> and <<modules-node>>.
  22. [discrete]
  23. [[transform-privileges]]
  24. ==== Security privileges
  25. The {es} {security-features} provide <<built-in-roles,built-in roles>>
  26. and <<security-privileges,privileges>> that make it easier to control
  27. which users can manage or view {transforms}.
  28. For example, you need `manage_transform` cluster privileges to preview and
  29. create {transforms}. Members of the built-in `transform_admin` role have these
  30. privileges. You also need `read` and `view_index_metadata` index privileges on
  31. the source index and `read`, `create_index`, and `index` privileges on the
  32. destination index.