# .asdasd

**URL:** https://discuss.elastic.co/t/asdasd/99474
**Category:** Beats
**Tags:** filebeat
**Created:** [September 5, 2017, 7:18pm UTC](https://discuss.elastic.co/t/asdasd/99474 "2017-09-05T19:18:54Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![srivarunlokku](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@srivarunlokku](https://discuss.elastic.co/u/srivarunlokku)
#### Post date: [September 5, 2017, 7:18pm UTC](https://discuss.elastic.co/t/asdasd/99474/1 "2017-09-05T19:18:54Z")

</div>

........sdsdsa

---

<div class="post-metadata">

### Author: ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [September 11, 2017, 1:20pm UTC](https://discuss.elastic.co/t/asdasd/99474/2 "2017-09-11T13:20:33Z")

</div>

Is there any error? Check the Filebeat log file.

IIRC Amazon has some specialized requirements for requests to Elasticsearch where each request needs to be signed. There is no support for this (for auth Filebeat supports standard HTTP Basic Auth or TLS client certs).

---

<div class="post-metadata">

### Author: ![srivarunlokku](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@srivarunlokku](https://discuss.elastic.co/u/srivarunlokku)
#### Post date: [October 3, 2017, 3:12pm UTC](https://discuss.elastic.co/t/asdasd/99474/3 "2017-10-03T15:12:09Z")

</div>

sdfsdf

---

<div class="post-metadata">

### Author: ![srivarunlokku](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@srivarunlokku](https://discuss.elastic.co/u/srivarunlokku)
#### Post date: [October 3, 2017, 3:39pm UTC](https://discuss.elastic.co/t/asdasd/99474/4 "2017-10-03T15:39:16Z")

</div>

sddf

---

<div class="post-metadata">

### Author: ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [October 3, 2017, 4:35pm UTC](https://discuss.elastic.co/t/asdasd/99474/5 "2017-10-03T16:35:08Z")

</div>

> [@srivarunlokku](#):
>
> [https://logs.salesfusion360.com:9200](https://logs.salesfusion360.com:9200): dial tcp 10.0.0.10:9200: connectex: No connection could be made because the target machine actively refused it.

Sounds like your Amazon ES access policy is blocking the IP traffic. You'll probably need to grant anonymous access to your IP.

> [@srivarunlokku](#):
>
> I tried sending to logstash server as well. It shows different error on.

What's that error? Does your LS instance have access to the AWS ES instance? Are you using the [AWS ES output plugin](https://github.com/awslabs/logstash-output-amazon_es) that signs the requests to ES or have you granted the IP full anonymous access.

Consider trying the [Elastic Cloud](https://www.elastic.co/cloud/as-a-service/signup) service (also available from the [AWS marketplace](https://aws.amazon.com/marketplace/pp/B01N6YCISK?qid=1507048150098&sr=0-1&ref_=srh_res_product_title)) as it uses standard HTTP basic auth over TLS for authentication.

---

<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: [October 31, 2017, 4:35pm UTC](https://discuss.elastic.co/t/asdasd/99474/6 "2017-10-31T16:35:22Z")

</div>

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