New

The executive guide to generative AI

Read more
About usPartnersSupport|Login

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.

« Elastic Cloud Enterprise 2.0.1 Elastic Cloud Enterprise 1.1.5 »
Elastic Docs ›Elastic Cloud Enterprise Reference [2.0] ›Release notes

Elastic Cloud Enterprise 2.0.0

edit

Elastic Cloud Enterprise 2.0.0

edit

New for Elastic Cloud Enterprise version 2.0.0:

  • Changed username for all new installations of ECE. You should now use admin as the username for the user that is created during installation. For installations upgraded from 1.x, the root user is still available until the next major version; all new 2.x installations have only the admin and readonly users.
  • New deployment templates for the Elastic Stack. Deploy the Elastic Stack using our new deployment templates. These flexible, customizable templates are designed to fit your use case better, whether it’s search, logging or whatever challenge you can think up for Elastic Cloud Enterprise.
  • New customizable deployment templates for your hardware. Create your own deployment templates that are designed to work with your hardware. By first creating instance configurations that tell ECE what kind of hardware you have, you can provide the building blocks that you can then create deployment templated from. Create your own templates that are optimized for I/O, CPU, memory, and storage to match your use case.

  • New machine learning capabilities. Add machine learning to your deployments to gain insight and predict anomalies. Previously available for the Elastic Stack on-prem, now supported on Elastic Cloud Enterprise.

    Machine learning requires Elasticsearch version 6.3.1 or later, but you can upgrade your deployment to a supported version first and then add machine learning.

  • New hot-warm architecture with index lifecycle management. Quickly ingest and query current data, while keeping older data around on more cost-effective storage. If you need a complete logging solution, this is it.
  • Additional Kibana deployment capabilities. Deploy Kibana across multiple availability zones with your Elasticsearch cluster and scale Kibana to whatever size you need.
  • New dedicated master nodes. Improve the resilience of your deployments by adding dedicated master nodes. Larger-scale deployments get them automatically.
  • Additional snapshot interval configuration. Quickly change your snapshot interval using the Cloud UI.
  • Better networking and ports guidance. Need a better understanding of how our products communicate with each other and on which ports? Check out our improved ECE networking and ports page.
  • New night mode capability. Enjoy our new night mode in the Cloud UI. UI too bright when you want to focus on work? Try the night mode, available in the Cloud UI.
  • Improved security for Elasticsearch clusters and Kibana instances. To secure your Elasticsearch clusters and Kibana instances, use a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication.
  • Support for installing ECE on Ubuntu 16.04 using Docker 18.03. Docker 1.13 is still supported, but now users that wish to use a newer Docker version have an upgrade path.
  • Support for full encryption. Full encryption is supported for all internal network traffic, including traffic between nodes in a cluster, and between proxies, clusters, and all internal services.

As before, you can manage hosted Elasticsearch and Kibana from our Cloud UI. Our UI might look different with its new sliders, but your existing deployments will continue to work exactly as before.

To upgrade to Elastic Cloud Enterprise version 2.0.0, see Upgrade Your Installation. After you complete the upgrade, configure deployment templates for ECE to indicate what kind of hardware you have available for Elastic Stack deployments.

Known problems or limitations

edit

The following known problems or limitations exist for ECE 2.0:

  • You cannot convert Elastic Stack deployments between templates. For example: A deployment created with the default template cannot be converted to a hot-warm template. You can work around this limitation by creating a new deployment with the template you want and restoring your data using a snapshot from the original deployment.
  • This version of ECE is known to have a problem with snapshot storage integrations, breaking support for Minio (when using the Elastic Stack 6.4.2 or later), Google Cloud Storage (GCS), and Microsoft Azure Storage. Except for Microsoft Azure Storage, these storage integrations are available again in ECE 2.1 and we recommend that you upgrade to this later version. A possible workaround to reenable Microsoft Azure Storage is still being investigated. After upgrading to ECE 2.1, you might also need to upgrade your deployments to the Elastic Stack 6.5.0 or later to reenable snapshot storage support.

Breaking changes

edit

There are no breaking changes for ECE 2.0.

Release date: September 25, 2018

« Elastic Cloud Enterprise 2.0.1 Elastic Cloud Enterprise 1.1.5 »

On this page

Was this helpful?
Feedback