- Introducing Elasticsearch Service
- Adding data to Elasticsearch
- Migrating data
- Ingesting data from your application
- Ingest data with Node.js on Elasticsearch Service
- Ingest data with Python on Elasticsearch Service
- Ingest data from Beats to Elasticsearch Service with Logstash as a proxy
- Ingest data from a relational database into Elasticsearch Service
- Ingest logs from a Python application using Filebeat
- Ingest logs from a Node.js web application using Filebeat
- Configure Beats and Logstash with Cloud ID
- Best practices for managing your data
- Configure index management
- Enable cross-cluster search and cross-cluster replication
- Access other deployments of the same Elasticsearch Service organization
- Access deployments of another Elasticsearch Service organization
- Access deployments of an Elastic Cloud Enterprise environment
- Access clusters of a self-managed environment
- Enabling CCS/R between Elasticsearch Service and ECK
- Edit or remove a trusted environment
- Migrate the cross-cluster search deployment template
- Manage data from the command line
- Preparing a deployment for production
- Securing your deployment
- Monitoring your deployment
- Monitor with AutoOps
- Configure Stack monitoring alerts
- Access performance metrics
- Keep track of deployment activity
- Diagnose and resolve issues
- Diagnose unavailable nodes
- Why are my shards unavailable?
- Why is performance degrading over time?
- Is my cluster really highly available?
- How does high memory pressure affect performance?
- Why are my cluster response times suddenly so much worse?
- How do I resolve deployment health warnings?
- How do I resolve node bootlooping?
- Why did my node move to a different host?
- Snapshot and restore
- Managing your organization
- Your account and billing
- Billing Dimensions
- Billing models
- Using Elastic Consumption Units for billing
- Edit user account settings
- Monitor and analyze your account usage
- Check your subscription overview
- Add your billing details
- Choose a subscription level
- Check your billing history
- Update billing and operational contacts
- Stop charges for a deployment
- Billing FAQ
- Elasticsearch Service hardware
- Elasticsearch Service GCP instance configurations
- Elasticsearch Service GCP default provider instance configurations
- Elasticsearch Service AWS instance configurations
- Elasticsearch Service AWS default provider instance configurations
- Elasticsearch Service Azure instance configurations
- Elasticsearch Service Azure default provider instance configurations
- Change hardware for a specific resource
- Elasticsearch Service regions
- About Elasticsearch Service
- RESTful API
- Release notes
- Enhancements and bug fixes - February 2025
- Enhancements and bug fixes - January 2025
- Enhancements and bug fixes - December 2024
- Enhancements and bug fixes - November 2024
- Enhancements and bug fixes - Late October 2024
- Enhancements and bug fixes - Early October 2024
- Enhancements and bug fixes - September 2024
- Enhancements and bug fixes - Late August 2024
- Enhancements and bug fixes - Early August 2024
- Enhancements and bug fixes - July 2024
- Enhancements and bug fixes - Late June 2024
- Enhancements and bug fixes - Early June 2024
- Enhancements and bug fixes - Early May 2024
- Bring your own key, and more
- AWS region EU Central 2 (Zurich) now available
- GCP region Middle East West 1 (Tel Aviv) now available
- Enhancements and bug fixes - March 2024
- Enhancements and bug fixes - January 2024
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- AWS region EU North 1 (Stockholm) now available
- GCP regions Asia Southeast 2 (Indonesia) and Europe West 9 (Paris)
- Enhancements and bug fixes
- Enhancements and bug fixes
- Bug fixes
- Enhancements and bug fixes
- Role-based access control, and more
- Newly released deployment templates for Integrations Server, Master, and Coordinating
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Enhancements and bug fixes
- Cross environment search and replication, and more
- Enhancements and bug fixes
- Enhancements and bug fixes
- Azure region Canada Central (Toronto) now available
- Azure region Brazil South (São Paulo) now available
- Azure region South Africa North (Johannesburg) now available
- Azure region Central India (Pune) now available
- Enhancements and bug fixes
- Azure new virtual machine types available
- Billing Costs Analysis API, and more
- Organization and billing API updates, and more
- Integrations Server, and more
- Trust across organizations, and more
- Organizations, and more
- Elastic Consumption Units, and more
- AWS region Africa (Cape Town) available
- AWS region Europe (Milan) available
- AWS region Middle East (Bahrain) available
- Enhancements and bug fixes
- Enhancements and bug fixes
- GCP Private Link, and more
- Enhancements and bug fixes
- GCP region Asia Northeast 3 (Seoul) available
- Enhancements and bug fixes
- Enhancements and bug fixes
- Native Azure integration, and more
- Frozen data tier and more
- Enhancements and bug fixes
- Azure region Southcentral US (Texas) available
- Azure region East US (Virginia) available
- Custom endpoint aliases, and more
- Autoscaling, and more
- Cross-region and cross-provider support, warm and cold data tiers, and more
- Better feature usage tracking, new cost and usage analysis page, and more
- New features, enhancements, and bug fixes
- AWS region Asia Pacific (Hong Kong)
- Enterprise subscription self service, log in with Microsoft, bug fixes, and more
- SSO for Enterprise Search, support for more settings
- Azure region Australia East (New South Wales)
- New logging features, better GCP marketplace self service
- Azure region US Central (Iowa)
- AWS region Asia Pacific (Mumbai)
- Elastic solutions and Microsoft Azure Marketplace integration
- AWS region Pacific (Seoul)
- AWS region EU West 3 (Paris)
- Traffic management and improved network security
- AWS region Canada (Central)
- Enterprise Search
- New security setting, in-place configuration changes, new hardware support, and signup with Google
- Azure region France Central (Paris)
- Regions AWS US East 2 (Ohio) and Azure North Europe (Ireland)
- Our Elasticsearch Service API is generally available
- GCP regions Asia East 1 (Taiwan), Europe North 1 (Finland), and Europe West 4 (Netherlands)
- Azure region UK South (London)
- GCP region US East 1 (South Carolina)
- GCP regions Asia Southeast 1 (Singapore) and South America East 1 (Sao Paulo)
- Snapshot lifecycle management, index lifecycle management migration, and more
- Azure region Japan East (Tokyo)
- App Search
- GCP region Asia Pacific South 1 (Mumbai)
- GCP region North America Northeast 1 (Montreal)
- New Elastic Cloud home page and other improvements
- Azure regions US West 2 (Washington) and Southeast Asia (Singapore)
- GCP regions US East 4 (N. Virginia) and Europe West 2 (London)
- Better plugin and bundle support, improved pricing calculator, bug fixes, and more
- GCP region Asia Pacific Southeast 1 (Sydney)
- Elasticsearch Service on Microsoft Azure
- Cross-cluster search, OIDC and Kerberos authentication
- AWS region EU (London)
- GCP region Asia Pacific Northeast 1 (Tokyo)
- Usability improvements and Kibana bug fix
- GCS support and private subscription
- Elastic Stack 6.8 and 7.1
- ILM and hot-warm architecture
- Elasticsearch keystore and more
- Trial capacity and more
- APM Servers and more
- Snapshot retention period and more
- Improvements and snapshot intervals
- SAML and multi-factor authentication
- Next generation of Elasticsearch Service
- Branding update
- Minor Console updates
- New Cloud Console and bug fixes
- What’s new with the Elastic Stack
Enhancements and bug fixes
editEnhancements and bug fixes
editThe following changes are included in this release.
Features
editDisplay storage for all data nodes. Display storage amount for all data instances on the create deployment page.
Dynamically apply changes to v6 Kibana saved objects in ApplyKibanaClusterSystemAssets so they’re compatible with 7.12. ECE 2.11 introduces the upgrade of the logging-and-metrics system cluster to version 7.12.
There is a possibility that some of the default ECE dashboards break after the upgrade - in particular, we’ve identified that some of the visualizations in the [Metricbeat Docker] Overview
dashboard are likely to break. For that reason, we advise that users export Kibana saved objects through the Kibana UI before upgrading ECE to 2.10. If they notice that a Kibana dashboard is not working after the upgrade, they should reimport the saved object through the Kibana UI.
Enhancements
editRework conditional logic for ValidateEnoughDiskSpace. The step "Validating disk space" will not show up as often in the plan activity log for plans which do not downsize the cluster.
Force new Kibana instance if the deployment alias changes. Restart Kibana when the deployment alias is changed. This is to make sure the server.publicBaseUrl
setting in Kibana is picked up on changes to the deployment alias.
Set server.publicBasePath
for every Kibana deployment. Every cloud deployment of Kibana will have the setting server.publicBasePath
automatically configured to the URL of Kibana.
Rework conditional logic for EnsureCleanAllocationsStep. The step "Ensuring valid shard allocation rules are present" will not run as often during plans when it doesn’t need to.
[ZK History pruning] Stale attempts detection and autocleaning. - Adds a mechanism by which plan attempts entries older than 30 days (this age can be changed through the STALE_ATTEMPTS_AGE
constructor service environment variable) will be deleted upon plan changes as long as they are not the last train of failed old attempts or the last old successful attempt.
Rework conditional logic for RunIndexCuration. The step "Running index curation" will not run during plans as often when it does not need to.
Enable data pipeline logging on director. Director service logs are now shipped to the logging & metrics cluster.
Rework conditional logic for ApplyCurationSettings. The step "Applying index curation settings" will not run as often when it does not need to.
Adding monitoring.cluster_alerts.allowedSpaces to Kibana settings. Allows users to restrict which spaces the auto generated cluster alerts are created in for Stack Monitoring.
Add Kibana ECS audit settings. Adds new Kibana ECS audit logging settings to allow list.
Bug fixes
editUse validated deployment alias for ConfigSettingsService. Fixes a bug to correctly update server.publicBaseUrl
when removing the alias from a deployment.
Tolerate absent awareness.attributes. Fixes a bug that would cause plans to fail if an ES cluster had transient awareness settings without specific attributes set.
Don’t show "Delete APM" in every plan change when it’s been already deleted. Fixes a bug where, after Enterprise Search or APM are removed from a deployment, they still appear in the UI plan summary in subsequent plan changes, as if they were not removed from the deployment.
Limit master instances to one node per zone. Fixes a bug that allowed users to have more than one dedicated master node in a zone.
Fix crashes in the deployment template view when the monitoring deployment couldn’t be found. When a deployment template includes observability configuration, the deployment template view would incorrectly search for the referenced deployment by cluster ID, not by deployment ID. When this fails to match any deployments, the entire page would fail. Now we can correctly search by deployment ID, and show a relevant error when no deployment is found.
Fix title alignment in Billing tabs. A recent update to the billing area caused a very minor inconsistency with the vertical alignment of titles across the different tabs. This is now fixed.
Docs
editTraffic filters are not compatible with monitoring due to Metricbeat. Traffic filtering is not compatible with monitoring.
On this page