# Accessing Kibana of AWS ElasticSearch by Gateway using AWS IAM

**URL:** <https://discuss.elastic.co/t/accessing-kibana-of-aws-elasticsearch-by-gateway-using-aws-iam/58938>\
**Category:** Elasticsearch\
**Created:** [August 25, 2016, 1:51pm UTC](https://discuss.elastic.co/t/accessing-kibana-of-aws-elasticsearch-by-gateway-using-aws-iam/58938 "2016-08-25T13:51:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![camarar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/camarar/32/20476_2.png) [@camarar](https://discuss.elastic.co/u/camarar)\
**Post date:** [August 25, 2016, 1:51pm UTC](https://discuss.elastic.co/t/accessing-kibana-of-aws-elasticsearch-by-gateway-using-aws-iam/58938/1 "2016-08-25T13:51:50Z")

</div>

I'm studying about ELK Stack and AWS Gateway.

I created AWS ElasticSearch and set this access policy: { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::[AWS account ID]:root" }, "Action": "es:\*", "Resource": "arn:aws:es:sa-east-1:[AWS account ID]:domain/camarar-elk/\*" } ] }

PS: I try to use with this policy too: { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::[AWS account ID]:user/[User]" }, "Action": "es:\*", "Resource": "arn:aws:es:sa-east-1:[AWS account ID]:domain/camarar-elk/\*" } ] }

After, I created an AWS API Gateway using http proxy and GET method to route all request to Kibana url. And in this Gateway I using one AWS IAM to access Kibana.

Finally, I created an user of AWS IAM with this policy "AmazonESFullAccess".

All the time I received the same error:{"Message":"User: anonymous is not authorized to perform: es:ESHttpGet on resource: camarar-elk"}

Anybody could you please help me to resolve this problem?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 26, 2016, 5:19am UTC](https://discuss.elastic.co/t/accessing-kibana-of-aws-elasticsearch-by-gateway-using-aws-iam/58938/2 "2016-08-26T05:19:58Z")

</div>

You need to ask on the AWS forums.

---

<div class="post-metadata">

**Author:** ![camarar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/camarar/32/20476_2.png) [@camarar](https://discuss.elastic.co/u/camarar)\
**Post date:** [August 26, 2016, 1:07pm UTC](https://discuss.elastic.co/t/accessing-kibana-of-aws-elasticsearch-by-gateway-using-aws-iam/58938/3 "2016-08-26T13:07:15Z")

</div>

I sent this post to all the channels that I knew about Elastic. And this forum is about Elastic it is possible that anyone had this problem using AWS Elastic..

---

<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, 10:24pm UTC](https://discuss.elastic.co/t/accessing-kibana-of-aws-elasticsearch-by-gateway-using-aws-iam/58938/4 "2017-07-05T22:24:53Z")

</div>