- 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
Enhancements and bug fixes
editEnhancements and bug fixes
editThe following changes are included in this release.
Features
editAdd also_trusted_by
to certificate metadata in direct trusts. Certificate metadata in DirectTrustRelationships now lists other deployments that also trust the certificate.
Enhancements
edit[GCM][Usage Cluster] Adding usage_timestamp
and creation_timestamp
fields to Usage Records. This PR adds two new fields to Usage Records, by defining them in the usage-v*
index template:
* usage_timestamp
: the timestamp indicating the idealized end of the metering period, and
* creation_timestamp
: the timestamp when the Usage Record first comes into existence within the record producer, right before it writes said record to disk, a
Allow proxy to establish TLSv1.3 connections with willing clients. Enable TLS v1.3 on the proxies (note, establishing TLS v1.2 connections is still possible and not going away for now; this is an extra option for clients that support TLS v1.3).
Adding a deploymentId section to the new header with a copy button next to it. A more prominent and copy-able location for the deployment Id in the header of a deployment.
Allow http.connection_pool_ttl for OIDC realms. Allow user override of the new http.connection_pool_ttl setting for OIDC realms. The new setting is documented at OpenID Connect realm settings.
Promote rest of configuration to plan. The enabled_built_in_plugins
, user_plugins
, and user_bundles
configuration entries will be moved from the cluster_topology
level to the plan
level when a plan change occurs through the UI.
#100075 override clear upgrade version. Users will now be able to clear administrator set user setting overrides without needing to file a support ticket during the version upgrade process.
Bump beats version to 7.17.5. Upgrades filebeat and metricbeat used to ingest logs and metrics in ECE to 7.17.5.
Allow users to clear override settings on the Edit page. Users are now able to clear administrator set user setting overrides without needing to file a support ticket. Go to the Edit page of your deployment and if an override is set, select the Clear overrides button.
Expose deployment.autoscaling_enabled fields in the API models. Introduce autoscaling_enabled
at the deployment level. This will be consistent with the autoscaling_enabled
field on the Elasticsearch resource. In the future this value will also be used to enable autoscaling on other resources within a deployment.
81858: Log Initial Data Step added to all the flows. This change adds new step named "Log Initial Data" on UI that just prints cluster_id, plan_id and constructor for all the flows. Earlier calculate incremental change used to print this info but this step was applicable to only modification/edit flow. With this change cluster_id, plan_id and constructor will be printed for all the flows.
Bug fixes
editBugfix: Re-enable monitoring cleaner service.. Fixed monitoring indices not being cleaned up regularly.
When using the [logging and monitoring feature](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-enable-logging-and-monitoring.html), monitoring data is supposed to be removed after a retention period (Default: 3 days). A bug lead to the data being stored indefinitely. The monitoring indices are now again being cleaned up correctly after the configured retention period.
Don’t rebuild the topology element when configuring autoscaling_min
. Fixes an issue preventing users from updating the maximum size of ML tiers.
Added fields to APM allow list. Added the following settings to the APM allow list:
-
xpack.apm.maxServiceSelection
(v7.13 - v7.16) -
xpack.apm.maxSuggestions
(v7.16)
Issue # 100465 - Stop sending the verification email to non-GCP/AWS new users. We no longer push users to verify their email address (https://github.com/elastic/cloud/issues/85396) but we’re still sending the verification email to users. Let’s stop sending this email out since new users get a lot of additional emails during the trial journey, and this email serves no purpose anymore. This is applicable for Azure, Found and Heroku users. We will continue sening verification emails to AWS and GCP users for now.
[Legacy Biller] Updating algorithm to compute snapshot storage size. This PR updates the algorithm for computing snapshot storage size in the legacy biller, concretely implemented in the _get_snapshot_storage_usage
method.
Deprecations
editSet maximum version for xpack.apm.maxServiceEnvironments
. xpack.apm.maxServiceEnvironments
has been deprecated in 8.0.0
.
The setting has been replaced by maxSuggestions
which can be configured in Kibana’s Advanced Settings.
On this page