Pain point · Permissions & security · Blocks work
Creating custom search attributes fails with Elasticsearch 403 on OpenSearch
3 source threads · first seen 2020-07 · last seen 2023-08
Summary
Adding a custom search attribute via CLI fails because the server user lacks permission to update the Elasticsearch mapping on a managed OpenSearch domain, so advanced visibility cannot be extended.
- Affects
- Self-hosters using AWS OpenSearch and Postgres
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“unable to update Elasticsearch mapping: elastic: Error 403 (Forbidden): no permissions for [] and User”
“It happens occasionally that one of the three (randomly) will be lost after the CLI command show up the registering is succeeded”
“I initially receive an error when trying to add attribute”