ok, some background. with AWS as you aware you have the ability to create multiple subnets and then you also have 1-3 AZ's (availability zones, ak different physical locations).
With EKS you create a cluster (which is managed and then you add worker nodes, during the creation of the worker nodes you specify the subnet, so you can basically for a 3 subnet per az and 2 az's create 6 worker nodes, one on each h of the 6 subnets. You then add labels to the workers,
when you now deploy your pod you can use/specify a nodeSelector. which pushes the pod onto select nodes or az's or both.
For this exercise I will create ay number of nodes to match the desired / best design / layout.
think best plan might be to start there... the cluster/design, we then match the required yaml to deploy the Elastic stack onto it, and then decide/define how/where we want Kibana deployed, For us everything needs to be HA, implying Kibana also, so I'd have a question when we get there, how to deploy multiple Kibana's and have them share their configuration/dashboard layout.
happy to be ginea pig here to get this designed/laid out for others to use/abuse.
ps I'll go and close the other thread.