# Logstash Output to ES hosted on AWS, authentication not working

**URL:** <https://discuss.elastic.co/t/logstash-output-to-es-hosted-on-aws-authentication-not-working/164504>\
**Category:** Logstash\
**Created:** [January 16, 2019, 4:37pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-hosted-on-aws-authentication-not-working/164504 "2019-01-16T16:37:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Smitto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/smitto/32/38710_2.png) [@Smitto](https://discuss.elastic.co/u/Smitto)\
**Post date:** [January 16, 2019, 4:37pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-hosted-on-aws-authentication-not-working/164504/1 "2019-01-16T16:37:19Z")

</div>

I've been trying to send my Logstash output to an Elasticsearch instance being hosted on AWS. Following the instructions [here](https://discuss.elastic.co/t/unable-to-communicate-with-elasticseach/70057) I've set up my conf file's output as the following:

```
output {
    elasticsearch {
        hosts => ["host_url"]
        index => "logstash-dev-device-data"
        document_type => "logstash-device-data"
        manage_template => true
        template => "./logstash_idx_mapping.json"
        template_name => "logstash_idx_mapping_template"
        user => "username"
        password => "${LOGSTASH_PASSWORD}"
    }
}

```

In kibana, I have a user set up with the username and password I'm passing in the config output above.  
I'm still getting the following error

`Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Something is wrong with your configuration.", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/config/mixin.rb:86:in 'config_init'"`

Does anyone know what else I can try for this? Thanks!

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 16, 2019, 5:02pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-hosted-on-aws-authentication-not-working/164504/2 "2019-01-16T17:02:58Z")

</div>

I believe AWS ES requires a separate, custom output plugin named `amazon_es`.

---

<div class="post-metadata">

**Author:** ![Smitto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/smitto/32/38710_2.png) [@Smitto](https://discuss.elastic.co/u/Smitto)\
**Post date:** [January 16, 2019, 7:11pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-hosted-on-aws-authentication-not-working/164504/3 "2019-01-16T19:11:06Z")

</div>

Thanks for the response Christian. This wasn't using AWS's specific ES service, but it turned out the issue was stemming from a change in my template path.

---

<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:** [February 13, 2019, 7:11pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-hosted-on-aws-authentication-not-working/164504/4 "2019-02-13T19:11:14Z")

</div>

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