{"id":540,"date":"2024-06-26T13:39:51","date_gmt":"2024-06-26T20:39:51","guid":{"rendered":"http:\/\/184.72.63.26\/?p=540"},"modified":"2024-10-23T20:05:22","modified_gmt":"2024-10-24T03:05:22","slug":"implement-rag-with-aws-bedrock-and-mongodb-atlas","status":"publish","type":"post","link":"https:\/\/www.wallacel.com\/index.php\/2024\/06\/26\/implement-rag-with-aws-bedrock-and-mongodb-atlas\/","title":{"rendered":"Implement RAG with AWS Bedrock and MongoDB Atlas"},"content":{"rendered":"\n

While exploring AI use cases, I discovered Retrieval-Augmented Generation (RAG)<\/strong>. This technique in natural language processing merges information retrieval with text generation. By doing so, it boosts the abilities of language models to generate responses not just from their pre-trained knowledge but also by sourcing information from contextually relevant documents, leading to more accurate, precise, and timely replies. <\/p>\n\n\n\n

In this article, I will experiment with building a generative AI agent using AWS Bedrock to help me in comparing different models of plug-in hybrid SUV available in the market . I already short-listed a few car makers’ models and I want the agent to tailor its responses from these models only. To do so, I will build a knowledge base and populate it with information like catalogues and brochures of these SUVs, in hope that the agent can help me to make a better buying decision.<\/p>\n\n\n\n

How RAG works<\/h2>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Large Language Model (LLM) are trained on vast volumes of data and use billions of parameters to generate output for tasks like answering questions. RAG optimizes LLM output by referencing a knowledge base outside of its training data source before generating a response.<\/p>\n\n\n\n

Data Ingestion:<\/strong> With AWS Bedrock, you build a knowledge base by populating it with external data (e.g. documents uploaded to a S3 bucket). These documents are split into chunks, converted to embeddings, and stored within a vector database (e.g. Mongodb Atlas).<\/p>\n\n\n\n

Information Retrieval:<\/strong> When user asks a question, the embedded foundation model in AWS Bedrock utilizes the vector index in the database to find the most relevant documents that match the query. The model then uses these information with its training data to generate a more relevant and up-to-date response for the user.<\/p>\n\n\n\n

Foundation Models<\/h2>\n\n\n\n

AWS Bedrock supports a range of foundation models<\/a> from Amazon’s own Titan models to other AI companies and in this setup I will try with both the Titan Embeddings G1 – Text<\/strong> and Claude 3 by Anthropic. <\/strong>They are both ideal for open-ended text generation and conversation chat, and supporting RAG. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

To request access for models, go to AWS Bedrock console and choose Model access, and select the models you want to try.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Data Source for Knowledge Base<\/h2>\n\n\n\n

To prepare the data, I download brochures and catalogues of different car makers’ PHEV SUVs that are available in the market with similar price range, and upload them to a S3 bucket. AWS Bedrock knowledge base supports the following document file formats:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

I create a new S3 bucket for storing my documents.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Create a AWS Bedrock Knowledge Base<\/h2>\n\n\n\n

To create a knowledge base, go to AWS Bedrock console and choose Knowledge base
(Note: You must not sign in as root as it cannot create a knowledge base)<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Use the S3 bucket just created as the data source<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Now choose ‘Titan Embeddings G1 – Text<\/strong>‘ as the embeddings model for converting the documents in S3 into chunks in our vector database. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Note: AWS introduced the newer Titan Text Embeddings v2 model in April 2024<\/a> and states that it is optimized for RAG, however when I tried to use this model, it failed to create the vector store with using MongoDB Atlas.<\/p>\n\n\n\n

AWS Bedrock supports a wide range of vector databases including its own Amazon OpenSearch, but in this setup I will use MongoDB Atlas for its quick, easy deployment and optimized performance.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Sign Up for MongoDB Atlas<\/h2>\n\n\n\n

Login or Signup<\/a> an account to MongoDB Atlas for an account. Create a MongoDB Atlas cluster with a M10<\/strong> configuration (M0 free cluster will not work) and setup user and network access.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Under Database Access, add a database user with read and write access to the database.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Under Network Access, add an entry to allow access from anywhere.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Create a database and collection in MongoDB Atlas cluster<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Under Atlas Search, create a vector search index and select Altas Vector Search<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Select the database and collection where the embeddings are stored, then enter the following JSON in the index definition. These fields will need to match the fields in the AWS Bedrock knowledge base configuration.<\/p>\n\n\n\n

{\n  \"fields\": [\n    {\n      \"numDimensions\": 1536,\n      \"path\": \"bedrock_embedding\",\n      \"similarity\": \"cosine\",\n      \"type\": \"vector\"\n    },\n    {\n      \"path\": \"bedrock_metadata\",\n      \"type\": \"filter\"\n    },\n    {\n      \"path\": \"bedrock_text_chunk\",\n      \"type\": \"filter\"\n    }\n  ]\n}<\/code><\/pre>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Now that our vector database is created, we want to store our MongoDB database username and password to AWS Secrets Manager for enhanced security. Go to Secrets Manager console and choose ‘Store a new secret’.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Let’s go back to AWS Bedrock console and continue the MongoDb configuration setup. <\/p>\n\n\n\n
    \n
  • Hostname: <mongodb cluster hostname><\/em><\/li>\n\n\n\n
  • Database name:  bedrock_db<\/strong><\/li>\n\n\n\n
  • Collection name: bedrock<\/strong><\/li>\n\n\n\n
  • Credentials secret ARN: Use the ARN from database credentials in AWS Secrets Manager<\/em><\/li>\n\n\n\n
  • Vector search index name: vector_index<\/strong><\/li>\n\n\n\n
  • Vector embedding field path: bedrock_embedding<\/strong><\/li>\n\n\n\n
  • Text field path: bedrock_text_chunk<\/strong><\/li>\n\n\n\n
  • Metadata field path: bedrock_metadata<\/strong><\/li>\n<\/ul>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Hostname<\/strong> can be obtained from the connection string in MongoDB Atlas’s Cluster Overview->Connect->Shell<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    It takes a few minutes to create the knowledge base. <\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    To ensure our data source remains current, we need to synchronize it either periodically or each time new documents are uploaded to the S3 bucket.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Create a AWS Bedrock Agent<\/h2>\n\n\n\n
    In order to query the knowledge base, we need to create a Bedrock Agent. Go to AWS Bedrock console, choose Agents and select Create Agent. I want the agent to answer my questions like an expert in the automotive industry and help me choose the best SUV model.<\/p>\n\n\n\n
      \n
    • Select model: Anthropic Claude 3 Haiku<\/strong><\/li>\n\n\n\n
    • Instructions for agent: You are an automotive expert. Your role is to help customers to understand and choose the best plug in hybrid model auto in the market<\/strong><\/li>\n<\/ul>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      Add the knowledge base containing the catalogues and brochures to the agent.<\/p>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      Now I can ask the agent questions like ‘Which model has the fastest charging time?<\/strong><\/em>‘ or ‘Which suv has the longest ev driving range?<\/strong><\/em>‘<\/p>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      <\/p>\n\n\n\n
      Building a RAG Chatbot<\/h2>\n\n\n\n
      With Amazon Bedrock API, I can make a chatbot and embed it to a website and interact with my knowledge base. This can be useful for a variety of use cases like providing customer service with product specific help to customers, or legal advice by retrieving relevant case laws, statutes, and legal documents. <\/p>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      Clean Up<\/h2>\n\n\n\n
      When we are done experimenting with RAG, we can either pause the MongoDB Atlas cluster to save some running cost, or terminate it completely.<\/p>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      Conclusion<\/h2>\n\n\n\n
      This article demonstrates how to easily access AI models like Amazon Titan and Antropic Claude 3 using AWS Bedrock and MongoDB Atlas. Thank you for reading, and I hope you found it helpful.<\/p>\n","protected":false},"excerpt":{"rendered":"
      While exploring AI use cases, I discovered Retrieval-Augmented Generation (RAG). This technique in natural language processing merges information retrieval with text generation. By doing so, it boosts the abilities of language models to generate responses not just from their pre-trained knowledge but also by sourcing information from contextually relevant documents, leading to more accurate, precise, […]<\/p>\n","protected":false},"author":1,"featured_media":611,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[35,38,36,37,34],"class_list":["post-540","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aws","tag-bedrock","tag-claude-3","tag-generative-ai","tag-mongodb-atlas","tag-rag"],"_links":{"self":[{"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/posts\/540","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/comments?post=540"}],"version-history":[{"count":27,"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/posts\/540\/revisions"}],"predecessor-version":[{"id":1019,"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/posts\/540\/revisions\/1019"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/media\/611"}],"wp:attachment":[{"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/media?parent=540"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/categories?post=540"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wallacel.com\/index.php\/wp-json\/wp\/v2\/tags?post=540"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}