# 403 Forbidden when trying to send logs using Filebeat

**URL:** <https://discuss.elastic.co/t/403-forbidden-when-trying-to-send-logs-using-filebeat/279249>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 21, 2021, 10:04am UTC](https://discuss.elastic.co/t/403-forbidden-when-trying-to-send-logs-using-filebeat/279249 "2021-07-21T10:04:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OksanaH](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oksanah/32/91894_2.png) [@OksanaH](https://discuss.elastic.co/u/OksanaH)\
**Post date:** [July 21, 2021, 10:04am UTC](https://discuss.elastic.co/t/403-forbidden-when-trying-to-send-logs-using-filebeat/279249/1 "2021-07-21T10:04:13Z")

</div>

I'm using Filebeat OSS licenced version 7.10, and AWS ElasticSearch 7.10.  
I use a reverse logging proxy and set up auth like this:`proxy_set_header Authorization "";`  
When configuring Filebeat, I use Basic Auth (username and password, base 64 encoded) and use that to send logs to ElasticSearch.  
I get a 403 error with the following message:

`Authorization header requires 'Credential' parameter. Authorization header requires 'Signature' parameter. Authorization header requires 'SignedHeaders' parameter`

What could be the reason for this error?  
Thanks

---

<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:** [August 18, 2021, 12:04pm UTC](https://discuss.elastic.co/t/403-forbidden-when-trying-to-send-logs-using-filebeat/279249/2 "2021-08-18T12:04:24Z")

</div>

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