Google Axion instances now available on Elastic Cloud Hosted

At Elastic, we are always focused on improving performance and cost efficiency for our customers running observability, security, and search workloads on Elastic Cloud Hosted. We are excited to introduce a new CPU-optimized (Arm) hardware profile powered by Axion — Google’s custom-designed, Arm-based processors.

This new Arm-based hardware profile brings the next generation of Google Cloud compute to Elastic Cloud Hosted.

The CPU-optimized (Arm) hardware profile delivers up to 25% better price-performance compared to the previous CPU-optimized generation, making it ideal for CPU-bound, indexing-heavy, and query-intensive workloads.

Customers benefit from improved compute efficiency, faster data processing, and more cost-effective scaling across search, observability, and security workloads — all without changing how they build or operate on Elastic Cloud Hosted.

This hardware profile is available in select Google Cloud regions. For the most up-to-date list of supported regions, refer to our regional availability documentation.

1. In the Elastic Cloud console, start creating a new deployment by selecting a solution view (Elasticsearch, Elastic Observability, or Elastic Security) for your deployment and then select Google Cloud as your cloud provider.

2. When choosing the hardware profile, select CPU-optimized (Arm). More information on our hardware profiles and configurations can be found in our documentation.

3. Once selected, continue with your usual configuration steps and create the deployment. 

Elastic Cloud will automatically provision the deployment powered by Google Axion (Arm) instances.

1. From the Elastic Cloud console, click on an existing deployment that has been created. 

2. On the deployment overview page next to your current hardware profile, select Edit.

3. Select the CPU-optimized (Arm) hardware profile. 

4. Preview the changes for the new hardware profile. 

5. Click Update, then confirm the changes to migrate to the new hardware profile. 

That’s it! Visit our documentation for more details.