- 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
Autoscaling, and more
editAutoscaling, and more
editRelease highlights
editIntroducing deployment autoscaling!

New autoscaling support on Elasticsearch Service helps you to balance cost with efficient performance by adjusting the resources available to your deployments automatically. This reduces the need for you to adjust capacity manually as requirements and loads change over time. In this initial release, data tiers can scale up automatically in response to past and present storage usage, and machine learning nodes can scale both up and down based on memory requirements for the current jobs. Learn more…
Features
editPublish Elasticsearch Service prices. Elasticsearch service pricing is now published on the Elastic website so that current pricing for all providers, regions, and instance types can be seen in one location.
Include internal details and failure type in logs. The logs generated from a plan change now contain more detail, making it easier for you to debug problems and understand why a plan may have failed. Three new attributes are now included in the step logs:
-
details
: Contains details about a step failure, visible to all console users. -
internal_details
: Contains sensitive details about the step failure, visible only to admin console users. -
failure_type
: Describes the type of failure that occurred.
Add Copy ID link to the application links. The deployment overview now has a Copy ID
link. This simplifies getting the application IDs required to set up cross-cluster search and cross-cluster replication.
Add prices app to the billing service. A prices application is added to the billing service to expose the /v1/prices/adjustment?domain=<domain-id>
endpoint as a REST API. Note that the API will validate that domain-id
is one of the types.adjustments
fields (currently "aws", "azure", "gcp", and "found") and will always return the current
adjustment.
Enable Elasticsearch searchable snapshots partial cache settings. Searchable Snapshots partial storage settings can now be configured when you create a new deployment.
Enhancements
editSend an email on GCP paused/ended unsubscribe events. GCP Marketplace customers are now emailed after disconnecting a project with the list of deployments that will be terminated if they don’t reconnect the project. The email includes the timestamp when deployment termination will occur and other details.
Turn on marketplace toggle always. Users can now see both marketplace and non-marketplace prices for AWS on the pricing page.
Enable subscription self-serve for AWS Marketplace users. AWS Marketplace users can now self-select their billing subscription level.
Improve snapshot repository logging. Error reporting is improved for certain failures that can occur when creating snapshot repositories.
Disable internal collection when Metricbeat enabled. Metricbeat monitoring performance is optimized by disabling legacy monitoring collection in Elasticsearch, Kibana, and APM when Metricbeat is in use.
Change user settings validation to validate objects as a whole . New validation rules for user settings require the order setting when specifying a custom realm through user settings for Elasticsearch clusters on version 8.0 or higher.
Stop sending extraneous exception details. Plan failures shown in the user console now have fewer extraneous, unactionable details in them.
Update go to 1.15.8. The Elasticsearch Service proxy has been updated to go version 1.15.8.
Bug fixes
editDisplay all snapshots Fixes a bug where only a subset of available snapshots were displayed in the UI, sometimes causing a message inconsistent with the snapshots that actually exist in the cluster.
Update full name and email for SSO if needed. This fix ensures that Elasticsearch Service users will get an updated display name when they SSO into a Stack application, such as Kibana, after updating their email address.
Use disk queue in Metricbeat. Fixes issues on dedicated master instances on version 7.6+ that use the monitoring feature, where memory pressure is elevated and garbage collection is more frequent on the elected master, by using the Metricbeat disk queue.
Add voting exclusion for instances losing master role. Fixes a variety of edge cases that could lead to cluster quorum loss on 7.x+ clusters, such as running a plan that switches from multiple master nodes to a single master node.
Fix "GC Overhead Per Node" metric. Fixes a bug that prevented the "GC Overhead Per Node" metric on the console Performance page from working properly.
Fix console request metrics query. Fixes bug where user console metrics would not show request metrics.
Handle terminated deployments and missing templates on Edit screen. Editing terminated or certain system deployments should no longer throw an error.
Keep legacy exporter enabled when monitoring with Metricbeat. Fixes the following three bugs:
- Legacy collection monitoring of externally deployed services (e.g. Logstash) was disabled when Metricbeat monitoring is enabled in Cloud.
- Monitoring index retention was not being enforced when self-monitoring is enabled.
- Restoring a snapshot into a new deployment with cluster state could restore broken monitoring settings that require manual Elasticsearch settings changes.
Apply correct timestamps to downloaded bundles. Fixes a bug that could cause instances to bootloop during rolling plans if a cluster is configured with user bundles.
Enable AttemptClusterStabilisation feature flag. Running a plan in which some instances will be mutated will now first (re-)start any other instances that are not running. This mitigates the risk of losing cluster quorum during certain plans (such as adding dedicated masters) when the cluster is in an abnormal state.
Use recommended JVM heap allocation for dedicated masters. Fixes an issue where dedicated masters can OOM due to over-allocated heap size
Get rid of nested retry loop. Cluster creation plans which fail will now fail faster instead of hanging unnecessarily during the rollback-migrate step.
Avoid chown of home directory when log delivery is enabled. Fixes a bug where Kibana can take a long time to start when log delivery is enabled.
Use smaller Elasticsearch heap when Filebeat and Metricbeat are running. Fixes a bug where when logs and metrics are enabled on Elasticsearch clusters: Small, master-only, instances and tiebreaker instances have memory swapping issues.
Make some ES domain fields optional. Fixes a bug that would sometimes cause plans to fail during the Migrating shard data
step.
Clear (don’t set) initial-master-nodes if cluster already bootstrapped. Clusters will no longer end up in a split brain state if masters are added while all other masters are currently offline.
On this page