Elastic Cloud on Azure gets a speed boost: Compute-optimized instances on Azure Cobalt ARM

The new hardware profile is available in Elastic Cloud Console and iIt uses the Dpldsv6 VM series which is  Microsoft's Cobalt-based ARM instances with NVMe direct-attach storage. 

For Elasticsearch, the local NVMe SSD disk is worth calling out separately. Local NVMe storage delivers improved random read performance versus  remote-attached premium storage.

Not every Elasticsearch deployment is bottlenecked on CPU. The CPU Optimized (ARM) profile offers the greatest gains for compute-bound workloads, but customers running storage-heavy or memory-intensive workloads may also see improvements from the updated I/O and memory characteristics of the underlying instances. But if you see any of the following, the compute-optimized ARM profile is worth testing:

• You consistently see high CPU utilization during peak query or indexing windows

• You're running dense vector search (kNN) or hybrid search with heavy reranking

• You run frequent aggregations across large date ranges

New deployment via the Azure Portal:
Log in to the Azure Portal, search for "Elasticsearch," and select the Marketplace offering that fits your use case (e.g., Search, Observability, or Security). Once the deployment is created, you can click on “Go to Resource” and choose Advanced Settings “Manage changes in Elastic Cloud”.  This will take you to the Elastic Cloud Console where you can edit the Hardware Profile and select the new ‘CPU Optimized (ARM) profile.

Via the Elastic Cloud Console:
Log in to Elastic Cloud and create a deployment or migrate an existing one to the new hardware profile. During the configuration process, under hardware profiles, the ‘Storage Optimized’ hardware profile is the default.  Select the new "CPU-optimized(ARM)" profile, which uses the Dpldsv6 VM series to utilize this new hardware profile.

The Cobalt ARM compute-optimized hardware profile is available for Elastic Cloud Hosted deployments in the following Azure regions:

• New South Wales (australiaeast)

• Netherlands (westeurope)

• Washington (westus2)

• Iowa (centralus)

• Toronto (canadacentral)

• Texas (southcentralus)

• Paris (francecentral)

Additional regions will follow over the coming months as capacity comes online. Check the Azure configuration reference for the current region list.