Update cloud-instance-recommendations.md

docs/deployments/deployment-preparation/cloud-instance-recommendations.md

@@ -12,17 +12,18 @@ other instance types as long as they fulfill the system requirements.
 Simplyblock can work with local instance storage (local NVMe devices) and Amazon EBS volumes. For performance reasons,
 Amazon EBS is not recommended for high-performance clusters.
 
-!!! critical
+!!! important
     If local NVMe devices are chosen, make sure that the nodes in the cluster are provisioned into a placement group of type
-    _Spread_!
+    _Spread_! Otherwise there is no guarantee that multiple storage nodes won't be located in the same failure domain. 
 
 Generally, with AWS, there are three considerations when selecting virtual machine types:
 
 - Minimum requirements of vCPU and RAM
 - Locally attached NVMe devices
 - Network performance (dedicated and "up to")
 
-Based on those criteria, simplyblock commonly recommends the following virtual machine types for storage nodes:
+Based on those criteria, simplyblock commonly recommends the following virtual machine types for storage nodes
+***in disaggregated clusters***:
 
 | VM Type         | vCPU(s) | RAM    | Locally Attached Storage | Network Performance |
 |-----------------|---------|--------|--------------------------|---------------------|
@@ -35,6 +36,10 @@ Based on those criteria, simplyblock commonly recommends the following virtual m
 | _i4i.8xlarge_   | 32      | 256 GB | 2x 3750 GB               | 18.75 GBit/s        |
 | _i4i.12xlarge_  | 48      | 384 GB | 3x 3750 GB               | 28.12 GBit/s        |
 
+For hyper-converged AWS EC2-based Kubernetes workers (EKS, k3s or other), any instance with a local SSD can be chosen.
+
+Keep the [minimum system requirements](./hardware-requirements.md)in mind. At least 8 vCPUs are required for simplyblock. 
+
 ## Google Compute Engine Recommendations
 
 !!! critical