Build RAG Chatbot with Haystack, Pgvector, Amazon Bedrock Claude 3.7 Sonnet, and Cohere embed-english-light-v3.0

Introduction to RAG

Retrieval-Augmented Generation (RAG) is a game-changer for GenAI applications, especially in conversational AI. It combines the power of pre-trained large language models (LLMs) like OpenAI’s GPT with external knowledge sources stored in vector databases such as Milvus and Zilliz Cloud, allowing for more accurate, contextually relevant, and up-to-date response generation. A RAG pipeline usually consists of four basic components: a vector database, an embedding model, an LLM, and a framework.

Key Components We'll Use for This RAG Chatbot

This tutorial shows you how to build a simple RAG chatbot in Python using the following components:

Haystack: An open-source Python framework designed for building production-ready NLP applications, particularly question answering and semantic search systems. Haystack excels at retrieving information from large document collections through its modular architecture that combines retrieval and reader components. Ideal for developers creating search applications, chatbots, and knowledge management systems that require efficient document processing and accurate information extraction from unstructured text.
Pgvector: an open-source extension for PostgreSQL that enables efficient storage and querying of high-dimensional vector data, essential for machine learning and AI applications. Designed to handle embeddings, it supports fast approximate nearest neighbor (ANN) searches using algorithms like HNSW and IVFFlat. Since it is just a vector search add-on to traditional search rather than a purpose-built vector database, it lacks scalability and availability and many other advanced features required by enterprise-level applications. Therefore, if you prefer a much more scalable solution or hate to manage your own infrastructure, we recommend using Zilliz Cloud, which is a fully managed vector database service built on the open-source Milvus and offers a free tier supporting up to 1 million vectors.)
Amazon Bedrock Claude 3.7 Sonnet: A versatile multimodal AI model designed for enterprise applications, excelling in complex reasoning, code generation, and natural language tasks. Known for its balance of speed, accuracy, and cost-efficiency, it is ideal for data analysis, content creation, and scalable automation within AWS-integrated environments.
Cohere embed-english-light-v3.0: A lightweight, efficient embedding model designed to convert English text into high-dimensional vector representations. Excelling in speed and scalability, it balances accuracy with low computational demands, making it ideal for semantic search, text clustering, and retrieval-augmented applications in resource-constrained environments.

By the end of this tutorial, you’ll have a functional chatbot capable of answering questions based on a custom knowledge base.

Note: Since we may use proprietary models in our tutorials, make sure you have the required API key beforehand.

Step 1: Install and Set Up Haystack

import os
import requests

from haystack import Pipeline
from haystack.components.converters import MarkdownToDocument

from haystack.components.preprocessors import DocumentSplitter
from haystack.components.writers import DocumentWriter

Step 2: Install and Set Up Amazon Bedrock Claude 3.7 Sonnet

Amazon Bedrock is a fully managed service that makes high-performing foundation models from leading AI startups and Amazon available through a unified API. You can choose from various foundation models to find the one best suited for your use case.

To use LLMs on Amazon Bedrock for text generation together with Haystack, you need to initialize an AmazonBedrockGenerator with the model name, the AWS credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_DEFAULT_REGION) should be set as environment variables, be configured as described above or passed as Secret arguments. Note, make sure the region you set supports Amazon Bedrock.

Now, let's start installing and setting up models with Amazon Bedrock.

pip install amazon-bedrock-haystack

from haystack_integrations.components.generators.amazon_bedrock import AmazonBedrockGenerator

aws_access_key_id="..."
aws_secret_access_key="..."
aws_region_name="eu-central-1"

generator = AmazonBedrockGenerator(model="anthropic.claude-3-7-sonnet-20250219-v1:0")

Step 3: Install and Set Up Cohere embed-english-light-v3.0

To start using this integration with Haystack, install it with:

pip install cohere-haystack

from haystack import Document
from haystack_integrations.components.embedders.cohere.document_embedder import CohereDocumentEmbedder
from haystack_integrations.components.embedders.cohere.text_embedder import CohereTextEmbedder

text_embedder = CohereTextEmbedder(model="embed-english-light-v3.0")
document_embedder = CohereDocumentEmbedder(model="embed-english-light-v3.0")

Step 4: Install and Set Up Pgvector

To quickly set up a PostgreSQL database with pgvector, you can use Docker:

docker run -d -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres ankane/pgvector

To use pgvector with Haystack, install the pgvector-haystack integration:

pip install pgvector-haystack

import os
from haystack_integrations.document_stores.pgvector import PgvectorDocumentStore
from haystack_integrations.components.retrievers.pgvector import PgvectorEmbeddingRetriever

os.environ["PG_CONN_STR"] = "postgresql://postgres:postgres@localhost:5432/postgres"

document_store = PgvectorDocumentStore()
retriever = PgvectorEmbeddingRetriever(document_store=document_store)

Step 5: Build a RAG Chatbot

Now that you’ve set up all components, let’s start to build a simple chatbot. We’ll use the Milvus introduction doc as a private knowledge base. You can replace it your own dataset to customize your RAG chatbot.

url = 'https://raw.githubusercontent.com/milvus-io/milvus-docs/refs/heads/v2.5.x/site/en/about/overview.md'
example_file = 'example_file.md'
response = requests.get(url)
with open(example_file, 'wb') as f:
    f.write(response.content)
file_paths = [example_file]  # You can replace it with your own file paths.

indexing_pipeline = Pipeline()
indexing_pipeline.add_component("converter", MarkdownToDocument())
indexing_pipeline.add_component("splitter", DocumentSplitter(split_by="sentence", split_length=2))
indexing_pipeline.add_component("embedder", document_embedder)
indexing_pipeline.add_component("writer", DocumentWriter(document_store))
indexing_pipeline.connect("converter", "splitter")
indexing_pipeline.connect("splitter", "embedder")
indexing_pipeline.connect("embedder", "writer")
indexing_pipeline.run({"converter": {"sources": file_paths}})

# print("Number of documents:", document_store.count_documents())
  
question = "What is Milvus?"  # You can replace it with your own question.

retrieval_pipeline = Pipeline()
retrieval_pipeline.add_component("embedder", text_embedder)
retrieval_pipeline.add_component("retriever", retriever)
retrieval_pipeline.connect("embedder", "retriever")

retrieval_results = retrieval_pipeline.run({"embedder": {"text": question}})

# for doc in retrieval_results["retriever"]["documents"]:
#     print(doc.content)
#     print("-" * 10)

from haystack.utils import Secret
from haystack.components.builders import PromptBuilder

retriever = PgvectorEmbeddingRetriever(document_store=document_store) 
 text_embedder = CohereTextEmbedder(model="embed-english-light-v3.0")

prompt_template = """Answer the following query based on the provided context. If the context does
                     not include an answer, reply with 'I don't know'.\n
                     Query: {{query}}
                     Documents:
                     {% for doc in documents %}
                        {{ doc.content }}
                     {% endfor %}
                     Answer: 
                  """

rag_pipeline = Pipeline()
rag_pipeline.add_component("text_embedder", text_embedder)
rag_pipeline.add_component("retriever", retriever)
rag_pipeline.add_component("prompt_builder", PromptBuilder(template=prompt_template))
rag_pipeline.add_component("generator", generator)
rag_pipeline.connect("text_embedder.embedding", "retriever.query_embedding")
rag_pipeline.connect("retriever.documents", "prompt_builder.documents")
rag_pipeline.connect("prompt_builder", "generator")

results = rag_pipeline.run({"text_embedder": {"text": question}, "prompt_builder": {"query": question},})
print('RAG answer:\n', results["generator"]["replies"][0])

Optimization Tips

As you build your RAG system, optimization is key to ensuring peak performance and efficiency. While setting up the components is an essential first step, fine-tuning each one will help you create a solution that works even better and scales seamlessly. In this section, we’ll share some practical tips for optimizing all these components, giving you the edge to build smarter, faster, and more responsive RAG applications.

Haystack optimization tips

To optimize Haystack in a RAG setup, ensure you use an efficient retriever like FAISS or Milvus for scalable and fast similarity searches. Fine-tune your document store settings, such as indexing strategies and storage backends, to balance speed and accuracy. Use batch processing for embedding generation to reduce latency and optimize API calls. Leverage Haystack's pipeline caching to avoid redundant computations, especially for frequently queried documents. Tune your reader model by selecting a lightweight yet accurate transformer-based model like DistilBERT to speed up response times. Implement query rewriting or filtering techniques to enhance retrieval quality, ensuring the most relevant documents are retrieved for generation. Finally, monitor system performance with Haystack’s built-in evaluation tools to iteratively refine your setup based on real-world query performance.

pgvector optimization tips

To optimize pgvector in a Retrieval-Augmented Generation (RAG) setup, consider indexing your vectors using GiST or IVFFlat to significantly speed up search queries and improve retrieval performance. Make sure to leverage parallelization for query execution, allowing multiple queries to be processed simultaneously, especially for large datasets. Optimize memory usage by tuning the vector storage size and using compressed embeddings where possible. To further enhance query speed, implement pre-filtering techniques to narrow down search space before querying. Regularly rebuild indexes to ensure they are up to date with any new data. Fine-tune vectorization models to reduce dimensionality without sacrificing accuracy, thus improving both storage efficiency and retrieval times. Finally, manage resource allocation carefully, utilizing horizontal scaling for larger datasets and offloading intensive operations to dedicated processing units to maintain responsiveness during high-traffic periods.

AmazonBedrock Claude 3.7 Sonnet optimization tips

Optimize Claude 3.7 Sonnet in RAG by preprocessing data to remove noise, using semantic chunking (512-1024 tokens) with overlap for context continuity. Adjust temperature (0.3–0.6 balances creativity) and max_tokens to control response length. Structure prompts with clear instructions and retrieval context placement. Cache frequent queries and embeddings to reduce latency. Apply metadata filters during retrieval to improve relevance. Monitor precision/recall via built-in metrics and tweak retrieval thresholds. Use batch inference for cost efficiency and parallelize document processing. Test varying chunk sizes, top-k retrievals, and system prompts to balance accuracy, speed, and operational costs.

Cohere embed-english-light-v3.0 optimization tips

To optimize Cohere embed-english-light-v3.0 in RAG, ensure input text is clean and concise by removing redundant whitespace, special characters, or irrelevant metadata. Use batch processing for embeddings to reduce API calls and latency. Align chunk sizes with the model’s 512-token limit, splitting longer texts into coherent segments. Cache frequent or static embeddings to save costs. Fine-tune retrieval scoring (e.g., cosine similarity) to match your data distribution, and pre-filter low-relevance documents using metadata to reduce computational overhead. Regularly validate embedding quality against domain-specific benchmarks.

By implementing these tips across your components, you'll be able to enhance the performance and functionality of your RAG system, ensuring it’s optimized for both speed and accuracy. Keep testing, iterating, and refining your setup to stay ahead in the ever-evolving world of AI development.

RAG Cost Calculator: A Free Tool to Calculate Your Cost in Seconds

Estimating the cost of a Retrieval-Augmented Generation (RAG) pipeline involves analyzing expenses across vector storage, compute resources, and API usage. Key cost drivers include vector database queries, embedding generation, and LLM inference.

RAG Cost Calculator is a free tool that quickly estimates the cost of building a RAG pipeline, including chunking, embedding, vector storage/search, and LLM generation. It also helps you identify cost-saving opportunities and achieve up to 10x cost reduction on vector databases with the serverless option.

Calculate your RAG cost now.

Calculate your RAG cost

What Have You Learned?

By diving into this tutorial, you’ve unlocked the power of combining cutting-edge tools to build a fully functional RAG system! You’ve seen how Haystack acts as the backbone, seamlessly orchestrating the flow of data between components with its intuitive pipelines. Paired with Pgvector, a robust vector database, you learned to store and retrieve embeddings efficiently, ensuring your system can quickly access relevant information. The magic of Cohere’s embed-english-light-v3.0 model transformed raw text into rich numerical representations, capturing the nuances of language so your RAG system understands context like never before. Then, Amazon Bedrock’s Claude 3 Sonnet stepped in as the brain, synthesizing retrieved data into coherent, human-like responses—proving how powerful LLMs are at turning information into actionable insights. Together, these tools form a dynamic pipeline that bridges data retrieval and generative intelligence, empowering you to create applications that feel almost alive with understanding!

But this tutorial didn’t stop there! You also discovered pro tips for optimizing performance, like tuning chunk sizes for embeddings and balancing speed with accuracy in retrieval. And who could forget the free RAG cost calculator? Now you can estimate expenses upfront, making smart, budget-friendly choices without sacrificing quality. Imagine the possibilities ahead—personalized chatbots, research assistants, or even AI-driven knowledge hubs—all built on the foundation you’ve mastered here. The tools are in your hands, and the roadmap is clear. So why wait? Start experimenting, tweak those pipelines, and watch your ideas come to life. Every line of code you write brings us closer to a future where AI isn’t just a tool but a trusted collaborator. Your journey into RAG is just beginning—build boldly, optimize fearlessly, and let your creativity reshape what’s possible! 🚀

Further Resources

🌟 In addition to this RAG tutorial, unleash your full potential with these incredible resources to level up your RAG skills.

How to Build a Multimodal RAG | Documentation
How to Enhance the Performance of Your RAG Pipeline
Graph RAG with Milvus | Documentation
How to Evaluate RAG Applications - Zilliz Learn
Generative AI Resource Hub | Zilliz

We'd Love to Hear What You Think!

We’d love to hear your thoughts! 🌟 Leave your questions or comments below or join our vibrant Milvus Discord community to share your experiences, ask questions, or connect with thousands of AI enthusiasts. Your journey matters to us!

If you like this tutorial, show your support by giving our Milvus GitHub repo a star ⭐—it means the world to us and inspires us to keep creating! 💖