- Elastic Cloud Enterprise - Elastic Cloud on your Infrastructure: other versions:
- Introducing Elastic Cloud Enterprise
- Preparing your installation
- Installing Elastic Cloud Enterprise
- Identify the deployment scenario
- Install ECE on a public cloud
- Install ECE on your own premises
- Alternative: Install ECE with Ansible
- Log into the Cloud UI
- Install ECE on additional hosts
- Migrate ECE to Podman hosts
- Post-installation steps
- Configuring your installation
- System deployments configuration
- Configure deployment templates
- Tag your allocators
- Edit instance configurations
- Create instance configurations
- Create deployment templates
- Configure system deployment templates
- Configure index management for templates
- Updating custom templates to support
node_roles
and autoscaling - Updating custom templates to support Integrations Server
- Default instance configurations
- Include additional Kibana plugins
- Manage snapshot repositories
- Manage licenses
- Change the ECE API URL
- Change endpoint URLs
- Enable custom endpoint aliases
- Configure allocator affinity
- Change allocator disconnect timeout
- Migrate ECE on Podman hosts to SELinux in
enforcing
mode
- Securing your installation
- Monitoring your installation
- Administering your installation
- Working with deployments
- Create a deployment
- Access Kibana
- Adding data to Elasticsearch
- Migrating data
- Ingesting data from your application
- Ingest data with Node.js on Elastic Cloud Enterprise
- Ingest data with Python on Elastic Cloud Enterprise
- Ingest data from Beats to Elastic Cloud Enterprise with Logstash as a proxy
- Ingest data from a relational database into Elastic Cloud Enterprise
- Ingest logs from a Python application using Filebeat
- Ingest logs from a Node.js web application using Filebeat
- Manage data from the command line
- Administering deployments
- Change your deployment configuration
- Maintenance mode
- Terminate a deployment
- Restart a deployment
- Restore a deployment
- Delete a deployment
- Migrate to index lifecycle management
- Disable an Elasticsearch data tier
- Access the Elasticsearch API console
- Work with snapshots
- Restore a snapshot across clusters
- Upgrade versions
- Editing your user settings
- Deployment autoscaling
- Configure Beats and Logstash with Cloud ID
- Keep your clusters healthy
- Keep track of deployment activity
- Secure your clusters
- Deployment heap dumps
- Deployment thread dumps
- Traffic Filtering
- Connect to your cluster
- Manage your Kibana instance
- Manage your APM & Fleet Server (7.13+)
- Manage your APM Server (versions before 7.13)
- Manage your Integrations Server
- Switch from APM to Integrations Server payload
- Enable logging and monitoring
- Enable cross-cluster search and cross-cluster replication
- Access other deployments of the same Elastic Cloud Enterprise environment
- Access deployments of another Elastic Cloud Enterprise environment
- Access deployments of an Elasticsearch Service organization
- Access clusters of a self-managed environment
- Enabling CCS/R between Elastic Cloud Enterprise and ECK
- Edit or remove a trusted environment
- Migrate the cross-cluster search deployment template
- Enable App Search
- Enable Enterprise Search
- Enable Graph (versions before 5.0)
- Troubleshooting
- RESTful API
- Authentication
- API calls
- How to access the API
- API examples
- Setting up your environment
- A first API call: What deployments are there?
- Create a first Deployment: Elasticsearch and Kibana
- Applying a new plan: Resize and add high availability
- Updating a deployment: Checking on progress
- Applying a new deployment configuration: Upgrade
- Enable more stack features: Add Enterprise Search to a deployment
- Dipping a toe into platform automation: Generate a roles token
- Customize your deployment
- Remove unwanted deployment templates and instance configurations
- Secure your settings
- API reference
- Changes to index allocation and API
- Script reference
- Release notes
- Elastic Cloud Enterprise 3.7.3
- Elastic Cloud Enterprise 3.7.2
- Elastic Cloud Enterprise 3.7.1
- Elastic Cloud Enterprise 3.7.0
- Elastic Cloud Enterprise 3.6.2
- Elastic Cloud Enterprise 3.6.1
- Elastic Cloud Enterprise 3.6.0
- Elastic Cloud Enterprise 3.5.1
- Elastic Cloud Enterprise 3.5.0
- Elastic Cloud Enterprise 3.4.1
- Elastic Cloud Enterprise 3.4.0
- Elastic Cloud Enterprise 3.3.0
- Elastic Cloud Enterprise 3.2.1
- Elastic Cloud Enterprise 3.2.0
- Elastic Cloud Enterprise 3.1.1
- Elastic Cloud Enterprise 3.1.0
- Elastic Cloud Enterprise 3.0.0
- Elastic Cloud Enterprise 2.13.4
- Elastic Cloud Enterprise 2.13.3
- Elastic Cloud Enterprise 2.13.2
- Elastic Cloud Enterprise 2.13.1
- Elastic Cloud Enterprise 2.13.0
- Elastic Cloud Enterprise 2.12.4
- Elastic Cloud Enterprise 2.12.3
- Elastic Cloud Enterprise 2.12.2
- Elastic Cloud Enterprise 2.12.1
- Elastic Cloud Enterprise 2.12.0
- Elastic Cloud Enterprise 2.11.2
- Elastic Cloud Enterprise 2.11.1
- Elastic Cloud Enterprise 2.11.0
- Elastic Cloud Enterprise 2.10.1
- Elastic Cloud Enterprise 2.10.0
- Elastic Cloud Enterprise 2.9.2
- Elastic Cloud Enterprise 2.9.1
- Elastic Cloud Enterprise 2.9.0
- Elastic Cloud Enterprise 2.8.1
- Elastic Cloud Enterprise 2.8.0
- Elastic Cloud Enterprise 2.7.2
- Elastic Cloud Enterprise 2.7.1
- Elastic Cloud Enterprise 2.7.0
- Elastic Cloud Enterprise 2.6.2
- Elastic Cloud Enterprise 2.6.1
- Elastic Cloud Enterprise 2.6.0
- Elastic Cloud Enterprise 2.5.1
- Elastic Cloud Enterprise 2.5.0
- Elastic Cloud Enterprise 2.4.3
- Elastic Cloud Enterprise 2.4.2
- Elastic Cloud Enterprise 2.4.1
- Elastic Cloud Enterprise 2.4.0
- Elastic Cloud Enterprise 2.3.2
- Elastic Cloud Enterprise 2.3.1
- Elastic Cloud Enterprise 2.3.0
- Elastic Cloud Enterprise 2.2.3
- Elastic Cloud Enterprise 2.2.2
- Elastic Cloud Enterprise 2.2.1
- Elastic Cloud Enterprise 2.2.0
- Elastic Cloud Enterprise 2.1.1
- Elastic Cloud Enterprise 2.1.0
- Elastic Cloud Enterprise 2.0.1
- Elastic Cloud Enterprise 2.0.0
- Elastic Cloud Enterprise 1.1.5
- Elastic Cloud Enterprise 1.1.4
- Elastic Cloud Enterprise 1.1.3
- Elastic Cloud Enterprise 1.1.2
- Elastic Cloud Enterprise 1.1.1
- Elastic Cloud Enterprise 1.1.0
- Elastic Cloud Enterprise 1.0.2
- Elastic Cloud Enterprise 1.0.1
- Elastic Cloud Enterprise 1.0.0
- What’s new with the Elastic Stack
- About this product
Elastic Cloud Enterprise 2.7.0
editElastic Cloud Enterprise 2.7.0
editNew 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, check 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, check Upgrade versions.
-
Automatic upgrade of some system clusters. Starting with this release, ECE now automatically upgrades the
admin-console-elasticsearch
andsecurity
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. Check Configure SSO for deployments.
-
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.
Known problems
edit-
In ECE version 2.7.0 we added a new container scheduled task service to run miscellaneous administrative tasks on runners with the
allocator
role. Unfortunately, this new service was causing an excessive number of connections to be created to the ZooKeeper coordination services. This issue is fixed in ECE version 2.7.2 and later. We highly recommend you to upgrade to a release with the fix.
What’s changed
edit-
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 thenode.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.
-
The new
To upgrade your Elastic Cloud Enterprise installation to this latest version, check Upgrade your installation.
Release date: November 10, 2020
On this page