- 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
New features, enhancements, and bug fixes
editNew features, enhancements, and bug fixes
editThis release includes a number of new features, enhancements, and bug fixes.
Features
editAdd endpoint for determining supported applications. Add an endpoint listing the applications that the user can access from Okta.
curl -H "Authorization: Bearer $AUTH_TOKEN" http://192.168.40.10.ip.es.io:22400/api/v1/saas/user/applications
Sample response:
{ "applications": [ "training", "dream-machine" ] }
Enhancements
editAlert users about features outside of subscription level. We now alert you if you are using features that are outside of what is included with your subscription level.
New button for creating a monitoring deployment. Add button to create a monitoring deployment on the Logs and Metrics page when only one or no deployment are available.
Default disk quota multipliers (constructor). The constructor service is updated to recognize default disk quota multipliers for each known cluster type.
The constructor now supports three new environment variables:
- ES_DISK_QUOTA_MULTIPLIER - Default disk quota multiplier for Elasticsearch instances. If the multiplier is not defined in an instance configuration, this value is used. optional. the default value is 32
- KB_DISK_QUOTA_MULTIPLIER - Default multiplier for Kibana. optional. the default value is 4
- APM_DISK_QUOTA_MULTIPLIER - Default multiplier for APM. optional. the default value is 4
Make API keys API endpoint public. You can now manage API keys via the keys
API endpoint in addition to managing them through the UI.
Add dedicated master nodes when autoscaling a cluster. The autoscaling request handler can now perform post-processing of scaled cluster specification and automatically add dedicated masters, if the number of nodes (any combination of roles, other than dedicated masters) exceeds the threshold. The default number of nodes is six and is defined in the cluster settings.
Add Support portal link. For users with a Support account, the Support page now includes a link to the Elastic Support portal.
Add node_roles support to the EsClusterTopologyElement. Add a new nodeRoles
field to the EsClusterTopologyElement
for Elasticsearch version 7.10 and later.
Add Workplace Search sync monitor configs. Add Workplace Search content source sync error configurations to the configuration allowlist (whitelist).
Bug fixes
editFix staging adminconsole metrics link. We fixed a bug that caused improper ece.cluster
filtering on detailed cluster link in the staging adminconsole.
Fix YAML parser in UI. Fixed 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
. Saving these YAML settings now works as expected.
JSON Web Tokens no longer change from plan to plan. Fixed an issue where, when log delivery is enabled, a force restart plan caused instances to be created.
Add metadata to IBM default template for default UI select. The default deployment template is selected by default on IBM regions.
Transform SSO and observability plan sections after deployment defaults are generated. The Elastic Cloud Deployments API allows users to omit an Elastic Stack version when creating a new deployment, which enables the system to choose the latest available version. A bug has been fixed where this behavior caused Elastic Cloud to Kibana SSO to not be available when the version was left out.
Update breadcrumbs on update of content. - Breadcrumbs for the ECE SAML, LDAP, and Active Directory pages were not showing up correctly, which is now fixed.
Fix bootloop error message. Fixed a misleading error message that claimed an instance was boot looping even if it may not have been.
Fix issue where APM or AppSearch could get flagged valid for SSO. The Cloud Deployments API had a bug fixed where requests to create or update a deployment can fail in some cases when APM resources share the same ref_id
value as Kibana or Enterprise Search. The bug caused the API to consider APM valid for SSO during preliminary logic to build up the API identity.service_provider
plan section, but then failed validation when sending the plan to the constructor component.
Fix JSON search slow logs and deprecation logs. Fixed an issue where, when log delivery is enabled, slow logs don’t always get ingested.
Don’t include SSO realm settings when determining if Kibana basic realm should be included. For Cloud SSO, Cloud does not include a basic auth provider (username + password login form) if the system detects that customers have other auth providers configured through custom Kibana settings. There is a bug where, if customers modify the Kibana settings for the auto-generated SAML realm used for Cloud SSO (with the name in the format cloud-saml-kibana-$KIBANA_ID
), the basic auth provider is not added. This bug is now fixed, as we only look at customer-provided auth providers and realms while determining if the basic provider should be included.
Skip cross links update on cluster creation. When creating a deployment we resolve all cross-linked resources in the deployment (resources that are linked to the same Elasticsearch) and we populate those links in cluster data when creating each resource. This means that for each resource linked to an Elasticsearch, we add <cluster_type>_cluster_id
: <cluster-id>` in each other resource that is linked to the same Elasticsearch.
Fix snapshot suspension. During plan changes, we suspend automatic snapshotting, so that snapshots do not conflict with any of the changes defined in the plan. There was a bug where, in some cases, this suspension was not lifted at the end of the plan, which caused snapshotting to remain suspended. This bug fix ensures that the snapshot suspension is always lifted when a plan is completed.
Correctly update ES security realms when adding an SSO-enabled resource to a deployment. We fixed a bug where single sign-on (SSO) is not enabled when adding a new Kibana instance (7.7.0 and later) or an Enterprise Search instance (version 7.9.2 and later) to a deployment.
On this page