Support for new hardware profiles are continuously added to provide better price-performance on our Cloud platform.
With the release of the hardware profile migration capability, you now have the flexibility to switch between hardware profiles on your existing deployment. You can see the current hardware profile on each deployment’s Overview page, have the ability to edit the profile, and select a new one. This allows you to take advantage of more efficient hardware available on cloud providers, like Graviton2-based instances on AWS, N2 machines on GCP, or Edsv4, Ddv4, or Fsv2 VMs on Azure, with the added benefit of simplifying your migration process.
First, click the ‘Edit’ link next to the hardware profile name:
Once complete, a new flyout will appear allowing you to select and compare the hardware specifications between the deployment’s current hardware profile and any available alternatives.
After reviewing and confirming the resource allocation differences between the current and new hardware profile, click ‘Update.’ Now, you can follow the updates to your cluster through the deployment’s Activity page.
Choosing a new hardware profile
When choosing a new hardware profile, it’s important to consider changing the hardware profile types that optimize for different usage patterns. Most often users will benefit by upgrading to a newer hardware profile in the same lineage.
Using aws-io-optimized or aws-io-optimized-v2? Upgrading to aws-io-optimized-v3 will usually provide better performance at a more cost-effective price.
The same is true for users moving from azure-io-optimized or azure-io-optimized-v2 to azure-io-optimized-v3, which is now available directly in managing your deployment.
Similarly, moving from gcp-compute-optimized-v2 to gcp-cpu-optimized will provide an improved experience as you can migrate from N1 to N2 instances for better performance at a lower cost.
Over time, Elastic will continue to add new and improved hardware profile versions that allow you to optimize for both cost and performance.
Get started today with Elastic Cloud
The release and timing of any features or functionality described in this post remain at Elastic's sole discretion. Any features or functionality not currently available may not be delivered on time or at all.