Frozen data tier and moreedit

Release highlightsedit

The frozen data tier is now available in Elasticsearch Service

animated graphic highlighting the new frozen tier availability

A frozen data tier, powered by searchable snapshots, allows you to store large volumes of less frequently searched data in object storage including Amazon S3, Google Cloud Storage, and Microsoft Azure Blob Storage. The new data tier is designed to be so cost-effective you’ll never need to delete data. It is fully integrated with autoscaling, allowing you to seamlessly scale to store massive amounts of data. Learn more…​

Enhancementsedit

Display frozen tier blob storage. Frozen tier storage is now displayed on the UI as the amount of searchable storage available (a multiplier of 1600x the RAM size).

Display changes in activity view by topology element ID if present. Configuration changes will now reference Elasticsearch topology elements by ID instead of their underlying hardware configuration, where possible.

Update SLM health reporting. When Snapshot Lifecycle Management (SLM) is in use, snapshots are now reported as unhealthy only if SLM is suspended while there is no ongoing plan activity.

Remove polling from snapshots. Removes polling from the snapshots page to reduce load on the cluster.

Bug fixesedit

Fix App Search to Enterprise Search upgrades. Fixed a bug that would prevent users from migrating App Search deployments to Enterprise Search for versions 7.10.0 and above.

Show data and master pricing in architecture component. Updated the pricing page summary to show the price for data and master nodes, and to show storage rather than RAM in the Architecture key.

Increase size of training button. Updated the size of the training button to match the size of other, similar buttons on the Elastic Cloud portal page.

Only ignore allocation.require shard routing rules. Ensure that data tier shard routing allocation preferences are retained when restoring a deployment from snapshots, or restoring a snapshot from another deployment.

Use aliased endpoints for logs and metrics links. Fixed an issue where the links to logs and metrics single-sign on did not work.

Check node_roles for voting_only designation. Fixed a bug that could lead to quorum loss for Elasticsearch clusters version 7.11 or higher that are in exactly 2 availability zones (plus a tiebreaker) when running a plan to switch to dedicated masters.

Stop trying to query non-existent App Search. The Deployment Overview tab should no longer display an error if App Search is available but not enabled.

Adjust region query in the UI. Adjusted the UI query for selecting deployments within the same region to be less flexible.

TCP RST cleanup Fixed a bug where an improperly closed connection to the transport passthrough proxy would result in an idle backend connection remaining open.

Docsedit

Add ToC to ESS API reference main page. For better navigation, a table of contents has been added to the API reference documentation.

Add Python scenario to the docs. Added a usage scenario for ingesting, searching, and updating data in a Python application.

Update docs with new Support page URL. All documentation links have been updated to reflect the new location of the Support site at https://cloud.elastic.co/support (formerly https://cloud.elastic.co/help).

Update AWS hardware reference We updated the Elasticsearch Service default provider instance configurations documentation to reflect our current usage of m5d and r5d instances, removing stale references to m5 and r4 instances.