# Port Requirement

**URL:** <https://discuss.elastic.co/t/port-requirement/51529>\
**Category:** Beats\
**Created:** [June 1, 2016, 8:56am UTC](https://discuss.elastic.co/t/port-requirement/51529 "2016-06-01T08:56:38Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 1, 2016, 8:56am UTC](https://discuss.elastic.co/t/port-requirement/51529/1 "2016-06-01T08:56:38Z")

</div>

It seems that when we start install and run the different kinds of beats, they will go smooth naturally. So is there any actual port opening requirement for beats?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [June 1, 2016, 9:28am UTC](https://discuss.elastic.co/t/port-requirement/51529/2 "2016-06-01T09:28:54Z")

</div>

Depends on output. Beats do not open any ports.

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 1, 2016, 9:40am UTC](https://discuss.elastic.co/t/port-requirement/51529/3 "2016-06-01T09:40:14Z")

</div>

I am outputing to elasticsearch which is installed in another server. So no ports needed for that?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 1, 2016, 5:27pm UTC](https://discuss.elastic.co/t/port-requirement/51529/4 "2016-06-01T17:27:09Z")

</div>

Your Beats obviously need to be able to open connections towards the ES server's HTTP interface, which typically runs on port 9200.

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 2, 2016, 1:23am UTC](https://discuss.elastic.co/t/port-requirement/51529/5 "2016-06-02T01:23:02Z")

</div>

Yup but like the comunication port between beats and elasticsearch is flexible?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 2, 2016, 3:39am UTC](https://discuss.elastic.co/t/port-requirement/51529/6 "2016-06-02T03:39:29Z")

</div>

I'm not sure what you mean. ES's listening port is configurable so in that sense it's flexible.

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 2, 2016, 4:40am UTC](https://discuss.elastic.co/t/port-requirement/51529/7 "2016-06-02T04:40:56Z")

</div>

Yea, ok. I understand your meanings. Great 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:** [June 22, 2016, 8:56am UTC](https://discuss.elastic.co/t/port-requirement/51529/8 "2016-06-22T08:56:50Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.
