It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.

The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Change endpoint URLs Security considerations »
Elastic Docs ›Elastic Cloud Enterprise Reference [2.1]

Securing your installation

edit

Securing your installation

edit

Learn about security considerations and security-related tasks you should be aware of when deploying Elastic Cloud Enterprise:

  • Security Considerations - Covers information about current limitations, access control, encryption, and possible attack vectors.
  • Generate Roles Tokens - For automation purposes, generate a new ephemeral or persistent token with the right role permissions, so that you can install ECE on hosts and add the right roles at the same time.
  • Revoke Roles Tokens - Roles tokens enable additional hosts to join an ECE installation. If a token is no longer needed, it should be revoked to improve security.
  • Manage Security Certificates - Provide your own certificates for ECE to avoid a security warning when connecting to the Cloud UI or when using the API over HTTPS.
  • Restrict IP Traffic - Create rule sets of allowed IP addresses to block unwanted traffic from your Elastic Cloud Enterprise installation and deployments.
  • Retrieve User Passwords - Retrieve the credentials for the administration console users admin and readonly.
  • Reset User Passwords - Reset the passwords for the admin and readonly administration console users that you use to log into the Cloud UI.
« Change endpoint URLs Security considerations »