Hello, im receiving 403 errors from elasticsearch ...
# troubleshoot
a
Hello, im receiving 403 errors from elasticsearch in the datahub-elasticsearch-setup-job. Is there anywhere details or a template for the policy I should apply to the datahub user ? I implemented a prefix with all the rights but it doesn't seem to work.
plus1 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: 1️⃣ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? 2️⃣ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues?
a
What is your version/deployment method. This could be related to the way the instance is deployed and connection rules between the containers
s
Hello @astonishing-answer-96712, Thanks for your answer ! I work with Robin so he asked me to continue this thread. We are on the version
v0.10.1
of Datahub. We've deployed it with GKE and helm. Also, we've noticed that the only rights that doesn't raise this error is the superadmin one, on Elasticsearch. If remove the superadmin rights, Datahub will return
ERROR 403
even if we give the "_all_" Cluster Privilege. What have we done wrong? Is there any privilege needed by the datahub user that only the superadmin can have? Thanks in advance for your help !
Any news on this matter? 😬 @astonishing-answer-96712
a
Could you walkthrough your usecase a little more? Are you looking to restrict access rights to the service working in ES?