- Newest
- Most votes
- Most comments
If you are on public access, and your IAM has the right permission but you still cannot access dashboard, check if you have enabled "Access to Opensearch Dashboards", which is disabled by default. Here is how:
- Go to OpenSearch -> Collections, click into your serverless collection.
- Scroll down to Network part, click Manage network access -> click into network policy name, choose edit, scroll to the very bottom and click "Enable access to OpenSearch Dashboards", put your filters in.
This did the trick!
Error 401 while accessing OpenSearch serverless dashboard generally occurs when you are a collection has VPC access type but you are trying to access it from the public internet. I kindly request you to check if the request to access dashboard is coming from the same VPC in which the collection is created.
For more details on network settings for OpenSearch serverless collection, I kindly request you to follow reference[1].
Please let me know If you are using VPC access type and sending the request through the same VPC and still facing this issue or have any other concerns/queries related to the same, please feel free to reach back to me and I will be glad to assist.
Reference: [1] Network access for Amazon OpenSearch Serverless https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-network.html
Hey Akash, I have a vectorsearch opensearch collection under the opensearch managed VPC endpoint. I have successfully created a collection defining all the required IAM permissions to the users that needs to access the collection, properly defined data access policy, network policy being private and using VPC endpoint id. But when I try to hit the dashboard URL, it is still giving me error 401. Do you have any idea why is that happening or any workaround on it? Is it not possible to hit the dashboard URL directly or do I need to place some kind of the proxy server in between?
I'm also facing the same issue and when i try to access it publicly i get 401 whereas within the vpc it is throwing 403.
I'm also having these issues with a public access type. Further the OpenSearch Dashboards URL doesn't even show up.
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
how did you resolved? i'm also having same problem