- 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
Better feature usage tracking, new cost and usage analysis page, and more
editBetter feature usage tracking, new cost and usage analysis page, and more
editRelease highlights
editFeature usage tracking for self-service customers. It is now possible for customers to analyze their Elastic Cloud feature usage and choose the subscription level that best fits their needs.
Cost and usage analysis page. To help users better understand their costs, we have introduced a new Usage analysis page under Account & Billing. The Usage analysis page allows you to filter historical data and break down usage by deployment, as well as by product. For annual and overages customers, it also shows how many credits will be applied for the current bill cycle.
Features
editUnhide deployment aliases fields from Deployments API. Deployment Alias field alias
added to support user-friendly URLs for deployment resources.
Log delivery health status. Callout section lists all observability health issues for a deployment.
Add data tiers to UI. Data tiers and their associated Elasticsearch node.roles
are now supported in the UI.
Enhancements
editUpdated the user menu hover and focus state. Fixes minor visual bugs in the user menu. The buttons were not the full width of their parent, and the focus state was emphazising that issue. In addition, the moon
icon had the wrong colour.
Allow the vis_type_table.legacyVisEnabled kibana setting. Adds new datatable setting vis_type_table.legacyVisEnabled
to allow list. This setting can be used to switch to the legacy datatable.
GovCloud Registration page. Allows GovCloud users to self-service registration.
Start using Metricbeat for monitoring for 7.6+ clusters. For 7.6+ deployments, monitoring will now be implemented using Metricbeat since legacy collection monitoring is deprecated and planned for removal. Any deployment update executed on a monitored 7.6+ deployment will undergo a one-time rolling plan change to transition the deployment to Metricbeat-based monitoring.
Allow Kibana CORS settings on Cloud. Cloud adds Cross-Origin Resource Sharing (CORS) support for Kibana with the following settings:
server.cors.enabled
- Set to true
to allow cross-origin API calls. Default: false
.
server.cors.allowCredentials
- Set to true
to allow browser code to access the response body whenever the request is performed with user credentials. Default: false
.
server.cors.allowOrigin
- List of origins permitted to access resources. You must specify server.cors.allowOrigin
when server.cors.allowCredentials: true
. Default: ["*"]
Implement new deployment features navigation and page. Adds new deployment features ESS navigation item and page.
Remove subscription from the user menu. The subscription level badge is removed from the user menu. Users should navigate to Account & Billing to view their subscription level.
Bug fixes
editUpdating disk notifications toggle to reflect default setting. Fixes default UI setting for disk notifications.
chmod user bundles after unpacking them. User bundles with read-only files or folders will no longer cause nodes to boot loop on restart.
Fix stuck allocator task scheduler. Fixes the issue with duplicated ticks and leader latches in ClusterTaskScheduler
by introducing a scheduler with a single fixed tick loop.
No Kibana upgrade. Fixes a bug where a disabled or terminated Kibana would not allow users to upgrade their deployment version.
Fix company info validation. Fixes a bug that was improperly validating user inputs when they were updating their credit card information.
Fix action after enabling monitoring on a deployment. Fixes issue when enabling Logs and metrics on a deployment. User sees the Enable button before the status flips to pending and shows the new monitoring deployment.
Fix YAML parser in UI. Fixes a bug where attempting to save YAML settings that only include comments resulted in an error message: The YAML settings are invalid, please check your syntax
.
Re-enable allocations when major version upgrade fails. Re-enables allocations by setting them back to all
after a (rolling) major version upgrade fails. Allocations are also set to primaries
and not none
before rolling an instance, as recommended by Elasticsearch.
Fix partial upgrade bug. Fixes a bug preventing the upgrade of deployments with Elasticsearch instances on different versions.
Remove issue time so that JWT don’t change from plan to plan. Fixes an issue where when log delivery is enabled, a force restart plan causes instances to be created.
Fix Kibana metrics link errors. Fixes errors that are shown in Kibana when following metrics links from logs and metrics UI.
On this page