You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a role is deployed manually via UI AWS lambda will identify the role and permission
if the role is created via API, such as dev tool, lambda will always throws below error
{'type': 'security_exception', 'reason': 'no permissions for [indices:data/write/delete/byquery] and User [name=arn:aws:iam::111111111111111:role/lambdaOpenSearchRole, backend_roles=[arn:aws:iam::111111111111111:role/lambdaOpenSearchRole], requestedTenant=null]'}], 'type': 'security_exception', 'reason': 'no permissions for [indices:data/write/delete/byquery] and User [name=arn:aws:iam::111111111111111:role/lambdaOpenSearchRole, backend_roles=[arn:aws:iam::111111111111111:role/lambdaOpenSearchRole], requestedTenant=null]'}, 'status': 403}
Related component
Plugins
To Reproduce
Create a role via API (dev tool)
Map the role to a backend role to AWS role via API
Test with a lambda python code for any simple task such as getting a document by ID
The text was updated successfully, but these errors were encountered:
alwashali
added
bug
Something isn't working
untriaged
Require the attention of the repository maintainers and may need to be prioritized
labels
Jul 19, 2024
peternied
changed the title
[BUG] <Backend role mapping is not found by AWS resource if deployed via api>
[BUG] Backend role mapping is not found by AWS resource if deployed via api
Jul 24, 2024
[Triage - attendees 12] @alwashali Thanks for creating this issue, it looks like this is related to the security plugin, I'm going to transfer this issue to that repository. Note; it looks like you are using AWS' OpenSearch service, I would recommend creating a support ticket with them for a faster/ more complete response.
peternied
removed
the
untriaged
Require the attention of the repository maintainers and may need to be prioritized
label
Jul 24, 2024
[Triage] Hi @alwashali, thanks for filing this issue. This looks like an AWS OpenSearch Service question. Unfortunately, we are unable to provide support for these issues as this project is for the open-source code base. Please contact your AWS service team or file a support ticket for this issue.
Describe the bug
If a role is deployed manually via UI AWS lambda will identify the role and permission
if the role is created via API, such as dev tool, lambda will always throws below error
{'type': 'security_exception', 'reason': 'no permissions for [indices:data/write/delete/byquery] and User [name=arn:aws:iam::111111111111111:role/lambdaOpenSearchRole, backend_roles=[arn:aws:iam::111111111111111:role/lambdaOpenSearchRole], requestedTenant=null]'}], 'type': 'security_exception', 'reason': 'no permissions for [indices:data/write/delete/byquery] and User [name=arn:aws:iam::111111111111111:role/lambdaOpenSearchRole, backend_roles=[arn:aws:iam::111111111111111:role/lambdaOpenSearchRole], requestedTenant=null]'}, 'status': 403}
Related component
Plugins
To Reproduce
The text was updated successfully, but these errors were encountered: