# Nginx authentication to aws es inside vpc

**URL:** <https://discuss.elastic.co/t/nginx-authentication-to-aws-es-inside-vpc/115899>\
**Category:** Elasticsearch\
**Created:** [January 17, 2018, 2:45pm UTC](https://discuss.elastic.co/t/nginx-authentication-to-aws-es-inside-vpc/115899 "2018-01-17T14:45:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rrecchia1](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@rrecchia1](https://discuss.elastic.co/u/rrecchia1)\
**Post date:** [January 17, 2018, 2:45pm UTC](https://discuss.elastic.co/t/nginx-authentication-to-aws-es-inside-vpc/115899/1 "2018-01-17T14:45:15Z")

</div>

So we have nginx reverse proxying to elasticsearch set up in amazon aws VPC. so far things are working as expected. I want to add some basic http authentication as I have done this many times in the past. However this time after I get the login screen I am seeing this error in the nginx logs. Http 403 error

"POST /es\_admin/.kibana/index-pattern/\_search?stored\_fields= HTTP/1.1" 403

authentication does work as I do get the Kibana Interface ( we are running kibana on the ec2 instance ) just no data.

---

<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:** [February 14, 2018, 2:45pm UTC](https://discuss.elastic.co/t/nginx-authentication-to-aws-es-inside-vpc/115899/2 "2018-02-14T14:45:20Z")

</div>

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