- 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
Elastic Consumption Units, and more
editElastic Consumption Units, and more
editIntroducing Elastic Consumption Units!
Prepaid billing just got easier. For new annual customers on the prepaid consumption billing model, all Elasticsearch Service usage is now conveniently metered and billed in Elastic Consumption Units (ECUs). All other customers will be migrated to this model at a future date. To learn more, check Using Elastic Consumption Units for billing and our Billing FAQ.
Enhancements
editAdd transactionGroupBucketSize to allow list. Added support for the xpack.apm.ui.transactionGroupBucketSize
APM configuration setting in the Kibana User Settings editor for versions 7.16.0 and later.
Add APM configuration settings to cloud allow list. The following APM configuration settings are now supported and can be edited in the Kibana User Settings editor:
- xpack.apm.onboardingIndices
- xpack.apm.metricsIndices
- xpack.apm.sourcemapIndices
- xpack.apm.agent.migrations.enabled
- xpack.apm.serviceMapEnabled
- xpack.observability.annotations.index
- xpack.apm.maxServiceEnvironments
- xpack.apm.serviceMapFingerprintBucketSize
- xpack.apm.ui.serviceMapFingerprintGlobalBucketSize
- xpack.apm.ui.serviceMapTraceIdBucketSize
- xpack.apm.ui.serviceMapTraceIdGlobalBucketSize
- xpack.apm.ui.serviceMapMaxTracesPerRequest
- xpack.apm.ui.metricsInterval
Set nameid_format in SAML config for SSO. Elasticsearch Service now sets nameid_format
explicitly when configuring SAML realms for SSO.
Make the document-level security and field-level security features available in all environments. The DLS and FLS features are now accessible through the GET /api/v1/saas/billing/{organization_id}/features
API in all environments.
Make the searchable snapshots feature available in all environments. The searchable-snapshots
feature is now accessible through the GET /api/v1/saas/billing/usage/features
API in the all environments.
Add workplace_search.content_source.salesforce.enable_cases setting. Added configurable settings for Salesforce content source in Workplace Search (workplace_search.content_source.salesforce.enable_cases
) that allow you to enable or disable synchronization of Case Salesforce objects.
Enable expansion of time range for Billing Usage page . We removed the three month limit that applied when querying deployment information on the billing Usage page.
Add help text to region field. When creating a traffic filter a region
field must be set, however there can be a few different concepts of region at this time. This PR adds some clarifying help text to the region
field shown on the Create traffic filter UI.
EOL warnings in stack versions. Displays an End of Life warning on the Elasticsearch Service UI where the stack version and deployment lists are displayed, and the individual deployment pages, for Elastic Stack packs and deployments using versions 5.x and 2.x.
Bug fixes
editDo not meter hidden deployments. This PR updates the CTS feature-usage
task to check if the cluster instance it is about to meter usage for belongs to a hidden deployment. If so, the task does not perform any metering of that instance.
Show failed status and error in heap dump UI. Fixed a UI error when heap dump capture fails.
Deprecations
editDepreciation of CCS deployments. The dedicated Cross cluster Search deployment type is deprecated in preparation for its removal in Elasticsearch Service 3.0. It is no longer listed when creating new deployments through the UI.
Remove Azure Marketplace docs in favour of Azure integrated offering. Elasticsearch is now offered as a native service in the Azure console, providing consolidated billing with your Azure bill, simplified data ingestion for Azure logs and metrics, support for Private Link, and more. As a result of this new native service offering, Elasticsearch Service is no longer offered as part of the Azure Marketplace. To learn more the new integration, check our Native Azure integration documentation.
Revove kibana.defaultAppId. The Kibana user setting kibana.defaultAppId
has been removed from the Elasticsearch Service allow list for version 8.0, as the property will no longer be supported beginning in version 8.
Docs
editOverhaul deployment health landing page. We’ve updated our Keeping your deployment healthy page to help you find the resources needed to ensure the ongoing health of your Elasticsearch Service deployments, and to troubleshoot any problems when they arise.
Traffic Filter API Example. We’ve added several examples to help you manage traffic filters in Elasticsearch Service using the API.
Improve memory pressure documentation We’ve updated the monitoring scenario documentation for memory pressure to include additional guidance on sizing, workload, sharding, data retention, and performance tuning. Learn more …
On this page