- 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.1.0
editElastic Cloud Enterprise 2.1.0
editHighlights for Elastic Cloud Enterprise version 2.1.0:
- Run cross-cluster searches. The Cross-Cluster Search API is now available and allows any node to act as a federated client across multiple clusters. A cross-cluster search node connects to a remote cluster in order to execute federated search requests, without joining that node to the remote cluster. Benefits of cross-cluster search include more powerful logging scenarios and the ability to split up monolithic deployments. Check Enable cross-cluster search and cross-cluster replication.
-
Deploy APM Server. When you create or edit Elastic Stack deployments, you can now stand up an APM Server and get the secret token to configure your APM Agents. The APM Server is already hooked up to work with Elasticsearch and Kibana. Check Manage your APM Server (versions before 7.13).
APM requires 6.3.0 or later, but you can upgrade your deployment to a supported version first, then add APM to your deployment.
- Restrict connections with IP Filtering. An important security layer to control traffic to your deployments, you can now apply IP filtering to application clients, node clients, or transport clients, in addition to other nodes that are attempting to join an Elasticsearch cluster. You enable IP filtering by creating rule sets that allow specific IP Addresses. Check IP traffic filters.
- Keep sensitive settings in the Elasticsearch keystore. Elastic Cloud Enterprise now supports the Elasticsearch keystore as a RESTful API-only feature that allows you to securely store your settings. Check Secure your settings.
- New versions of the Elastic Stack. Elastic Cloud Enterprise now supports the latest versions of the Elastic Stack, including 5.6.14 and 6.6.0.
- Disk-based shard allocation settings are now enabled by default. These settings affect only newly created clusters.
- Proxy HTTP requests to clusters through the API. This allows you to send RESTful API requests to a specific cluster.
To upgrade to Elastic Cloud Enterprise version 2.1.0, check Upgrade your installation and take note of the updated installation prerequisites for Docker in the next section. For offline (air-gapped) installations: After you complete the upgrade, you must also download the APM server images for the Elastic Stack versions that you plan to use.
Updated prerequisites
editNew recommended Docker version. After internal testing, we now officially support and recommend Docker 18.09.02 as an installation prerequisite for Elastic Cloud Enterprise. To learn more about the installation of Docker for supported Linux distributions, check Configure your operating system. For existing installations, follow the steps in Perform host maintenance when upgrading to Docker 18.09.02.
Previously, we primarily recommended Docker 1.11 for use with Elastic Cloud Enterprise. We no longer recommend this version, but some Linux distributions might work with other versions of Docker. To check which versions of Docker we support, refer to the Linux distributions.
Bug Fixes
editElastic Cloud Enterprise version 2.1.0 includes the following bug fixes:
-
Fixed snapshot storage integrations. ECE 2.0 broke a number of different snapshot storage integrations, which this version fixes:
- Minio: You can now use Minio again with Elastic Stack version 6.5 or later. If you have a deployment on on earlier versions of the Elastic Stack, upgrade the deployment to version 6.5 or later after upgrading ECE.
- GCS: Google Cloud Storage is also supported again, without needing to allow access to Cloud APIs from the host.
- Azure: A possible workaround to reenable Microsoft Azure Storage is still being investigated.
- Improved checks when uploading Elastic Stack packs. ECE now perform additional checks when uploading new versions of the Elastic Stack to prevent the upload of empty ZIP files.
Release date: January 29, 2019
On this page