# Fleet-server is unauthorized on indice

**URL:** <https://discuss.elastic.co/t/fleet-server-is-unauthorized-on-indice/332566>\
**Category:** Elastic Agent\
**Created:** [May 4, 2023, 2:05pm UTC](https://discuss.elastic.co/t/fleet-server-is-unauthorized-on-indice/332566 "2023-05-04T14:05:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![stenbot1](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@stenbot1](https://discuss.elastic.co/u/stenbot1)\
**Post date:** [May 4, 2023, 2:05pm UTC](https://discuss.elastic.co/t/fleet-server-is-unauthorized-on-indice/332566/1 "2023-05-04T14:05:12Z")

</div>

Hello!

I am pretty green when it comes to Elastic but I recently set up a brand new stack to test ingesting a log file. I installed the Elastic Agent on a Windows machine that outputs logs to a file. I have the integration for Custom Logs set up in the policy for the agent. I created an Ingest Pipeline for these logs and when I go into Discover to see if the logs are being ingested I get the error:

`Action [indices:admin/auto_create] is unauthorized for API key id [######] of user [elastic/fleet-server] on indices [logs-log-1-default], this action is granted by the index privileges [auto_configure,create_index,manage,all]"}, dropping event!`

for all the lines in the log. Not sure where to go from here.

Thanks!

---

<div class="post-metadata">

**Author:** ![Priscilla\_Parodi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/priscilla_parodi/32/43047_2.png) [@Priscilla\_Parodi](https://discuss.elastic.co/u/Priscilla_Parodi)\
**Post date:** [May 31, 2023, 4:50pm UTC](https://discuss.elastic.co/t/fleet-server-is-unauthorized-on-indice/332566/2 "2023-05-31T16:50:37Z")

</div>

Hello @stenbot1,

Which Elastic version are you using? Could you pls check if [this solution](https://discuss.elastic.co/t/action-indices-admin-auto-create-is-unauthorized-for-api-key-id-of-user-elastic-fleet-server-on-indices-metricbeat-7-14-1-2021-09-08-this-action-is-granted-by-the-index-privileges-auto-configure-create-index-manage-all/283608) works for you?

---

<div class="post-metadata">

**Author:** ![stenbot1](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@stenbot1](https://discuss.elastic.co/u/stenbot1)\
**Post date:** [June 13, 2023, 5:35pm UTC](https://discuss.elastic.co/t/fleet-server-is-unauthorized-on-indice/332566/3 "2023-06-13T17:35:47Z")

</div>

I am currently using 8.7.1. I tried the fix suggested in the solution you linked and it solved my issue. Thank You!

---

<div class="post-metadata">

**Author:** ![Priscilla\_Parodi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/priscilla_parodi/32/43047_2.png) [@Priscilla\_Parodi](https://discuss.elastic.co/u/Priscilla_Parodi)\
**Post date:** [June 13, 2023, 5:59pm UTC](https://discuss.elastic.co/t/fleet-server-is-unauthorized-on-indice/332566/4 "2023-06-13T17:59:56Z")

</div>

You're welcome!

---

<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 11, 2023, 6:00pm UTC](https://discuss.elastic.co/t/fleet-server-is-unauthorized-on-indice/332566/5 "2023-07-11T18:00:54Z")

</div>

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