- 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
editMake allocator add direct trust certificates to Elasticsearch. This release of Elasticsearch Service configures Elasticsearch instances to trust certificates uploaded by customers for use with remote connections to Elasticsearch clusters outside of a Cloud managed environment.
New migrate_template
endpoint to migrate a deployment to a different deployment template. Adds the migrate_template
endpoint to allow migrating a deployment to a different deployment template.
Add type parameter and more validation to DirectTrustRelationship. DirectTrustRelationships now take an optional type
parameter which enables use case specific validation and supports a more guided experience in the user interface.
Allow xpack.security.authc.realms.jwt settings. Adds support for the beta JWT realm for Elasticsearch authentication.
Enable using different domain for Microsoft Azure storage. Enables support for the different domain used by blob storage in Azure Govcloud.
Enhancements
editReset the stack version of stateless resources when they are being re-enabled. Explicitly reset the version of a stateless resource (APM, Kibana, Enterprise Search) when re-enabling the resource on the Deployment edit page. Previously, these resources would be re-enabled using the version they were last running on. This blocked further changes when the Elasticsearch resource had been upgraded to different major version (for example 7.x to 8.x).
cloud-security-posture feature flag. Adding xpack.cloudSecurityPosture.enabled:
Kibana feature flag for cloud-security-posture.
Replace watcheralert.found.io references with alerts.elastic.co. Changes the email address references for watcher alert emails from watcheralert.found.io
to alerts.elastic.co
.
Allow monitoring to be shipped to a deployment running the next major version. Allow logs and metrics to be shipped to deployments running the next major version via the UI. For example, a 7.x deployment can now be configured to ship monitoring data to an 8.x deployment.
In runner’s reference.conf, set notification-email-from to Watcher Alert <noreply@alerts.elastic.co> by default. Changes the email address that’s used as sender for the Watcher alert emails from noreply@watcher.elastic-cloud.co
to noreply@alerts.elastic.co
. The change will apply to newly created deployments and when applying a plan to existing deployments.
Change sender address for Kibana alerts. Changes the email address that’s used as sender for Kibana alert emails from alerts-noreply@elastic.co
to noreply@alerts.elastic.co
. The change will apply to newly created deployments and when applying a plan to existing deployments.
Don’t show the APM secret token when APM is in managed mode. Stop showing the APM secret token when APM is managed by the Elastic Agent. Instead link through to the Fleet UI containing the secret token.
Adds support for service logs that are sent directly to Firehose. For example Route 53 query logging, Firewall, etc. These logs are configured to send to a given Firehose delivery stream instead of going through CloudWatch log group first.
Output log event looks like this:
{ "_index": ".ds-logs-aws.route53_resolver-default-2022.04.15-000001", "_type": "_doc", "_id": "660ddd8aaa", "_version": 1, "_score": 1, "_source": { "message": "{\"version\":\"1.100000\",\"account_id\":\"12345\",\"region\":\"us-east-1\",\"vpc_id\":\"vpc-e8722d92\",\"query_timestamp\":\"2022-04-15T22:26:37Z\",\"query_name\":\"tk2-209-14006.vs.sakura.ne.jp.\",\"query_type\":\"A\",\"query_class\":\"IN\",\"rcode\":\"NOERROR\",\"answers\":[{\"Rdata\":\"160.16.66.10\",\"Type\":\"A\",\"Class\":\"IN\"}],\"srcaddr\":\"172.31.84.43\",\"srcport\":\"50231\",\"transport\":\"UDP\",\"srcids\":{\"instance\":\"i-0646c0435554cc5ed\"}}", "@timestamp": "2022-04-15T22:27:49Z", "cloud.provider": "aws", "cloud.account.id": "12345", "cloud.region": "us-east-1", "aws.firehose.arn": "arn:aws:firehose:us-east-1:12345:deliverystream/route53-resolver-logs", "aws.firehose.request_id": "3d919d79-69c0-48b7-aa63-85d2f886a582", "aws.kinesis.type": "deliverystream", "aws.kinesis.name": "route53-resolver-logs", "aws.firehose.parameters.X-Found-Cluster": "ff0b7f06475245199add23784d445d3e", "aws.firehose.parameters.es_datastream_name": "logs-aws.route53_resolver-default", "data_stream.type": "logs", "data_stream.dataset": "aws.route53_resolver", "data_stream.namespace": "default" } }
Change Firehose parameter name to es_datastream_name. Changes the Firehose parameter name for users to specify a data stream name/index name to be only es_datastream_name
. Using an index is not recommended and should not be exposed in the parameter name.
Adds support for Firehose GZIP content encoding. When configuring Firehose delivery stream, user can choose to uses the content encoding to compress the body of a request before sending the request to the destination.
Don’t check the upgrade rules when re-enabling a terminated stateless resource. Stop enforcing upgrade rules when re-enabling stateless resources. For example, allow APM to be re-enabled on 8.2 if it was disabled on 7.14
Remove CSV maxSizeBytes whitelist cap for 7.15+. Allow xpack.reporting.csv.maxSizeBytes
whitelisting to exceed 50MB for cluster versions 7.15+, since it is chunked now.
Allow configuring Crawler content extraction settings. In version 8.3, the crawler in Enterprise Search adds new settings related to content extraction.
Warning when keystore entry is suspected to be invalid. In order to prevent invalid entries to the keystore that might cause all future plan changes to fail, we’ve added a list of well known keys that are expected to work, and validates the user-entered keystore entries against this list.
In case a key is not on the list of well known keys, the UI now issues a warning, provides some extra details on how secure settings work, and also asks the user to confirm that the setting might prevent future plan changes and may put the availability of their clusters at risk.
Reject requests to restart stopped deployment resources not running the same major stack version. Block requests to restart stopped stateless resources when they are not configured with the same major stack version as the Elasticsearch resource.
Beats upgrade to 7.17.1. Filebeat and Metricbeat shipping logs and metrics to the logging-and-metrics
cluster in Elastic Cloud Enterprise are upgraded from 7.12 to 7.17.
Set the region when creating a dedicated monitoring deployment. Pre-select the correct region when creating a dedicated monitoring deployment
Fix structured logging exceptions to comply with ECS. Changes the structured logging format to be Elastic Common Schema (ECS) compliant. Changes exception
to error
and class_name
to type
.
Bug fixes
editChange SSO realms to start at order 101, after user settings realms. Elasticsearch Service now uses realm orders above 100 for SSO realms to avoid conflict with any realms defined in user settings.
Show hourly rate instead of total usage in hourly rate tile. Fixes the value shown in the hourly rate tile of the usage page for trial users.
Fixed Summary sidebar. When editing a deployment, the summary sidebar no longer gets squashed when scrolling down the page.
Added more detail when instance overrides are reset. The calculate incremental elasticsearch change step was omitting the reason why the instance resize is done, when dealing with instance capacity overrides. This is fixed now and the reason is included in the detail step view.
Reset instance capacity overrides. Instance capacity overrides were not reset during the next plan change. Now, during the next plan change, the instance capacity overrides are removed and the initial capacity is used.
Fixed overflow problem when displaying summary of resized instances. Fixes the negative numbers that were sometimes shown in the overview of the resize step due to an overflow bug. This occurred when calculating the capacity of an instance in human readable fashion.
Don’t count stopped deployments on the platform region overview page. The healthy/unhealthy deployment counts on the platform overview page now exclude stopped deployments.
Only show the Enterprise Search read-only warning if Enterprise Search is enabled. During upgrades, if Enterprise Search was not enabled, sometimes a warning would be displayed about it being read-only.
Fix Proxy panic on error with empty request body Fixes Proxy panic
on retry of url.Error
with empty request body.
Deprecations
editChange useDiskThreshold to hidden property and don’t parse or serialize. The formerly deprecated use_disk_threshold
field in ElasticsearchSystemSettings
will no longer be returned in API responses and any value attempted written is ignored.
Update legacy region cipher suite. Updated the legacy region cipher suites to intermediate ciphers + Windows 11 client compatible cipher suites. Read more about this change to the supported ciphers list.
Docs
editAdd docs example for simplified deployment creation. We’ve added a new example to the Elasticsearch Service API docs showing how to create a deployment using default values based on a deployment template specified in the API request.
On this page