# Filebeat to AWS SQS

**URL:** <https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 25, 2016, 12:03am UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271 "2016-04-25T00:03:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![gcherneski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gcherneski/32/9382_2.png) [@gcherneski](https://discuss.elastic.co/u/gcherneski)\
**Post date:** [April 25, 2016, 12:03am UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271/1 "2016-04-25T00:03:31Z")

</div>

I am configuring an AWS-based ELK stack where I want to send my Filebeat output to AWS SQS and then from AWS SQS to an AWS ELB facing multiple Logstash instances. I cannot find any blog or doc on this subject. Has someone configured Filebeat to send log messages to SQS? If yes, can someone share their configs? Thank you in advance.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [April 25, 2016, 6:53am UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271/2 "2016-04-25T06:53:17Z")

</div>

Currently Filebeat only supports Elasticsearch and Logstash as output. We are adding Kafka and Redis for the next major release. SQS is not supported.

---

<div class="post-metadata">

**Author:** ![iGaskin](https://avatars.discourse-cdn.com/v4/letter/i/ad7895/32.png) [@iGaskin](https://discuss.elastic.co/u/iGaskin)\
**Post date:** [August 9, 2016, 12:00am UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271/3 "2016-08-09T00:00:00Z")

</div>

I was going to pursue the same type of architecture, but I suppose I'll pursue Redis as a queueing service. Any plans to support SQS in upcoming releases?

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [August 9, 2016, 2:10pm UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271/4 "2016-08-09T14:10:48Z")

</div>

Currently no plans to add SQS

---

<div class="post-metadata">

**Author:** ![D-R-i-V-e](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@D-R-i-V-e](https://discuss.elastic.co/u/D-R-i-V-e)\
**Post date:** [April 4, 2017, 7:50pm UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271/5 "2017-04-04T19:50:37Z")

</div>

Hi @Ruflin,  
What's the way to submit an official enhancement request for adding SQS support to Beats?  
We found Filebeat much more effective than Logstash, yet we are unable to switch and enjoy other Beats as well.  
Thanks,  
D.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [April 5, 2017, 2:22pm UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271/6 "2017-04-05T14:22:03Z")

</div>

You can open a feature request in the beats repo. But before you do, I recommend reading this entry here [https://github.com/elastic/beats/issues/581#issuecomment-247034174](https://github.com/elastic/beats/issues/581#issuecomment-247034174) and the linked issue. I think it still holds true.

What I recommend you to do is having filebeat on all your edge nodes and sending data to a few LS nodes to the output it to SQS.

---

<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 5, 2017, 9:49pm UTC](https://discuss.elastic.co/t/filebeat-to-aws-sqs/48271/7 "2017-07-05T21:49:44Z")

</div>


