# .NET NEST and logstash?

**URL:** <https://discuss.elastic.co/t/net-nest-and-logstash/62940>\
**Category:** Logstash\
**Created:** [October 13, 2016, 12:54pm UTC](https://discuss.elastic.co/t/net-nest-and-logstash/62940 "2016-10-13T12:54:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![agonzalez](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@agonzalez](https://discuss.elastic.co/u/agonzalez)\
**Post date:** [October 13, 2016, 12:54pm UTC](https://discuss.elastic.co/t/net-nest-and-logstash/62940/1 "2016-10-13T12:54:55Z")

</div>

is there any way to index documents using .NET NEST but using logstash as endpoint? All my clients are spread over internet and only should connect to logstash public server only, not directly to ES.

---

<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:** [October 13, 2016, 1:04pm UTC](https://discuss.elastic.co/t/net-nest-and-logstash/62940/2 "2016-10-13T13:04:57Z")

</div>

Logstash has an http input, but using NEST to post to it doesn't make sense. It _might_ work but you shouldn't rely on it.

---

<div class="post-metadata">

**Author:** ![KodrAus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kodraus/32/22798_2.png) [@KodrAus](https://discuss.elastic.co/u/KodrAus)\
**Post date:** [October 13, 2016, 9:25pm UTC](https://discuss.elastic.co/t/net-nest-and-logstash/62940/3 "2016-10-13T21:25:42Z")

</div>

You're saying you don't want your clients to connect to your ES cluster directly, which is good. But _why_ you don't want your clients to connect to ES directly is important for figuring out what to put between the internet and your cluster.

Is it purely a load balancing problem? You want to be able to queue requests and apply backpressure if it starts getting overloaded?

Or is it a security problem? Obviously you don't want an ES cluster that anybody can talk to floating around on the Internet.

So what's the plan?

---

<div class="post-metadata">

**Author:** ![agonzalez](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@agonzalez](https://discuss.elastic.co/u/agonzalez)\
**Post date:** [October 13, 2016, 9:46pm UTC](https://discuss.elastic.co/t/net-nest-and-logstash/62940/4 "2016-10-13T21:46:09Z")

</div>

It is a security problem, as this goes over internet I dont want customers decompiling my .net assembly and getting my public elk cluster ip and credentials and connecting to do queries. So I would like to mantain ES cluster not exposed to internet but just logstash so everything should be indexed through logstash and they cant query ES if there is some security breach.

My .net appliacation is an agent that runs on customers and collect data and index to ES, so it just need to index documents.

---

<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, 4:34am UTC](https://discuss.elastic.co/t/net-nest-and-logstash/62940/5 "2017-07-06T04:34:19Z")

</div>

Closed on July 6, 2017, 4:34am UTC