# Protect ElasticSearch port(s) on Amazon EC2 instances

**URL:** <https://discuss.elastic.co/t/protect-elasticsearch-port-s-on-amazon-ec2-instances/5979>\
**Category:** Elasticsearch\
**Created:** [November 26, 2011, 4:27pm UTC](https://discuss.elastic.co/t/protect-elasticsearch-port-s-on-amazon-ec2-instances/5979 "2011-11-26T16:27:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karussell1](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@Karussell1](https://discuss.elastic.co/u/Karussell1)\
**Post date:** [November 26, 2011, 4:27pm UTC](https://discuss.elastic.co/t/protect-elasticsearch-port-s-on-amazon-ec2-instances/5979/1 "2011-11-26T16:27:40Z")

</div>

I didn't get it working to avoid opening the 9300 port. In the manual  
it is stated that I need to open the port and when I do not open the  
port the instances do not discover themself as a cluster (I see an  
exception when they try to access the other machine). I guess there  
has to happen some magic with the security group or is it not  
possible?

Regards,  
Peter.

---

<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 6, 2017, 3:47am UTC](https://discuss.elastic.co/t/protect-elasticsearch-port-s-on-amazon-ec2-instances/5979/2 "2017-07-06T03:47:25Z")

</div>