Darren, Converse API is a newer addition and is becoming my first preference when using Bedrock. Converse API provides a consistent interface to use multiple models. if use case requires getting the source/citation of the KB document used in the RAG solution then, I will use RetrieveAndGenerate API.
Can we use converse api if we just need to summarize documents like pdf and images without any conversation (single turn)? Also do we know what is retention period for the uploaded document in aws?
embedding and image not supported however you can use for summarization and PDF is supported. Also, if you use console for bedrock/KB, retention is for current session only. if you use S3 for the document, you can control the retention and remove the document via event, life cycle policy or via console.
what is the differentiating use case as to when to implement the RetrieveAndGenerate API vs the Converse API when building a RAG Chatbot?
Darren, Converse API is a newer addition and is becoming my first preference when using Bedrock. Converse API provides a consistent interface to use multiple models. if use case requires getting the source/citation of the KB document used in the RAG solution then, I will use RetrieveAndGenerate API.
Can we use bedrock embiddings with converse API from vector database?
Currently, embedding models not supported by Converse API however, you can use Bedrock InvokeModel.
@@CloudWithGirish Sure, Thank you for the reply.
Can we use converse api if we just need to summarize documents like pdf and images without any conversation (single turn)? Also do we know what is retention period for the uploaded document in aws?
embedding and image not supported however you can use for summarization and PDF is supported. Also, if you use console for bedrock/KB, retention is for current session only. if you use S3 for the document, you can control the retention and remove the document via event, life cycle policy or via console.