Elastic Cloud Enterprise 2.6.0edit

New for Elastic Cloud Enterprise 2.6.0:

  • Better traffic management. Elastic Cloud Enterprise now supports two major traffic management features:

    • IP filtering. You can now limit access to your deployments hosted on Elastic Cloud Enterprise to a specific list of whitelisted IPs. IP filtering is useful if you have a list of known IPs that your users are connecting from. You can use this feature to limit access from your internal company network or VPC, where all connections are going out from a common gateway, for example. Check IP traffic filters.
  • Elastic Enterprise Search. App Search and Workplace Search are now available in Elastic Cloud Enterprise as a combined Enterprise Search deployment. From mobile applications to geo-localized search, App Search provides a set of tools that cater to both technical and non-technical search managers on your team to customize the application search experience and results. Workplace Search makes your teams' content findable, fast. Content platforms such as Google Drive, Salesforce, and many others, can be combined to create a unified and personalized search experience. Check Enable Enterprise Search.
  • New supported Linux distributions. With this version of ECE, we now officially support and recommend the following Linux distributions: Ubuntu 18.04 LTS (Bionic Beaver) and Red Hat Enterprise Linux (RHEL) 8 and CentOS 8.
  • New recommended Docker version. We now officially support and recommend Docker 19.03 as an installation prerequisite for ECE. To learn more about the installation of Docker for supported Linux distributions, check Configure your operating system.

What’s changededit

We renamed one model in our OpenAPI specification that affects the deprecated Clusters API. 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. If this is the case, you need to change the name of this model in your code:

  • Previous name: co.elastic.cloud.apiclient.model.ElasticsearchClusterSettings
  • New name: co.elastic.cloud.apiclient.model.DeprecatedElasticsearchClusterSettings.

The Deployment API is not affected by this change. Since the Clusters API is scheduled for removal in ECE 3.0, we encourage you to migrate your code to use the new Deployments API that replaces the deprecated Clusters API.

Breaking Changesedit

The in-place configuration change improvements included in this release mean that single availability zone deployments will be temporarily unavailable while the change is applied. If availability is a concern, you should use two availability zones for your deployment, which requires no downtime and which ensures deployment availability during future configuration changes, upgrades, and hardware failures.

As a best practice for production setups, you should never run with a single availability zone if downtime is a concern.


Version 3.0.0 will include the following breaking change:

  • The field ccs in co.elastic.cloud.apiclient.model.ElasticsearchClusterSettings has been deprecated and will no longer be supported in version 3.0.0. This field was used to configure remote clusters and retrieve the remote clusters of an elasticsearch cluster. As a replacement, there are now two specific endpoints that should be used to update and retrieve the remote clusters:

    • GET /api/v1/deployments/{deployment_id}/elasticsearch/{ref_id}/remote-clusters
    • PUT /api/v1/deployments/{deployment_id}/elasticsearch/{ref_id}/remote-clusters

    This change is needed in order to support configuration of remote clusters through Kibana and the Elasticsearch API directly.

Known problemsedit

This version of ECE has a known problem with the resizing of system-owned clusters: if you apply a configuration change that only adds more zones to the cluster, the change will cause some downtime. As a workaround to avoid the downtime, you can select the grow-and-shrink approach in the UI when you apply the configuration change.

Release date: August 18, 2020