- 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
- March 25, 2025
- Enhancements and bug fixes - March 2025
- 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
editOfficial Elastic diagnostics tool now supported. In an effort to streamline how we support you, Elasticsearch Service now integrates the Elasticsearch and Kibana diagnostics tooling that comes with the stack.
Enhancements
editLimit compatible versions for CCS/CCR, starting with 8.0. This release of Elasticsearch Service updates the rules for which versions are compatible to be used together for cross-cluster search and cross-cluster replication.
Add Kibana diagnostics. Adds the POST /deployments/{deployment_id}/kibana/{ref_id}/diagnostics/_capture
endpoint to retrieve Kibana diagnostics.
Track machine learning usage in all environments. Track the machine learning feature via the GET /api/v1/saas/billing/usage/features
API in all environments.
Reduce docker health-related plan failures. When docker is not healthy, allocators are not able to start new instances, which will cause failed plans. This change makes sure that allocators where docker is not healthy are avoided when allocating new instances.
Update Backend Response Time to include a list of attempted instances. Adds a list of backend_response_time for all the instances that the proxy attempted. This helps to see how many instances the proxy tries to connect to and the response time from each of those instances.
Don’t run SetQuorumSize for 7.x clusters. Plans for version 7.x and later clusters will no longer execute the step "Setting Elasticsearch cluster quorum size".
Improve the deployment pricing table. Now you can filter the deployments pricing table page by the marketplace provider.
When upgrading to 7.14, default to migrating to node_roles. A deployment being upgraded to version 7.14 or higher defaults to migrating from the deprecated node_type
to node_roles
.
Add Elasticsearch diagnostics. Adds the POST /deployments/{deployment_id}/elasticsearch/{ref_id}/diagnostics/_capture
endpoint to retrieve cluster diagnostics.
Bug fixes
editMake sure every cluster data contains a self-reference to the same cluster. Fixes the cluster metadata so internal requests to Kibana (for example, the Kibana proxy endpoints) work when using traffic filters.
Remove the APM rate_limit
max values. Removes the maximum value limits of 100
, 100
and 3000
for the APM server settings:
-
apm-server.rum.rate_limit
-
apm-server.frontend.rate_limit
-
apm-server.rum.event_rate.limit
Prevent crashes on pages translated with Google Translate. Fixes crashes in certain interactions of the login, reset password, and billing pages when they are translated using Google Translate.
Fixed a bug that applied the default traffic filters when a deployment is edited. When existing deployments were edited, even for no-op plans, the default traffic filters were being applied.
Respect extendedMaintenance during rolling step. Fixed a bug which caused plans to disable maintenance mode too early when applying rolling changes to nodes during a plan which uses extended maintenance.
Deprecations
editSecure tunneling page is deprecated. Our Tunneling SSL documentation page has been marked as deprecated and will be removed in an upcoming release. We do not recommend using HTTP clients to connect to Elastic Cloud. If you need to do so, you should use a reverse proxy setup. If you have any concerns, please contact support.
Enable the vis_type_vega.enableExternalUrls . In Elastic Stack version 8.0.0, the vega.enableExternalUrls
YAML setting will be removed (elastic/kibana#112643).
Use the vis_type_vega.enableExternalUrls
setting instead.
Supports timelion.ui.enabled until v7.16. Removes support for the timelion.ui.enabled
kibana.yml setting due to the removal of the Timelion app in the Elastic Stack version 7.16.
Adds a max version in the vis_type_table.legacyVisEnabled setting. The vis_type_table.legacyVisEnabled
setting is supported until Elastic Stack version 7.16.x.
Docs
editAdd a new section on Best practices for managing your data. We have added new guidelines to help our customers manage their data when they use Elasticsearch Service. These best practices are also accessible from the Shared responsibilities page.
Add Node.js application logging tutorial to Elasticsearch Service docs. As a further expansion to our Elasticsearch Service ingestion documentation, we’ve added a new guide Ingest logs from a Node.js web application using Filebeat.
On this page