- 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
- March 25, 2025
- Enhancements and bug fixes - March 2025
- 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
editFeedback link to the Help menu. Added a Give feedback
link to the Cloud console header in the Help menu. The link opens a feedback page in a new tab.
Force enroll on container restart. Introduced ephemeral Hosted Agent on container restart.
Enhancements
editGCP region Seoul (asia-northeast3). Elasticsearch Service is now available in the GCP region Seoul (asia-northeast3). You can select the new region when you create new deployments.
Shorten Azure private link endpoint name. Improves the handling of long Azure Private Link Endpoint names. With this release Azure Private Link traffic filters work regardless of the length of their endpoint names.
Make EnsureStorageResources step conditional. The step Preparing to store snapshots will run only when needed.
Consider allocator status when terminating. Plans that terminate deployments will no longer stall out during the step Waiting until instances are terminated if any nodes are on disconnected allocators.
Add support and docs for Manager ephemeral tasks configuration. Adds support and docs for:
-
xpack.task_manager.ephemeral_tasks.enabled
Kibana Task Manager configuration -
xpack.task_manager.ephemeral_tasks.request_capacity
Kibana Task Manager configuration -
xpack.alerting.maxEphemeralActionsPerAlert
Kibana Alerting configuration
Rework conditional logic for SuspendSnapshotting. The step Disabling snapshots will no longer run during plans that aren’t stopping nodes. If it fails, the plan is still allowed to continue in some cases.
Include chain status in TLS endpoints responses. Make GET /api/v1/platform/configuration/security/tls/{service_name}
responses include a status JSON object with information on the time to life of the service_name
certification chain. Check https://www.elastic.co/guide/en/cloud-enterprise/current/get-tls-certificate.html.
Increase APM and Fleet free tier to 1GB RAM. We have recently added Fleet Server to the APM component and, as part of that change, we are increasing the free tier from 512MB to 1GB to better support both services. We will also be updating the deployment templates to set the initial size of the APM and Fleet component to 1GB by default. If you have an existing deployment and are using the APM and Fleet free tier, you can scale it up to 1GB with no additional cost.
Add stricter validation to create or update deployment templates. When creating or updating a Deployment template, if it specifies node_roles
in the Elasticsearch plan, the template must contain all resource types and all Elasticsearch tiers.
Disable unused Enterprise Search resources. The Enterprise Search component is enabled by default for all deployment templates (with the initial size set to our free tier) so that you can test and use it without having to pay. If Enterprise Search is unused for 14 days (30 days in GovCloud), it will be disabled automatically. Once disabled, you can manually scale it up again at any time.
Bug fixes
editCTS - Gracefully handle returning keys of non-existent object. The CTS framework implements some JSON-parsing utility methods. One of them, GetKeys
returns the keys for a JSON object. This method causes a panic
if the JSON object itself is non-existent. This PR fixes this panic
by checking for the existence of the JSON object first. If it isn’t found, it returns an empty slice of keys.
Apply enterprise license during 7.8.1+ upgrades. Fixes a bug which causes clusters to not have access to new enterprise features immediately while upgrading to 7.8.1 or higher (from version 7.8.0 or lower).
Hide terminate button for Kibana. Removes a misleading Terminate
button that users couldn’t click.
Add breadcrumbs to getting started page. Adds header breadcrumbs to the Getting started page.
Port publisher to always update the znode after the first probe. Fixes a bug in the instance liveness probe when the allocator restarts, and the instance becomes unhealthy when the allocator is stopped.
Correctly count RAM-hours. Fixes undercounting of RAM-hours usage by the featureusage
CTS task.
Validate that there is only one resource for each type. Makes sure that it is not possible to create two resources of the same type in the same deployment (for example two Elasticsearch clusters), as this is not supported.
Deprecations
editRemove firmographics fields from marketplace sign in. Removes these fields from marketplace sign in:
- Industry
- Website
- Number of employees
- Country - gets inferred by Marketo/IPstack
- State - gets inferred by Marketo/IPstack
Docs
editOn this page