Skip to content

Commit f59eff2

Browse files
committed
output: elasticsearch: document AWS Elasticsearch status
Signed-off-by: Eduardo Silva <[email protected]>
1 parent 19138e5 commit f59eff2

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

output/elasticsearch.md

+13-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Elasticsearch
22

3-
The **es** output plugin, allows to flush your records into a [Elasticsearch](http://www.elastic.co) database. The following instructions assumes that you have a fully operational Elasticsearch service running in your environment.
3+
The **es** output plugin, allows to ingest your records into a [Elasticsearch](http://www.elastic.co) database. The following instructions assumes that you have a fully operational Elasticsearch service running in your environment.
44

55
## Configuration Parameters
66

@@ -117,3 +117,15 @@ If you see an error message like below, you'll need to fix your configuration to
117117
> Rejecting mapping update to [search] as the final mapping would have more than 1 type
118118
119119
For details, please read [the official blog post on that issue](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/removal-of-types.html).
120+
121+
### Fluent Bit + AWS Elasticsearch
122+
123+
AWS Elasticsearch adds an extra security layer where the HTTP requests we must be signed with AWS Signv4, as of Fluent Bit v1.3 this is not yet supported. At the end of January 2020 with the release of Fluent Bit v1.4 we are adding such feature (among integration with other AWS Services ;) )
124+
125+
As a workaround, you can use the following tool as a proxy:
126+
127+
- https://github.com/abutaha/aws-es-proxy
128+
129+
More details about this AWS requirement can be found here:
130+
131+
- https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-request-signing.html

0 commit comments

Comments
 (0)