# Elasticsearch networking on AWS

**URL:** <https://discuss.elastic.co/t/elasticsearch-networking-on-aws/140236>\
**Category:** Elasticsearch\
**Created:** [July 17, 2018, 1:02am UTC](https://discuss.elastic.co/t/elasticsearch-networking-on-aws/140236 "2018-07-17T01:02:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![arisbanach](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@arisbanach](https://discuss.elastic.co/u/arisbanach)\
**Post date:** [July 17, 2018, 1:02am UTC](https://discuss.elastic.co/t/elasticsearch-networking-on-aws/140236/1 "2018-07-17T01:02:21Z")

</div>

I'm curious if there has been any discussion around the ideal network infrastructure setup for Elasticsearch running on EC2 instances on AWS. I set up a few clusters before using public EC2 instances that had been configured with Security Groups that only allowed traffic to and from the appropriate sources (e.g. from Logstash and the API server) and then have only one instance that was publicly accessible: the API server.

However, there are so many networking configuration options, and networking is not my greatest strength. Should Elasticsearch be in a private subnet and use a NAT Gateway? Should it be configured the way I mentioned I was doing it above? Some other way?

I know that, as with most software at this level, that it probably depends on your use case and you CAN configure it any way you want, but there surely must be some relatively ideal practice for most use cases, isn't there?

Any thoughts on this would be much appreciated.

---

<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:** [August 14, 2018, 1:02am UTC](https://discuss.elastic.co/t/elasticsearch-networking-on-aws/140236/2 "2018-08-14T01:02:28Z")

</div>

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