# Elastic Cloud hardware profiles do not line up with documenation **URL:** \ **Category:** Elasticsearch\ **Created:** [February 18, 2022, 4:18am UTC](https://discuss.elastic.co/t/elastic-cloud-hardware-profiles-do-not-line-up-with-documenation/297564 "2022-02-18T04:18:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![JJK](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jjk/32/26684_2.png) [@JJK](https://discuss.elastic.co/u/JJK)\ **Post date:** [February 18, 2022, 4:18am UTC](https://discuss.elastic.co/t/elastic-cloud-hardware-profiles-do-not-line-up-with-documenation/297564/1 "2022-02-18T04:18:42Z")
I'm trying to create a new deployment. The linked help documentation mentions 3 options for hardware profiles: > **[What are hardware profiles? | Elasticsearch Service Documentation | Elastic](https://www.elastic.co/guide/en/cloud/current/ec-getting-started-profiles.html)** ``` I/O Optimized Computed Optimized Memory Optimized ``` Actual options given in Elastic cloud: ``` Storage Optimized Storage Optimized (Dense) General Purpose CPU Optimized ``` I would like to pick the option closest to I/O optimized, but I have no idea which one that might be. ---
**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 18, 2022, 6:12pm UTC](https://discuss.elastic.co/t/elastic-cloud-hardware-profiles-do-not-line-up-with-documenation/297564/2 "2022-02-18T18:12:33Z")
Hi @JJK Which Provider? What is your use case Search.. observability? Tell me a little bit and I'll help if I can. ---
**Author:** ![JJK](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jjk/32/26684_2.png) [@JJK](https://discuss.elastic.co/u/JJK)\ **Post date:** [February 18, 2022, 6:53pm UTC](https://discuss.elastic.co/t/elastic-cloud-hardware-profiles-do-not-line-up-with-documenation/297564/3 "2022-02-18T18:53:48Z")
Both Google Cloud (default) and Amazon Web Services show different hardware profiles then what is in the documentation. (Only Azure matches docs). I'm planning on using Amazon Web Services. See attached images. ![Screen Shot 2022-02-18 at 10.51.25 AM](https://us1.discourse-cdn.com/elastic/original/3X/3/c/3cf4825e8cf462fa5c81b80d3d3276cb555a2b3a.png) ![Screen Shot 2022-02-18 at 10.50.44 AM](https://us1.discourse-cdn.com/elastic/original/3X/a/5/a5e60ac7a4bb7fe458da1655dcba5fb598988cf3.png) ---
**Author:** ![JJK](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jjk/32/26684_2.png) [@JJK](https://discuss.elastic.co/u/JJK)\ **Post date:** [February 18, 2022, 7:06pm UTC](https://discuss.elastic.co/t/elastic-cloud-hardware-profiles-do-not-line-up-with-documenation/297564/4 "2022-02-18T19:06:27Z")
As far as use case: This is for a website where users add forms (just keyword/text fields, not docs) that get indexed (in near real time) and are stored indefinitely. These forms are then searched by the members of their organization. So there is a high search load, and near-real-time indexing. ---
**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, 2022, 1:37am UTC](https://discuss.elastic.co/t/elastic-cloud-hardware-profiles-do-not-line-up-with-documenation/297564/5 "2022-02-19T01:37:11Z")
Hi @JJK Yup the Docs are a bit Behind / mixed up for that top level selection there have been a lot of updates **the page you really want to look at is this page** **[here](https://www.elastic.co/guide/en/cloud/current/ec-aws-instance-configuration.html)** which should be up to date. I would probably look at the CPU Optimized (ARM) is your searches are complex etc, aggregation and perhaps smaller dataset you can go with Compute Optimized which give a Higher Ratio to CPU to RAM which makes searches and indexing fast but the amount of storage is a bit lower but still pretty substantial > CPU Optimized (ARM) > > aws.es.datahot.c6gd > > Suitable for ingestion use cases with 1-4 days of data available for fast access and for search use cases with indexing and querying workloads. Provides the most CPU resources per unit of RAM. ![Screen Shot 2022-02-18 at 5.31.37 PM](https://us1.discourse-cdn.com/elastic/original/3X/e/0/e07d7cf938092b6afe0f7f7ee00bb933a0e7f3c6.png) Pick a size and scale up / down if needed ![Screen Shot 2022-02-18 at 5.35.32 PM](https://us1.discourse-cdn.com/elastic/original/3X/c/0/c0318f74dd09f3ce7e5a1d7fc22c8fc0cac11e0b.png) ---
**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, 2022, 1:37am UTC](https://discuss.elastic.co/t/elastic-cloud-hardware-profiles-do-not-line-up-with-documenation/297564/6 "2022-03-19T01:37:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.