- Newest
- Most votes
- Most comments
Based on your description, it appears you're experiencing an issue with syncing your Bedrock Knowledge Base. There are several common reasons why the sync might fail without providing a clear error message:
-
Model access permissions: The most likely cause is that you haven't subscribed to or requested access to the embedding model being used by your Knowledge Base. Even though you've created the Knowledge Base successfully, the sync process requires access to specific Bedrock models (like Amazon Titan Embed) to generate vector embeddings. Check the "Model access" section in the Bedrock console and ensure you've subscribed to the necessary models.
-
IAM role permissions: While you mentioned letting Bedrock create a new IAM role, the default role might not have all necessary permissions. The Knowledge Base role needs permissions to call the specified Bedrock embedding model, access your Redshift data, and manage the vector store.
-
Vector store configuration: If you're using Amazon OpenSearch Serverless as your vector store (which is often the default), ensure that the vector index is properly configured with the 'faiss' engine.
-
Sync process limitations: There might be an ongoing sync process that's not visible in the UI, or there could be issues with the console interface itself.
To troubleshoot:
- Check CloudTrail logs for any "StartIngestionJob" API execution details
- Verify you have access to the embedding model being used (typically Amazon Titan Embed)
- Refresh the page and try the sync again
- Check if there are any size limitations or format issues with your data in Redshift
Many users have resolved similar issues by subscribing to the required embedding model in the Bedrock Marketplace, particularly the Amazon Titan Embed model.
Sources
Bedrock Data source sync does not work | AWS re:Post
Data sync failed error in Amazon Bedrock Knowledgebase | AWS re:Post
Bedrock knowledge base data source sync is not working | AWS re:Post
- Titan is enabled
- Did try even adding Admin policy to IAM role, but no effect.
- This doesn't apply to structured knowledge bases.
- This was the initial sync failing.
Relevant content
- asked a year ago

Hi, did you you enabling logging to CloudWatch logs? This was the only way I was able to figure out the metadata file had a 10kb limit.
https://docs.aws.amazon.com/bedrock/latest/userguide/knowledge-bases-logging.html
I don't think there is such option for structured knowledge bases.