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 1.1.0
editElastic Cloud Enterprise 1.1.0
editNew for Elastic Cloud Enterprise version 1.1.0:
- An all-new visual Cloud UI design based on the Elastic UI Framework (EUI). The EUI framework is a design library with improved usability and accessibility that ensures consistency for future UI updates across all Elastic products. Visually, the Cloud UI now provides high contrast, color-blind safe palettes, and the correct aria labels to improve accessibility. To experience the new UI design, upgrade your installation to ECE 1.1 and log into the Cloud UI.
- Support for restoring snapshots from the Cloud UI. Snapshot repositories to back up your Elasticsearch clusters were supported previously, but you could restore snapshots only manually through the Restore API. With the new Cloud UI support, the process to restore snapshots is simplified. To learn more, see Work with Snapshots.
-
Updated Elastic Stack packs. Elastic Cloud Enterprise now ships with:
- Elasticsearch and Kibana 6.0.0
- Elasticsearch and Kibana 5.6.4
- Elasticsearch 2.4.6 and Kibana 4.6.5
-
Support for private Docker registries in air-gapped environments. If you cannot install Elastic Cloud Enterprise on each host by obtaining the installation images directly from Elastic over the internet, you can now push the ECE container images to your private Docker registry first. After pushing the images, point the installation script to your private Docker registry with the
--docker-registryparameter and install ECE on all of your hosts without further internet access. To learn more, see Install ECE Without Internet Access. -
Support for custom Docker socket locations. If your Docker installation is customized and uses a different location for the Docker socket, you can now specify the location of the Docker socket with the
--host-docker-hostparameter during installation. To learn more, see Script Reference. - A rolling strategy for configuration changes to Elasticsearch clusters that requires less free capacity. The strategy works by creating only one new node at a time when applying a layout change or a cluster resize operation. For large clusters, this new strategy significantly reduces the additional capacity required when compared to creating all new nodes at once. To use the new strategy, select Rolling create new under Configuration Strategy when you change your deployment configuration in the Cloud UI.
-
Bug fixes and operational improvements:
- The Cloud UI now indicates the correct storage capacity when you use the API to change the default RAM-to-storage ratio.
- ECE now checks if there is enough capacity before running the create and allocate steps during Elasticsearch cluster creation.
- A reworked playbook for production that supports small, medium and large deployment examples. Planning to set up a production system? Start with this playbook. Includes the steps necessary for each example, sample commands, and new illustrations. To learn more, see Playbook for Production.
Changed or removed in Elastic Cloud Enterprise 1.1.0:
-
The
--repository REPOSITORY_NAMEparameter that permitted you to specify a Docker repository during the Elastic Cloud Enterprise installation has been removed and replaced with the--docker-registryparameter.
To start using Elastic Cloud Enterprise 1.1, upgrade your installation.
For more information about what is new in ECE 1.1, see Elastic Cloud Enterprise 1.1.0 released.
Known issues in Elastic Cloud Enterprise 1.1.0:
- If you upgrade from older Elastic Cloud Enterprise versions to 1.1.0 and subsequently restart allocators or add more capacity, this can lead to authentication errors in Kibana. We recommend that you upgrade to 1.1.1 immediately to fix this issue.