# Hardware profiles for Hot/Warm tiers

**URL:** <https://discuss.elastic.co/t/hardware-profiles-for-hot-warm-tiers/353582>\
**Category:** Elasticsearch\
**Created:** [February 19, 2024, 11:40am UTC](https://discuss.elastic.co/t/hardware-profiles-for-hot-warm-tiers/353582 "2024-02-19T11:40:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![intrepid1](https://avatars.discourse-cdn.com/v4/letter/i/dbc845/32.png) [@intrepid1](https://discuss.elastic.co/u/intrepid1)\
**Post date:** [February 19, 2024, 11:40am UTC](https://discuss.elastic.co/t/hardware-profiles-for-hot-warm-tiers/353582/1 "2024-02-19T11:40:53Z")

</div>

Hi there,

We are in the process of moving our on-premise logging cluster to AWS on EC2 and would like to use a hot/warm architecture. The aim is to place the data on the hardware that is most suited to, allowing multiple use cases to be supported on the most pertinent hardware available. Another benefit is the reduce the overall hardware costs whilst still providing a service that meets our users expectations.

I have taken a look at the Elastic Cloud configuration tool as a starting point for hardware profiles and basing on a Dense Storage option. We have users that need their dashboards to load in a timely manner and also users that use Discover to search the logs.

Whereas the hot tier is based in i3 processors and SSD, the warm tier uses D3 with HDDs.

I wonder whether there are any users who have self managed clusters using hot/warm and indeed cold tiers and it would be interesting to hear what hardware profiles that they use.

I appreciate that things are different from use case to use case, but one can learn so much from the experiences of others.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [February 19, 2024, 7:10pm UTC](https://discuss.elastic.co/t/hardware-profiles-for-hot-warm-tiers/353582/2 "2024-02-19T19:10:54Z")

</div>

I would look at our profiles for Elastic Cloud... we consider them best practice and are a great place to start with if you are building your own clusters.

> **[VM configurations | Elasticsearch Service Documentation | Elastic](https://www.elastic.co/guide/en/cloud/current/ec_vm_configurations.html)**

> **[Elasticsearch Service AWS default provider instance configurations |...](https://www.elastic.co/guide/en/cloud/current/ec-default-aws-configurations.html)**

---

<div class="post-metadata">

**Author:** ![intrepid1](https://avatars.discourse-cdn.com/v4/letter/i/dbc845/32.png) [@intrepid1](https://discuss.elastic.co/u/intrepid1)\
**Post date:** [February 20, 2024, 9:01am UTC](https://discuss.elastic.co/t/hardware-profiles-for-hot-warm-tiers/353582/3 "2024-02-20T09:01:40Z")

</div>

Thank you.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 19, 2024, 9:02am UTC](https://discuss.elastic.co/t/hardware-profiles-for-hot-warm-tiers/353582/4 "2024-03-19T09:02:02Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.