- 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.0.0
editElastic Cloud Enterprise 2.0.0
editNew for Elastic Cloud Enterprise version 2.0.0:
-
Changed username for all new installations of ECE. You should now use
admin
as the username for the user that is created during installation. For installations upgraded from 1.x, theroot
user is still available until the next major version; all new 2.x installations have only theadmin
andreadonly
users. - New deployment templates for the Elastic Stack. Deploy the Elastic Stack using our new deployment templates. These flexible, customizable templates are designed to fit your use case better, whether it’s search, logging or whatever challenge you can think up for Elastic Cloud Enterprise.
- New customizable deployment templates for your hardware. Create your own deployment templates that are designed to work with your hardware. By first creating instance configurations that tell ECE what kind of hardware you have, you can provide the building blocks that you can then create deployment templated from. Create your own templates that are optimized for I/O, CPU, memory, and storage to match your use case.
-
New machine learning capabilities. Add machine learning to your deployments to gain insight and predict anomalies. Previously available for the Elastic Stack on-prem, now supported on Elastic Cloud Enterprise.
Machine learning requires Elasticsearch version 6.3.1 or later, but you can upgrade your deployment to a supported version first and then add machine learning.
- New hot-warm architecture with index lifecycle management. Quickly ingest and query current data, while keeping older data around on more cost-effective storage. If you need a complete logging solution, this is it.
- Additional Kibana deployment capabilities. Deploy Kibana across multiple availability zones with your Elasticsearch cluster and scale Kibana to whatever size you need.
- New dedicated master nodes. Improve the resilience of your deployments by adding dedicated master nodes. Larger-scale deployments get them automatically.
- Additional snapshot interval configuration. Quickly change your snapshot interval using the Cloud UI.
- Better networking and ports guidance. Need a better understanding of how our products communicate with each other and on which ports? Check out our improved ECE networking and ports page.
- New night mode capability. Enjoy our new night mode in the Cloud UI. UI too bright when you want to focus on work? Try the night mode, available in the Cloud UI.
- Improved security for Elasticsearch clusters and Kibana instances. To secure your Elasticsearch clusters and Kibana instances, use a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication.
- Support for installing ECE on Ubuntu 16.04 using Docker 18.03. Docker 1.13 is still supported, but now users that wish to use a newer Docker version have an upgrade path.
- Support for full encryption. Full encryption is supported for all internal network traffic, including traffic between nodes in a cluster, and between proxies, clusters, and all internal services.
As before, you can manage hosted Elasticsearch and Kibana from our Cloud UI. Our UI might look different with its new sliders, but your existing deployments will continue to work exactly as before.
To upgrade to Elastic Cloud Enterprise version 2.0.0, check Upgrade Your Installation. After you complete the upgrade, configure deployment templates for ECE to indicate what kind of hardware you have available for Elastic Stack deployments.
Known problems or limitations
editThe following known problems or limitations exist for ECE 2.0:
- You cannot convert Elastic Stack deployments between templates. For example: A deployment created with the default template cannot be converted to a hot-warm template. You can work around this limitation by creating a new deployment with the template you want and restoring your data using a snapshot from the original deployment.
- This version of ECE is known to have a problem with snapshot storage integrations, breaking support for Minio (when using the Elastic Stack 6.4.2 or later), Google Cloud Storage (GCS), and Microsoft Azure Storage. Except for Microsoft Azure Storage, these storage integrations are available again in ECE 2.1 and we recommend that you upgrade to this later version. A possible workaround to reenable Microsoft Azure Storage is still being investigated. After upgrading to ECE 2.1, you might also need to upgrade your deployments to the Elastic Stack 6.5.0 or later to reenable snapshot storage support.
Breaking changes
editThere are no breaking changes for ECE 2.0.
Release date: September 25, 2018
On this page
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now