# Beats output to AWS Elasticsearch

**URL:** https://discuss.elastic.co/t/beats-output-to-aws-elasticsearch/65985
**Category:** Beats
**Created:** [November 14, 2016, 1:27pm UTC](https://discuss.elastic.co/t/beats-output-to-aws-elasticsearch/65985 "2016-11-14T13:27:18Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![lpetre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lpetre/32/13154_2.png) [@lpetre](https://discuss.elastic.co/u/lpetre)
#### Post date: [November 14, 2016, 1:27pm UTC](https://discuss.elastic.co/t/beats-output-to-aws-elasticsearch/65985/1 "2016-11-14T13:27:18Z")

</div>

We'd like to setup our beat to output to the AWS Elasticsearch offering. The ideal way to do this is to sign the HTTP request with the AWS credentials. I'm trying to figure out the best way to implement this in the beats codebase. Is it a different output type? Or an configuration option to the Elasticsearch output type?

This is the lightest touch I could think of, but I'm curious to discuss the feature with the beats maintainers:

> **[elastic/beats](https://github.com/elastic/beats/compare/master...lpetre:sign_aws_requests)**
>
> beats - :tropical\_fish: Beats - Lightweight shippers for Elasticsearch & Logstash

Thanks!

---

<div class="post-metadata">

### Author: ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)
#### Post date: [November 15, 2016, 8:19am UTC](https://discuss.elastic.co/t/beats-output-to-aws-elasticsearch/65985/2 "2016-11-15T08:19:09Z")

</div>

Thanks for opening the discussion and for using Beats. In general I'd see the AWS ES output as a separate output type, but to be honest, I'm not sure it is something we want to support in the main Beats repository. The AWS ES service is separate from Elastic, and testing with it will add a some overhead to us, so we're not particularly eager 🙂

If you make it it's own output module, you could maintain it out of the Beats repository and only include it with a minimal patch at compilation time. This should help with maintaining across Beats versions. It looks like Go 1.8 will have dynamic plugins support, so relatively soon we might be also able to load such plugins at run time.

---

<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: [December 5, 2016, 1:27pm UTC](https://discuss.elastic.co/t/beats-output-to-aws-elasticsearch/65985/3 "2016-12-05T13:27:24Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.
