- Newest
- Most votes
- Most comments
Could be a fine grained access missing. ES has fine grained access control, please check the below
Index-Level Security
Index-level permissions include the ability to create new indices, search indices, read and write documents, delete documents, manage aliases, and more. Manage these permissions using the Index Permissions tab when creating a role. For a list of index-level action groups, see the Open Distro for Elasticsearch documentation
. https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/fgac.html
also, check the role mapping for the user “ arn:aws:iam::xxxxxx” a
To create a role mapping, login to Kibana, navigate to Security > Role Mappings, and click Create role mapping. Give your role mapping a unique name and choose which roles you wish to assign to your users.
https://aws.amazon.com/blogs/database/set-access-control-for-amazon-elasticsearch-service/
Relevant content
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
Hi. Did you solve this? I have the same issue.