- 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
New security setting, in-place configuration changes, new hardware support, and signup with Google released
editNew security setting, in-place configuration changes, new hardware support, and signup with Google released
editElasticsearch Service now supports additional features that let you do more with our hosted offering:
-
Support for new security setting. The
xpack.http.ssl.cipher_suites
setting is now enabled for Elasticsearch Service. This setting can be useful when using outgoing TLS traffic to external services with restrictive supported cipher suites. One example would be using Telegram from Watcher. -
In-place configuration changes. In-place changes for existing deployments substantially speed up configuration changes and are now the default for most operations that involve settings changes, upgrades, and deployment resizing. The benefits include:
- Reduced wait times
- Reduced chance of plan failures and improved platform stability
- Reduced data transfer charges from the cloud platform provider, proportional to the amount of data you manage in your deployment
The speed and reliability of in-place configuration changes comes from applying the changes to the existing instances of your deployment, such as the Elasticsearch nodes and Kibana instances, followed by a rolling restart. There is no downtime for highly available deployments with two or more availability zones, provided that deployments are sized to support their workloads.
Elasticsearch Service previously used only a grow-and-shrink approach for deployment changes. This approach adds new instances, migrates data from old instances to the new ones, and then shrinks the deployment by removing the old instances. Grow-and-shrink provides high availability during configuration changes even for single availability zones. The tradeoff is that changes frequently require replacing some or all of the deployment, triggering a potentially long-running data migration process for larger deployments.
When you change your deployment configuration, Elasticsearch Service will choose the right approach to apply the changes, using either the preferred in-place approach where possible or falling back to grow-and-shrink when necessary. Deployment changes that will continue to require a grow-and-shrink approach include:
- Configuration changes and upgrades to non-highly available deployments that use only one availability zone
- Changes to APM and Kibana instances
When applying changes to non-highly available deployments, the Elasticsearch Service Console now warns you that your deployment may suffer a temporary loss of availability. If loss of availability is not acceptable, make sure to use at least two availability zones, even if only temporarily. Keep in mind that production systems should never use only one availability zone.
The grow-and-shrink approach may still be used in some other scenarios, for example when the host that your deployment runs on has insufficient capacity to scale up an Elasticsearch cluster and needs to use capacity on another host.
-
New deployment templates to support AWS M5d and R5d hardware. AWS provides memory- and CPU-optimised machines with attached NVMe storage instead of GP2 which offers more performant hardware with better disk performance. In order to support the new hardware, you can now make use of updated AWS deployment templates. The new templates still use the same naming convention and replace components using R4 with R5d, and M5 with M5d.
What’s moving from R4 to R5d:
- Kibana
- APM
- Master nodes
- Memory-optimised data nodes
What’s moving from M5 to M5d:
- Coordinating nodes
- Machine learning nodes
- CPU-optimized data nodes
- App Search and Enterprise Search components
Prices for the new hardware are marginally higher. You can check the pricing calculator for exact prices.
New deployments will use the AWS M5d and R5d hardware by default. For existing deployments, there is currently no direct migration path, but you can make use of the new hardware by creating a new deployment and then restoring your data from a snapshot.
-
Social signup with Google. New users can now use social signup with Google, eliminating the need to verify email addresses or manage passwords when signing up for Elasticsearch Service.
How it works:
- Google social signup is available to all new Elastic Cloud trial and training users.
- GCP Marketplace and AWS Marketplace users still need to sign up with their email address and password just as before. We hope to offer social signup for marketplace users at a later date.
- GovCloud and Elasticsearch Service Private environments do not support social signup.
Breaking Changes
editThis version includes the following breaking changes:
-
Elasticsearch clusters provisioned prior to January 25th, 2019 have a CORS policy set at the proxy layer. This policy is now deprecated and we will be moving to a model that requires you to configure your own http module CORS policy. The
http.cors.*
settings are configurable as Elasticsearch user settings for all of your deployments.If your use case depends on the ability to receive CORS requests and you have an Elasticsearch cluster that was provisioned prior to January 25th 2019, you must manually apply the
http.cors.*
settings before the September 22 deadline, or you will potentially have an operational impact. -
The in-place configuration change improvements included in this release mean that single availability zone deployments will be temporarily unavailable while the change is applied. If availability is a concern, you should use two availability zones for your deployment, which requires no downtime and which ensures deployment availability during future configuration changes, upgrades, and hardware failures.
As a best practice for production setups, you should never run with a single availability zone if downtime is a concern.
Known Problems
edit- Traffic filters must not be enabled on monitoring clusters. If you are shipping your logs or metrics to a monitoring cluster, do not associate traffic filters with the Elasticsearch cluster you are sending the logs or metrics to. Since you cannot explicitly allow traffic from certain clusters currently, associating traffic filters with your monitoring cluster will result in clusters being blocked when sending data.
- A known bug in Elasticsearch affects clusters with versions 7.7.0 and 7.7.1 and can prevent you from making configuration changes. If this problem occurs, we recommend that you retry the configuration change. If retrying the change fails please contact Support. We also recommend that you to upgrade to version 7.8 or higher, where the problem has been addressed.
- Configurable limits in Enterprise Search are not supported on Cloud but will be in a future release.
Service release: June 17, 2020
On this page