# Logstash-output-elasticsearch-shield still available?

**URL:** https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400
**Category:** Elasticsearch
**Tags:** elastic-stack-security
**Created:** [July 13, 2015, 12:07am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400 "2015-07-13T00:07:08Z")
**Posts on this page:** 10
**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: [July 13, 2015, 12:07am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/1 "2015-07-13T00:07:08Z")

</div>

I just tried installing the logstash-output-elasticsearch-shiled plugin, with no results:

```
#plugin install logstash-output-elasticsearch-shield --verbose
-> Installing logstash-output-elasticsearch-shield...
Trying https://github.com/null/logstash-output-elasticsearch-shield/archive/master.zip...
Failed: IOException[Can't get https://github.com/null/logstash-output-elasticsearch-shield/archive/master.zip to /usr/share/elasticsearch/plugins/logstash-output-elasticsearch-shield.zip]; nested: FileNotFoundException[https://github.com/null/logstash-output-elasticsearch-shield/archive/master.zip]; nested: FileNotFoundException[https://github.com/null/logstash-output-elasticsearch-shield/archive/master.zip];
Failed to install logstash-output-elasticsearch-shield, reason: failed to download out of all possible locations..., use --verbose to get detailed information

```

I also tried searching github for the plugin, with no luck. Is this plugin still available?

---

<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: [July 13, 2015, 12:29am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/2 "2015-07-13T00:29:33Z")

</div>

I don't think there ever was one?  
Are you just sending to ES+Shield? If so use the standard ES output and set authentication there.

---

<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: [July 13, 2015, 12:38am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/3 "2015-07-13T00:38:21Z")

</div>

> [@warkolm](#):
>
> I don't think there ever was one?Are you just sending to ES+Shield? If so use the standard ES output and set authentication there.

I found that output in this documentation:

[Logstash Output ES Shield](https://www.elastic.co/guide/en/shield/current/logstash.html#ls-transport)

So maybe the docs need to be updated. 😄

But yeah, I tried using the standard output. And I'm having some issues there. I write about that problem in another post.

---

<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: [July 13, 2015, 12:45am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/4 "2015-07-13T00:45:13Z")

</div>

Right, well I can be wrong at times 😛

---

<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: [July 13, 2015, 12:47am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/5 "2015-07-13T00:47:43Z")

</div>

> [@warkolm](#):
>
> Right, well I can be wrong at times

LOL 😉

---

<div class="post-metadata">

### Author: ![jaymode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaymode/32/50103_2.png) [@jaymode](https://discuss.elastic.co/u/jaymode)
#### Post date: [July 13, 2015, 10:54am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/6 "2015-07-13T10:54:21Z")

</div>

I believe the documentation is correct. I didn't have any issues installing this logstash output in a fresh instance of logstash:

```
$ cd logstash-1.5.2
$ bin/plugin install logstash-output-elasticsearch-shield
Validating logstash-output-elasticsearch-shield
Installing logstash-output-elasticsearch-shield
Installation successful

```

What version of logstash did you run the install command from?

---

<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: [July 15, 2015, 1:54am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/7 "2015-07-15T01:54:42Z")

</div>

Hey Jaymode,

> [@jaymode](#):
>
> install logstash-output-elasticsearch-shield

Cool! Thanks for pointing that out. Seems there are two 'plugin' binaries, and I was using the wrong one!

```
[root@logs:~] #find / -name plugin -type f
/usr/share/elasticsearch/bin/plugin
/opt/logstash/bin/plugin

```

So I tried using the logstash plugin binary instead of the elasticsearch one, and it worked like a charm!

```
  [root@logs:~] #/opt/logstash/bin/plugin install logstash-output-elasticsearch-shield
Validating logstash-output-elasticsearch-shield
Installing logstash-output-elasticsearch-shield
Installation successful

```

I thank you for the advice! Well know that I have logstash working with ES+Shield, I may be content to stick with what I have. But I may use this at some point, as the documentation points out that its more efficient than HTTP mode.

Anyway, thanks again! And I definitely appreciate the tremendous helpfulness of this active community!

---

<div class="post-metadata">

### Author: ![jaymode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaymode/32/50103_2.png) [@jaymode](https://discuss.elastic.co/u/jaymode)
#### Post date: [July 15, 2015, 11:09am UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/8 "2015-07-15T11:09:09Z")

</div>

That's great! I'm glad you were able to get it going.

We're aware of the plugin executable name clash and we're looking at folding the functionality into the elasticsearch command [https://github.com/elastic/elasticsearch/issues/11797](https://github.com/elastic/elasticsearch/issues/11797)

---

<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: [July 15, 2015, 5:49pm UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/9 "2015-07-15T17:49:54Z")

</div>

> [@jaymode](#):
>
> That's great! I'm glad you were able to get it going.
> 
> We're aware of the plugin executable name clash and we're looking at folding the functionality into the elasticsearch command [Fold `plugin` script into `elasticsearch` script with -plugin option · Issue #11797 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/11797)

Hey man! Yeah I'm glad I got that sorted out too. And it makes sense to me to fold the functionality of both plugin commands into one. I was actually about to suggest it. Too confusing to have two commands with the same name service different purposes.

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: [July 6, 2017, 1:48pm UTC](https://discuss.elastic.co/t/logstash-output-elasticsearch-shield-still-available/25400/10 "2017-07-06T13:48:50Z")

</div>


