# ElasticSearch AWS Setup - Nodes and LoadBalancers

**URL:** <https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104>\
**Category:** Elasticsearch\
**Created:** [January 25, 2018, 6:58pm UTC](https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104 "2018-01-25T18:58:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [January 25, 2018, 6:58pm UTC](https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104/1 "2018-01-25T18:58:12Z")

</div>

Am trying to setup ES on AWS using the following configuration. Wanted to run this by the community to see if I'm doing the right thing. I have approximately 1 million documents to index.  
3 Master Only Nodes  
2 Data Only Nodes  
1 Cooridinating Node

Question:

- Does this setup look correct from performance?

- How do I configure the Elastic Load Balancer? IF there is a 1 Coordinating Node, does that mean i associate only this Node to the ELB? Which obviously doesnt make sense as ELBs need to have multiple endpoints to be truly load balancing. So does that mean I need to also spin up 2-3 Coordinating Nodes at the minimum and attach those to the ELB?

---

<div class="post-metadata">

**Author:** ![loren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loren/32/44942_2.png) [@loren](https://discuss.elastic.co/u/loren)\
**Post date:** [January 25, 2018, 7:56pm UTC](https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104/2 "2018-01-25T19:56:50Z")

</div>

I would suggest starting with 2 master-eligible data nodes, 1 replica, 1 shard, and have the ELB point at both.

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [January 25, 2018, 8:07pm UTC](https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104/3 "2018-01-25T20:07:19Z")

</div>

Edit 🙂

Thanks! Woudl such a configuration (3 master + data) be able to handle querying across 1-2 million documents?

---

<div class="post-metadata">

**Author:** ![loren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loren/32/44942_2.png) [@loren](https://discuss.elastic.co/u/loren)\
**Post date:** [January 25, 2018, 8:45pm UTC](https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104/4 "2018-01-25T20:45:54Z")

</div>

I was actually suggesting 2 nodes, not 3, since 1-2m docs doesn't seem like a lot. I only suggested 2 instead of 1 because it sounded like you wanted HA via the ELB. But it all depends on your document size and how you are analyzing/indexing fields, so really there's only one way to find out. Good luck!

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [January 25, 2018, 8:47pm UTC](https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104/5 "2018-01-25T20:47:06Z")

</div>

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 22, 2018, 8:47pm UTC](https://discuss.elastic.co/t/elasticsearch-aws-setup-nodes-and-loadbalancers/117104/6 "2018-02-22T20:47:20Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
