# ES in AWS EC2

**URL:** <https://discuss.elastic.co/t/es-in-aws-ec2/33156>\
**Category:** Elasticsearch\
**Created:** [October 28, 2015, 2:48pm UTC](https://discuss.elastic.co/t/es-in-aws-ec2/33156 "2015-10-28T14:48:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bluethundr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bluethundr/32/409_2.png) [@bluethundr](https://discuss.elastic.co/u/bluethundr)\
**Post date:** [October 28, 2015, 2:48pm UTC](https://discuss.elastic.co/t/es-in-aws-ec2/33156/1 "2015-10-28T14:48:46Z")

</div>

We have one of the requirement to host ES in AWS ( Euro Zone). Index size will be 100 GB. What would be the ideal instance sizes in AWS?

We'll also be investigating AWS ES as a service. However we'll still need a recommendation on this to compare.

Thanks!!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 28, 2015, 11:38pm UTC](https://discuss.elastic.co/t/es-in-aws-ec2/33156/2 "2015-10-28T23:38:18Z")

</div>

What sort of data?  
Query/indexing rate and requirements?  
What sort of queries?  
What version?

---

<div class="post-metadata">

**Author:** ![bluethundr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bluethundr/32/409_2.png) [@bluethundr](https://discuss.elastic.co/u/bluethundr)\
**Post date:** [November 1, 2015, 7:10pm UTC](https://discuss.elastic.co/t/es-in-aws-ec2/33156/3 "2015-11-01T19:10:48Z")

</div>

> [@warkolm](#):
>
> What sort of data?  
> Query/indexing rate and requirements?  
> What sort of queries?  
> What version?

Warkolm,

I don't have any information yet other than what I just told you, unfortunately. All I know is that the index size will be 100GB. Are there any general guidelines one can use for sizing elasticsearch clusters on AWS?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 1, 2015, 7:31pm UTC](https://discuss.elastic.co/t/es-in-aws-ec2/33156/4 "2015-11-01T19:31:13Z")

</div>

The query and indexing rate will have a significant impact on the cluster size and specification, as will the types of queries used and the latency requirements. Just the size of the indexed data is generally not sufficient for sizing. Also, does the 100GB of indexed data include replicas or not?

---

<div class="post-metadata">

**Author:** ![bluethundr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bluethundr/32/409_2.png) [@bluethundr](https://discuss.elastic.co/u/bluethundr)\
**Post date:** [November 1, 2015, 8:33pm UTC](https://discuss.elastic.co/t/es-in-aws-ec2/33156/5 "2015-11-01T20:33:46Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> The query and indexing rate will have a significant impact on the cluster size and specification, as will the types of queries used and the latency requirements. Just the size of the indexed data is generally not sufficient for sizing. Also, does the 100GB of indexed data include replicas or not?

Ok, thanks. I'll see if I can find that out. This request was forwarded to me by a manager from the client. Who may or may not know that information. But I'll talk to them and see what I can learn about their proposed environment.

I understand they are planning a 3 node cluster. So we'd probably want to store replicas of the entire data set on each of the 3 nodes. So by that alone we'd probably want a 300GB data partition on each node stored on EBS?

---

<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:** [July 5, 2017, 11:41pm UTC](https://discuss.elastic.co/t/es-in-aws-ec2/33156/6 "2017-07-05T23:41:26Z")

</div>


