← Back
AWS ML Blog

Build agentic retrieval on a Managed Amazon Bedrock Knowledge Base with CDK

•31 min read•
#agents#deployment#bedrock#amazon
Level:Advanced
For:AI Engineers
✦TL;DR

This article demonstrates building enterprise‑grade agentic retrieval using Amazon Bedrock’s new Managed Knowledge Base (type MANAGED) together with the AWS Cloud Development Kit (CDK). By leveraging the AgenticRetrieveStream API and AgentCore’s MCP‑exposed tool, the solution routes queries across two knowledge bases, performs multi‑turn, tool‑driven retrieval, and returns synthesized, cited answers while provisioning observability via seven‑layer CloudWatch dashboards and on‑demand plus continuous evaluation. Engineers can now deploy a fully managed, observable agentic RAG pipeline without provisioning OpenSearch Serverless resources.

⚡ Key Takeaways

  • Managed Knowledge Base type is **MANAGED**, handling ingestion, storage, indexing, and retrieval internally.
  • The architecture uses **AgenticRetrieveStream API** and **AgentCore** to provide multi‑turn planning and MCP‑exposed retrieval tools.
  • Observability is built‑in with **two Amazon CloudWatch dashboards** covering **seven layers of telemetry** and supports both **on‑demand and continuous evaluation**.
  • Integration is done via **AWS CDK**, provisioning the knowledge bases, agent runtime, and dashboards as CDK stacks.
  • The solution replaces the need for an **OpenSearch Serverless collection and index**, eliminating OCU costs.
💡 Why It Matters

Engineers can ship production‑ready, observable agentic RAG systems on Bedrock without managing search infrastructure, reducing operational complexity and cost while enabling richer multi‑source query handling.

✅ Practical Steps

  1. Use AWS CDK to define a stack that creates a **Managed Amazon Bedrock Knowledge Base** (type MANAGED) and configures **AgentCore** with the **AgenticRetrieveStream** tool.
  2. Deploy the CDK stack to provision the **CloudWatch dashboards** that capture the seven telemetry layers and enable both on‑demand and continuous evaluation.
  3. Route queries through the agent runtime, which selects the appropriate knowledge base and performs multi‑turn retrieval via the MCP‑exposed tool.

Want the full story? Read the original article.

Read on AWS ML Blog ↗

More like this

Introducing workload recovery and expanded infrastructure checks on Amazon SageMaker HyperPod

AWS ML Blog•#deployment

Introducing Unity Gateway Insights

Databricks Blog•#deployment

Introducing Gemini 4 Neon

Google DeepMind•#llm

DaisyRose-27B: Pushing the Frontier of Post-Training Efficiency

Hugging Face Blog•#llm

EXPLORE AI NEWS

Daily hand-picked stories on LLMs, RAG, agents and production AI — curated for engineers who ship.

BROWSE NEWS

GET THE WEEKLY DIGEST

Join engineers getting the Monday signal-over-noise AI breakdown. No spam, unsubscribe anytime.

LEARN AI ENGINEERING

Curated courses, research papers, repos and tutorials built for engineers leveling up in AI.

START LEARNING