# Access denied admin/aliases

**URL:** <https://discuss.elastic.co/t/access-denied-admin-aliases/186847>\
**Category:** Elasticsearch\
**Created:** [June 21, 2019, 9:27am UTC](https://discuss.elastic.co/t/access-denied-admin-aliases/186847 "2019-06-21T09:27:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wmcleod](https://avatars.discourse-cdn.com/v4/letter/w/ebca7d/32.png) [@wmcleod](https://discuss.elastic.co/u/wmcleod)\
**Post date:** [June 21, 2019, 9:27am UTC](https://discuss.elastic.co/t/access-denied-admin-aliases/186847/1 "2019-06-21T09:27:38Z")

</div>

I have setup a role to allow beats data to be indexed. I followed this article:  
[https://www.elastic.co/guide/en/beats/metricbeat/current/feature-roles.html](https://www.elastic.co/guide/en/beats/metricbeat/current/feature-roles.html)

The indexes aren't created and I receive the following entry in the audit log:  
{"@timestamp":"2019-06-21T10:24:44,209", "node.id":"xxxxxxxxxxxxxxxxxxxxx", "event.type":"transport", **"event.action":"access\_denied"** , "user.name":"ingest\_user", "user.realm":"default\_native", "user.roles":["ingest\_role","beats\_system"], "origin.type":"rest", "origin.address":"xx.xx.xx.xx:xxx", "request.id":"xxxxxxxxxxxxxxxxxxxxxx", **"action":"indices:admin/aliases"** , "request.name":"CreateIndexRequest", "indices":["\<metricbeat-financedept-{now/d}-000001\>"]}

What additional permissions are required to resolve this?

---

<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 19, 2019, 9:27am UTC](https://discuss.elastic.co/t/access-denied-admin-aliases/186847/2 "2019-07-19T09:27:42Z")

</div>

Closed on July 19, 2019, 9:27am UTC

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