Unable to see created vector index in OpenSearch Serverless

Question

After creating a collection in OpenSearch Serverless, I created a vector index through the console.
The creation seems to complete succesfully and in the Overview tab I can see the 'Indexes' count is 1.
However, when I go the 'Indexes' tab, I get the following error:

{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [OPEN]","index":"OPEN","index_uuid":"_na_"}],"type":"index_not_found_exception","reason":"no such index [OPEN]","index":"OPEN","index_uuid":"_na_"},"status":404}

I already tried to recreate the collection, but I always get the same error.
I've also tried to use Bedrock Knowledge Bases, which then creates an OpenSearch Serverless collection, and also there I see the same error.

Is this a permissions error or might there be a bug in the AWS backend?

re:Post Agent · Answer

The issue you're experiencing with not being able to see the created vector index in OpenSearch Serverless, despite the Overview tab showing an index count of 1, could be due to a few reasons:

1. Propagation Delay: OpenSearch Serverless might take some time to distribute systemic changes or updates across all nodes or replicas of an index. This propagation delay can cause the index to appear unavailable or inconsistent across different parts of the system.

2. Eventual Consistency: The OpenSearch Serverless system operates on an eventually consistent model, which means there might be a temporary discrepancy between what's reported in the Overview tab and what's actually accessible in the Indexes tab.

3. Permissions: There's a possibility that your current role or user doesn't have the necessary permissions to view the index details, even if you were able to create it.

To troubleshoot and potentially resolve this issue, you can try the following steps:

1. Wait for a few minutes (around 5-10) after creating the index before attempting to access it. This allows time for the system to fully propagate the changes.

2. Verify that your IAM role or user has the correct permissions to both create and view indexes in OpenSearch Serverless. Ensure you have the necessary data access policies configured for your collection.

3. Try to manually create or access the index using the OpenSearch API or CLI to see if you encounter the same issue.

4. If you're using Bedrock Knowledge Bases, ensure that the service role used has the required permissions to interact with OpenSearch Serverless collections and indexes.

5. Check the CloudWatch logs for any error messages or additional information that might help identify the root cause.

If after trying these steps you still encounter the same error, it's possible that there might be an underlying issue with the AWS backend. In this case, it would be advisable to contact AWS support for further investigation and assistance. They would be able to check for any known issues or bugs that might be affecting the OpenSearch Serverless service in your region or account.  
**Sources**  
[Resolve Amazon Bedrock knowledge base permission errors | AWS re:Post](https://repost.aws/knowledge-center/bedrock-knowledge-base-permission-errors)  
[Data access control for Amazon OpenSearch Serverless - Amazon OpenSearch Service](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-data-access.html)

Rich H · Answer

We've started seeing the same thing, definitely some sort of bug in OS collection.

Unable to see created vector index in OpenSearch Serverless

Relevant content