- 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.4.0
editElastic Cloud Enterprise 2.4.0
editNew for Elastic Cloud Enterprise 2.4.0:
- Elastic App Search (beta). You can now add Elastic App Search to your deployments for a more streamlined search experience: From mobile applications to geo-localized search, Elastic App Search offers customization tools, such as query-time synonyms and relevance tuning interfaces, that cater to both technical and non-technical search managers on your team. Check Enable App Search.
- Elastic Cloud Control tooling (ecctl, beta). A new command-line interface, ecctl is built on top of our existing ECE API and used by our own engineers. With ecctl, you can perform many of the operations that traditionally require using the Cloud UI or authenticating with the ECE API directly from the command line. This new tool provides added value if you want to script or automate portions of your ECE operations. The code is open for contributions on GitHub, so that you can build your own solution on top or add your own commands. New releases of ecctl happen separately from the ECE release cadence. Check Elastic Cloud Control Documentation.
- Better control through API keys. ECE now supports API keys that you can hand out to teams so that they can view or modify deployments. These API keys include tight integration with ECE role-based access controls (RBAC), so that an ECE administrator can create unique API keys for each user. Additionally, these user-specific API keys can be revoked as needed, for example in the case of a security compromise. Check Authenticate using an API key.
-
New API endpoints to manage deployments. This version of ECE introduces new API endpoints that treat deployments as a single entity, so that you can manage an entire deployment as a whole. Gone are the days when you needed to use different endpoints to upgrade the Elastic Stack components of a deployment, for example. The following endpoints are all new:
- New deployment distribution strategies. One of the benefits of the ECE platform is its robust deployment distribution logic that maximizes the utilization of the underlying resources you deploy the Elastic Stack on. With ECE 2.4, we are introducing several new deployment distribution strategies that let you customize how the Elastic Stack gets distributed across the available set of allocators in your ECE installation. Check Configure allocator affinity.
- A replacement proxy for ECE. One of the most important components of Elastic Cloud Enterprise is the proxy that most users interact with and that routes all incoming requests to the right deployment. ECE 2.4 includes a brand new proxy layer that brings improved stability and fault tolerance, along with the ability to keep routing traffic to Elastic Stack deployments even if the ECE coordination layer fails completely. Although new to ECE 2.4, this replacement proxy has been running in production as part of the Elasticsearch Service for several months, across three major cloud providers and dozens of regions. The new proxy is also more memory and CPU efficient, outperforming the previous implementation.
- Updated proxy layer defaults. In previous versions, the Elastic Cloud Enterprise proxy layer permitted negotiation with a client using TLS 1.0 and an intermediate level cipher suite. The proxy settings are now updated to default to a minimum of TLS 1.2 and a modern cipher suite, but we also include support for reverting to the legacy behavior. Check Configuring the TLS version.
- Elasticsearch and Kibana 7.4.1 and 6.8.4. This version of Elastic Cloud Enterprise includes new Elastic Stack versions. Previous versions of ECE can download these versions and add them as Elastic Stack packs. To learn more about best practices when upgrading, check Upgrade versions.
Want to learn more about what’s in this release? Check out our Elastic Cloud Enterprise 2.4 announcement blog post. To upgrade to your Elastic Cloud Enterprise installation to this latest version, check Upgrade your installation.
Known problems
editThis version of ECE has a known problem with traffic filtering, where users are unable to add or manage rule sets within the Cloud UI correctly. When attempting to add a rule while creating a new rule set, there is no option to save the rule or add more rules. Instead, a Create rule set button is displayed and while attempting to create the rule set the request appears to complete successfully, the new rule set does not include the rule. As a workaround, you can create and manage rule sets with the REST API.
This issue is fixed in Elastic Cloud Enterprise 2.4.1.
This version of Elastic Cloud Enterprise has a known problem with the installation or upgrade script yielding a false negative exception when journaldis used as a logging driver in Docker daemon versions 1.12 and 1.13. This error occurs even though the underlying bootstrap or upgrade process has completed successfully. Users need to check the output of bootstrap.log
or upgrade.log
to determine if the process completed successfully.
ECE versions from 2.4.0 to 2.4.3 are affected.
This version of ECE has a known problem with App Search upgrades from versions 7.5 to 7.6: Rolling upgrades can lead to limited data loss if you are actively modifying new engines during the upgrade process. The upgrade requires App Search instances for 7.5 to be stopped before the 7.6 ones are started. As a workaround, before upgrading the 7.5 App Search instances to 7.6, you can stop the traffic towards those instances by selecting Stop routing in the UI. Once all 7.5 instances are no longer routing traffic, it is safe to perform the upgrade by selecting Upgrade.
ECE versions from 2.4.0 to 2.4.4 are affected.
This version of ECE has a known problem with upgrading Elasticsearch to versions 7.7 and higher in deployments with App Search. App Search is no longer present in those stack versions and will be replaced by Enterprise Search, which will be available in an upcoming minor version of Elastic Cloud Enterprise.
ECE versions from 2.4 and 2.5 are affected.
All App Search versions from 7.5 to 7.6 have a bug in which the system.log
file is not rotated.
Release date: October 29, 2019
On this page