remote-clusters-security.asciidoc 2.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. [[remote-clusters-security]]
  2. === Configure remote clusters with security
  3. To use {ccr} or {ccs} safely with remote clusters, enable security on all
  4. connected clusters and configure Transport Layer Security (TLS) on every node.
  5. Configuring TLS security on the transport interface is minimally required for
  6. remote clusters. For additional security, configure TLS on the
  7. <<security-basic-setup-https,HTTP interface>> as well.
  8. All connected clusters must trust one another and be mutually authenticated
  9. with TLS on the transport interface. This means that the local cluster
  10. trusts the certificate authority (CA) of the remote cluster, and the remote
  11. cluster trusts the CA of the local cluster. When establishing a connection, all
  12. nodes will verify certificates from nodes on the other side. This mutual trust
  13. is required to securely connect a remote cluster, because all connected nodes
  14. effectively form a single security domain.
  15. User authentication is performed on the local cluster and the user and user’s
  16. roles names are passed to the remote clusters. A remote cluster checks the user’s
  17. role names against its local role definitions to determine which indices the user is
  18. allowed to access.
  19. Before using {ccr} or {ccs} with secured {es} clusters, complete the following
  20. configuration tasks:
  21. . Enable the {es} {security-features} on every node in each connected cluster by
  22. setting `xpack.security.enabled` to `true` in `elasticsearch.yml`. Refer to the
  23. <<general-security-settings,{es} security settings>>.
  24. . Configure Transport Layer Security (TLS) on every node to encrypt internode
  25. traffic and authenticate nodes in the local cluster with nodes in all remote
  26. clusters. Refer to
  27. <<security-basic-setup,set up basic security for the {stack}>> for the required
  28. steps to configure security.
  29. +
  30. NOTE: This procedure uses the same CA to generate certificates for all nodes.
  31. Alternatively, you can add the certificates from the local cluster as a
  32. trusted CA in each remote cluster. You must also add the certificates from
  33. remote clusters as a trusted CA on the local cluster. Using the same CA to
  34. generate certificates for all nodes simplifies this task.
  35. After enabling and configuring security, you can
  36. <<remote-clusters-connect,connect remote clusters>> from a local cluster.
  37. With your clusters connected, you'll need to
  38. <<remote-clusters-privileges,configure users and privileges>> on both the local
  39. and remote clusters.
  40. If you're configuring a remote cluster for {ccr}, you need to
  41. <<ccr-getting-started-follower-index,configure a follower index>> on your local
  42. cluster to replicate the leader index on a remote cluster.