Elastic Cloud Enterprise 2.7.0edit

New for Elastic Cloud Enterprise 2.7.0:

  • New logging features. You can now supplement your deployment monitoring by shipping logs to a monitoring deployment. The new functionality makes extra logging features available, including audit logging, and lets you search and analyze your deployment logs in Kibana. To get started, see Enable logging and monitoring.
  • Elastic Stack 7.10.0. This version of Elastic Cloud Enterprise is bundled with our latest Elastic Stack version. To learn more about best practices when upgrading deployments from previous versions of the Elastic Stack, see Upgrade versions.
  • Automatic upgrade of some system clusters. Starting with this release, ECE now automatically upgrades the admin-console-elasticsearch and security clusters to the latest bundled 7.x version of Elasticsearch. Upgrading these system clusters provides access to new features and keeps these clusters up to date with the rest of the stack.
  • SSO support for Enterprise Search. For Elastic Stack versions 7.9.2 and later, single sign-on (SSO) is now supported between your Elastic Cloud Enterprise account and Enterprise Search instances. Once you are authenticated to your Elastic Cloud Enterprise account, you no longer need to log in separately to access Enterprise Search. Learn more …​
  • Switch to session cookies for authentication. The Cloud UI now uses session cookies set by the API for authentication between client and server to improve security. In previous releases, the Cloud UI used JSON Web Tokens (JWTs) stored in localStorage for authentication.
  • Improved installation instructions. The ECE documentation is now simplified and repurposed into clearer paths for each installation option:

    With a linear and modular documentation design, it’ll be much easier to get up and running with ECE.

  • New Cloud UI header. We switched to a new black header bar for global header items in the Cloud UI.

What’s changededit

  • We changed the type used for optimistic concurrency version fields in OpenAPI specification from an integer to a string. This is necessary for the admin-console-elasticsearch cluster to be upgraded to Elasticsearch 7, which uses a 2 part primary term + sequence number versioning scheme. This does not change the API itself, but it requires changes in your code if you are using a client generated from our OpenAPI specification.
  • This release runs Elasticsearch 7.9.2 or later with the XX:ActiveProcessorCount JVM flag instead of the node.processors setting that was used with previous versions. If you had already added an Elastic Stack pack for version 7.9.2 or later before upgrading to ECE 2.7, the following changes apply:

    • The new ActiveProcessorCount JVM flag takes effect for Elasticsearch clusters on version 7.9.2 or later after the first instance reboot following the upgrade to ECE 2.7.
    • You might notice a change in performance characteristics, but our tests have indicated the difference to be a net positive one for most scenarios. The main driver for this change is to ensure more predictable performance, as the previous mechanism was shown to cause the JVM to make poor sizing choices for some of its internal thread pools.

To upgrade your Elastic Cloud Enterprise installation to this latest version, see Upgrade your installation.

Release date: November 10, 2020