- 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
Organization and billing API updates, and more
editOrganization and billing API updates, and more
editThe following changes are included in this release.
Features
editRevert the 8.0.0 specific format parsing. Elasticsearch Service now expects the same format for 8.0 snapshot API responses as was used in version 7.x.
Add live "in-app" EOL notifications. Add notifications for deployments which are approaching, or have reached EOL status.
Enhancements
editAdapt user settings for 7.17 and 8.0. Follow up for allowed user overridable config changes for APM Server 7.17 and 8.0.
Accessibility fix: added aria-label to "remove contact" button. Add screen reader label to the button for removing contacts.
Breaking down billing dimensions costs in the responses. Change the responses for the Costs Analysis APIs. In particular, the CostsOverview
renames resources
to capacity
and it replaces the data_transfer_and_storage
field with its equivalent breakdown into capacity
, data_in
data_out
, data_internode
, storage_bytes
and snapshot_storage
fields.
Elasticsearch deprecation logger level (ES7.16). Incorporate version 7.16 and newer deprecation level (CRITICAL/WARN) changes.
This commits updates deprecation log config to the ES7.17. Updates elasticsearch log4j config for 7.17 to contain additional field x-elastic-product-origin (and a few others that needed to be included).
Add APM auto-create settings to cloud allow list. Allow xpack.apm.autocreateIndexPattern
(for Kibana versions 7.6.0-7.16.0) and xpack.apm.autoCreateDataView
(renamed for ≥ 8.0.0) to be configured for the APM UI in Kibana on Cloud deployments.
Update disable sandbox option for reporting. Kibana configuration option xpack.reporting.capture.browser.chromium.disableSandbox
has been renamed to xpack.screenshotting.browser.chromium.disableSandbox
in 8.0.
Make organization APIs public. Organization management APIs are now available in the Elasticsearch Service public API.
Bug fixes
editBump co.elastic.support:diagnostics version to 8.2.7. Use version 8.2.7
of the Elastic support diagnostics, which includes the fix for Kibana version 8.0.
Show APM if terminated APM exists after upgrade to 8.0. Fixes a bug where if APM was terminated before or after upgrading from 7.17 to 8.0, the side navigation would show a menu item for Integrations Server instead of APM/Fleet.
Use vault on the bucket_capacity_show command. Change the password source for the bucket_capacity_show
command to be the vault.
Hide APM settings when in managed mode. Hides APM user settings when APM is in managed mode as user settings are not supported.
Show operations when pending plan is running if it isn’t a create plan. Fixes a bug where the Operations page is not displayed when a plan is in progress.
Disable logging and metrics warnings on downscaled topologies. Improves the observability configuration checks that produce alerts, reducing the number of false positives that aren’t applicable to downscaled configurations.
Deprecations
editRemove obsolete proxy settings from internal models. The proxy settings APIs have been deprecated because these settings were no longer used. The API endpoints still exist, but will not update or return actual settings anymore. In addition, the Adminconsole no longer takes the expected_proxies_count
setting into account when it determines the overall proxies health.
Comment out updating enable disk allocation setting. You can no longer disable disk-based shard allocation through the plan. If you need to do so, you can do it directly through the Elasticsearch cluster settings API.
Docs
editNew guide to migrate Elasticsearch data. Adds a new step-by-step guide on how to migrate from a self-managed, self-signed cluster to Elasticsearch Service by using a remote reindex.
Update node content. Updated the description on how nodes are automatically calculated based on the size chosen. Also updated the screen capture.
Update 6.8 upgrade documentation to indicate EOL. We’ve updated the Elastic Stack version 6.x upgrade instructions to indicate that version has reached the EOL date. If you are running this version, we recommend you to upgrade your deployment to a more current version of the Elastic stack.
On this page