Clarify product environment minimum for ECH (elastic#3307)

This is to address
elastic/support-tech-lead#1655 (internal
ticket).

## Preview - Before merge

-
[deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3307/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components)
-
[deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3307/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning)
-
[deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3307/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring)

## Preview - After merge

*
https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning
*
https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components
*
https://www.elastic.co/docs/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring

---------

Co-authored-by: Vlada Chirmicci <[email protected]>

Author: 2 people

deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md

@@ -34,7 +34,7 @@ For trials, larger sizes are not available until you [add a credit card](../../c
 Currently, half the memory is assigned to the JVM heap (a bit less when monitoring is activated). For example, on a 32 GB cluster, 16 GB are allotted to heap. The disk-to-RAM ratio currently is 1:24, meaning that you get 24 GB of storage space for each 1 GB of RAM. All clusters are backed by SSD drives.
 
 ::::{tip}
-For production systems, we recommend not using less than 4 GB of RAM for your cluster, which assigns 2 GB to the JVM heap.
+For production systems, each {{es}} instance in your cluster should have at least 4 GB of RAM, which assigns 2 GB to the JVM heap. Review [Minimum size recommendations for production use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details.
 ::::
 
 
@@ -43,7 +43,7 @@ The CPU resources assigned to a cluster are relative to the size of your cluster
 If you don’t want to autoscale your deployment, you can manually increase or decrease capacity by adjusting the size of hot, warm, cold, and frozen [data tiers](../../../manage-data/lifecycle/data-tiers.md) nodes. For example, you might want to add warm tier nodes if you have time series data that is accessed less frequently and rarely needs to be updated. Alternatively, you might need cold tier nodes if you have time series data that is accessed occasionally and not normally updated. For clusters that have six or more {{es}} nodes, dedicated master-eligible nodes are introduced. When your cluster grows, it becomes important to consider separating dedicated master-eligible nodes from dedicated data nodes.
 
 ::::{tip}
-We recommend using at least 4GB RAM for dedicated master nodes.
+For clusters with dedicated master nodes, we recommend using at least 4 GB of RAM for each dedicated master node. Review [Minimum size recommendations for production use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details.
 ::::
 
 

deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md

@@ -66,3 +66,12 @@ Scaling with {{ecloud}} is easy:
 * Or, if you prefer manual control, log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment, select *Edit*, and either increase the number of zones or the size per zone.
 
 The recommendation is to scale up the resources within a single zone until the cluster can take the full load (add some buffer to be prepared for a peak of requests), then scale out by adding additional zones depending on your requirements: two zones for High Availability, three zones for Fault Tolerance. 
+
+## Minimum size recommendations for production use [ec-minimum-recommendations]
+
+To ensure optimal performance and cluster stability in your production environment, we recommend adhering to the following minimum size guidelines. Deviating from these recommendations may lead to performance issues and cluster instability. For an enhanced user experience, consider planning your deployment capacity above these minimum recommendations, and adjust sizing based on your specific use case.
+
+* **{{es}} nodes / instances**: For production systems, we recommend that each {{es}} node / instance in your cluster has at least 4 GB of RAM.
+* **Clusters with logs and monitoring enabled**: Enabling logs and monitoring requires additional resources. For production systems with these features enabled, we recommend allocating at least 4 GB of RAM per {{es}} node / instance.
+* **Clusters with dedicated master nodes**: For clusters with dedicated master nodes, we advise using at least 4 GB of RAM for each dedicated master node.
+

deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md

@@ -41,7 +41,7 @@ For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/aut
 ## Before you begin [logging-and-monitoring-limitations]
 
 * Some limitations apply when you use monitoring on ECH or ECE. To learn more, check the monitoring [restrictions and limitations](#restrictions-monitoring).
-* Enabling logs and monitoring consumes extra resources on a deployment. For production systems, we recommend sizing deployments with logs and monitoring enabled to at least 4 GB of RAM on each {{es}} instance.
+* Enabling logs and monitoring requires additional resources. For production systems where these features are enabled, we recommend allocating at least 4 GB of RAM per {{es}} instance. Review [Minimum size recommendations for production use](../../deploy/elastic-cloud/elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details.
 
 ## Monitoring for production use [logging-and-monitoring-production]