- 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 - 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
Cross-region and cross-provider support, warm and cold data tiers, and more
editCross-region and cross-provider support, warm and cold data tiers, and more
editRelease highlights
editAdded support for cross-cluster search (CCS) and replication (CCR) across-regions and cloud providers. Break down data silos by searching across remote clusters regardless of where they are deployed. Increase data redundancy by storing copies of your data with CCR to ensure, in the event of a regional failure, a secondary, remote cluster can be used as a hot backup. Reduce search latency by storing copies of your data in a location nearer to the user. Check Enable cross-cluster search and cross-cluster replication.
Add an optional warm and cold tier in all 3+1 deployments. All built-in deployment templates have been extended to include an optional warm and cold data tier. You can now enable a warm tier on any type of deployment, and for deployments on Elastic Stack version 7.10 and higher, you can take advantage of snapshot-backed indices in a dedicated cold data tier and store much more data at the same cost. Check Data tiers.
Enhancements
editSupport for the Elasticsearch node.roles
configuration in the CRUD deployments API. When creating or updating a deployment on Elastic Stack version 7.10 and higher, users can now configure the Elasticsearch node roles by using the node_roles
field instead of the node_type
field in the ElasticsearchClusterTopologyElement.
Better logging on EnsureRepository. Improves the error reporting for failures that occur while creating snapshot repositories.
Prevent plans termination and creation of resources of the same kind. Adds a validation to check that resources of the same kind are not terminated and added to a single plan. This can happen if the refId
of a resource is changed, which would cause issues.
Better explanation message when allocators are vacated. Improves the error message Moving nodes off allocator
by adding additional context.
Respect kibana authc selector user prefs. When configuring Kibana in a deployment, users are now able to set xpack.security.authc.selector.enabled: false
without being overwritten by internal Cloud SSO settings.
Do not remove zero-sized tiers from create request. Adds zero-sized tiers to the API Create Deployment request, to support having optional data tiers available in all hardware profiles.
Add Workplace Search thumbnail enable/disable configuration. Adds a workplace_search.content_source.sync.thumbnails.enabled
configuration for Enterprise Search, which determines whether thumbnails are generated for synced documents.
Added support for new generation storage-optimized AWS D3 instances. The new generation instances offer better performance with a reduced price per GB of storage. The new hardware will replace the AWS D2 machine and is used for both warm and cold data nodes, allowing you to automatically move data that is less frequently searched to more cost-effective hardware. We currently offer D3 in the following regions: Ireland (EU West-1), North Virginia (US East-1), Ohio (US East-2), and Oregon (US West-2).
Bug fixes
editHandle terminated deployments and missing templates on Edit screen. Editing terminated or certain system deployments should no longer throw an error.
Apply correct timestamps to downloaded bundles. Fixes a bug that could cause instances to bootloop during rolling plans if a cluster is configured with user bundles.
Use recommended JVM heap allocation for dedicated masters. Fixes an issue where dedicated masters can go out of memory due to over-allocated heap size.
Use smaller Elasticsearch heap when Filebeat and Metricbeat are running. Fixes a bug where small, master-only instances and tiebreaker instances have memory swapping issues when logs and metrics are enabled on Elasticsearch clusters.
Make some Elasticsearch domain fields optional. Fixes a bug that might cause plans to fail during the "Migrating shard data" step.
Optimize ML cluster settings. Some plans could fail if an ML node is offline, even if the failsafe
flag is set. This change lets plans continue if the ‘Optimize ML Cluster settings’ step fails and the failsafe
flag is set.
Strip hop-by-hop headers. Removes the hop-by-hop headers from both request and response, and removes any header specified in the Connection
header.
Log metrics UI errors, Kibana and 24 hour logs.
- Fixes error messages for Logs and metrics panel.
- Fixes the issue where 24 hour logs do not show when logs monitoring is not enabled.
- Fixes the error when there is no Kibana option.
Deprecations
editHot-Warm Architecture deployment template is being deprecated. Now that all deployment templates include an optional warm tier on on any deployment, the dedicated Hot-Warm Architecture is deprecated and no longer available in the user console when creating new deployments. Existing deployments created with the Hot-Warm template are not affected and will also have access to the cold data tier when using a compatible 7.10+ version.
Add Workplace Search content source limit configurations. The following configurations are deprecated and will be removed in Elastic Stack version 8.0.0:
-
workplace_search.custom_api_source.document_size.limit
-
workplace_search.custom_api_source.total_fields.limit
Use the following configurations instead:
-
workplace_search.content_source.document_size.limit
-
workplace_search.content_source.total_fields.limit
The cross-cluster search deployment template is now deprecated. The cross-cluster search deployment template has been removed from the Elasticsearch Service user console. You no longer need to use the dedicated cross-cluster template to search across deployments. Instead, you can now use any template to configure remote clusters and search across them when using stack version 6.7 or above. Existing deployments created using this template are not affected, but they are required to migrate to another template before upgrading to the next 8.0 major version.
Docs
editRemove basicAuth from the ESS API documentation. Updated the API documentation to remove basic authentication from supported authentication mechanisms for Elastic Cloud.
Add SAML to the ESS API documentation. Support for Elastic Stack version 7.11 includes a new SAML API.