Skip to content

Knowledgebase sync not updating the AI

1

Problem: When I add new documents to my S3 bucket (which is a Bedrock KB data source) and sync, all metrics indicate success, but the AI can't retrieve the new data.

Specifics: Initial KB creation/sync works fine; AI references initial data. After uploading new documents to S3 and syncing: Bedrock KB sync history shows "Complete", "Added +1", and total "Source files" increases. OpenSearch "Total document count" for the KB's index also increases.

However, when querying via the Retrieve API (with unique phrases from the new docs), the new documents are NEVER returned. The AI in TEST Knowledgebase is also completely unaware of them.

This happens with both large KBs (tens of thousands of docs) and small test KBs (single docs).

I get zero errors in Bedrock or during sync. All statuses are green.

I've verified S3 access, IAM permissions, PDF searchability, and consistency of S3 paths.

It seems the data is ingested and indexed, but then it's not searchable. Any ideas why retrieval might fail despite all success indicators?

Thanks!

asked a year ago238 views

1 Answer
-1

Based on your description, there are several potential reasons why your newly added documents aren't being retrieved despite successful sync indicators:

  1. Sync Process Understanding: When you add new files to your S3 bucket, the Knowledge Base doesn't automatically update. You need to manually trigger a sync operation. It appears you're already doing this, but it's worth noting that syncing is incremental - Bedrock only processes added, modified, or deleted documents since the last sync.

  2. Model Access Issues: One common cause of sync problems is not having access to the embedding models being used. Verify that you have requested and been granted access to the specific models your Knowledge Base is using for vector embeddings under "model access" in Bedrock.

  3. File Overwriting Problems: If you're overwriting existing files in S3 rather than adding new ones with different names, this can sometimes cause issues with the sync process. The logs might show "PARTIALLY_INDEXED" status with "failed_to_update_metadata" errors. In some cases, deleting the problematic files and uploading them again (rather than overwriting) resolves the issue.

  4. Sync Timing: After a successful sync, it may take a few minutes for the vector embeddings to be fully reflected in the knowledge base for querying, especially if you're using a vector store other than Amazon Aurora.

  5. Console Refresh Issues: Sometimes the console may not reflect the actual state of operations. Try refreshing the page or waiting a few minutes to see if the retrieval starts working.

If you've verified all these points and the issue persists, you might want to check CloudWatch logs for any "StartIngestionJob" API execution details or CloudTrail event history, which could provide more insights into what might be happening behind the scenes during the sync process.
Sources
Bedrock knowledge base data source sync is not working | AWS re:Post
AWS Bedrock Knowledge Base not syncing when files are being over-written in S3 Bucket | AWS re:Post
Data sync in bedrock knowledge base | AWS re:Post
Bedrock Data source sync does not work | AWS re:Post
Does Knowledge Base auto update data from s3 | AWS re:Post

answered a year ago

  • Thank you for your in-depth answer but unfortunately i can check all these points off. When adding data (new data) i press the sync button and it syncs successfully.

    I have access to the embedding models and the initial knowledgebase creation is successful.

    Logs show that the sync was successful.

    I waited a whole 24hours but still nothing.

    The page does show that the sync was successful and that new data was added.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.