You may have a resource limitation that's interfering with getting all of those nodes created.
After running kubectl apply you can check the status of your deployment like this:
kubectl get elasticsearch(replaceelasticsearchwith the name of the pods you're looking for)- If the output of that command stays in the ApplyingChanges phase (never moving to Ready), run
kubectl get pods - If the list of pods provided indicates one or more pods in a "pending" status, run
kubectl describe pod <name of pod you want to check>(for example,kubectl describe pod quickstart-es-all-roles-2) and look for warnings, probably due to FailedScheduling. The message associated with the warning may indicate issues about insufficient memory for starting. - You may need to add one or more nodes to the EKS cluster, or reduce the resource utilization in the podTemplate section of the manifest.