Managed knowledge bases change the operating model for RAG by collapsing ingestion, parsing, retrieval, embeddings, re-ranking, and model selection into a single service boundary. For enterprise teams, the immediate value is less about novelty and more about removing pipeline assembly work: fewer custom connectors to maintain, fewer orchestration layers to secure, and fewer moving parts to observe when retrieval quality slips.
The architectural trade-off is control versus standardization. The serviceโs defaults can accelerate first deployment, but teams still need to think carefully about data segmentation, connector scope, and how permissions are inherited from source systems. In practice, the main design question becomes whether one managed knowledge base can safely serve multiple teams or whether workload, policy, and tenancy boundaries should remain separated to reduce blast radius and simplify governance.
Integration is the second-order benefit. Native exposure through AgentCore Gateway and MCP-compatible clients means the knowledge base can sit inside broader agent workflows without bespoke glue code. That reduces integration friction, but it also shifts attention to runtime controls: observability, retrieval evaluation, and permission management become part of the operational contract rather than an afterthought. For platform teams, that is useful because it aligns the knowledge layer with existing control planes instead of creating a parallel one.
Model flexibility remains important. Because infrastructure is separated from model choice, teams can tune embeddings, re-ranking, and generation independently as requirements evolve. That helps avoid lock-in at the retrieval layer while preserving the ability to balance latency, accuracy, and cost. The result is a more maintainable enterprise pattern for RAG, especially where content sources, compliance rules, and query complexity are all changing at once.
- Connecting to enterprise data โ Enterprise knowledge lives across disparate systems with different content types, access control lists, and document formats. Building and maintaining custom connectors for each source adds complexity that slows down development.
- Optimizing RAG accuracy โ Best practices for retrieval-augmented generation keep evolving. Developers need to experiment with different parsing strategies, chunking approaches, embedding models, and agentic retrieval behaviors to get accurate answers from their data.
- Managing infrastructure at scale โ Organizations need to serve large knowledge bases with millions of documents, or manage thousands of smaller knowledge bases across teams. Both patterns require reliable infrastructure, security enforcement, and cost control.
- Native data connectors โ Six pre-built ingestion connectors that natively pull enterprise data and permissions from SaaS applications, eliminating the overhead developers face in managing application-specific requirements. At launch, we support Amazon S3, SharePoint, Confluence, Web Crawler, Google Drive, and OneDrive.
- Smart Parsing โ Different content types and sources require different approaches to achieve accurate retrieval. Smart Parsing handles this complexity automatically, selecting the right parsing strategy for each data type and connector to provide the highest accuracy for your agents.
- Agentic Retriever โ Optimized for complex queries that require multiturn, multihop retrieval within a single knowledge base or across multiple knowledge bases. Agentic Retriever automatically infers end-user intent and draws relevant context from institutional knowledge spread across data sources and modalities.
Creating a Managed Knowledge Base is straightforward. Navigate to the Amazon Bedrock AgentCore console or the Amazon Bedrock console, open the Knowledge Bases page, and choose Create Managed KB. The experience is the same in both consoles.
One of the key challenges in building knowledge bases is preparing diverse data types for accurate retrieval. Once you point Managed Knowledge Base at your data sources, Smart Parsing automatically determines the optimal parsing strategy for each data type and connector, no extra configuration is required. Smart Parsing combines multiple techniques:
- Connector-specific data models โ Optimized handling for each data source. For example, the Web Crawler connector preserves HTML structure including embedded images and tables, ensuring rich content is not dropped during ingestion. SharePoint connectors maintain document hierarchy and relationships between files.
- Multimodal processing โ Automatic detection and processing of different content types within documents. The system identifies bounding boxes in documents, then sends them to foundation models for data extraction, captioning, and scene description in video files.
- Optimized chunking โ Smart Parsing leverages foundation models to understand document structure and extract meaningful content, ensuring that complex documents with mixed formats are properly indexed. Intelligent defaults balance retrieval accuracy with performance based on document type and content structure, while advanced users can customize chunking strategies when needed.
After your data is ingested, you can start querying your knowledge base. Generative AI applications often struggle with complex user queries that require reasoning, recursive multi-step retrieval, and intermediate evaluations of results. Consider a user asking two related questions: โWhat is the cloud infrastructure budget for the ML platform team?โ and โDoes our expense policy allow prepaying annual commitments?โ A single retrieval step might surface documents about the ML platform team but fail to connect the budget information with the expense policy needed to fully answer the question.
Amazon Bedrock Managed Knowledge Base seamlessly integrates with AgentCore Gateway as a native target type. This integration eliminates the need for manual integration and provides built-in observability, policy enforcement, and automatic permission management. You can navigate to the Amazon Bedrock AgentCore console or SDK and create an AgentCore Gateway or select an existing one. When adding targets to your gateway, you will find Knowledge Base as a new pre-built target type alongside other options such as MCP server, Lambda ARN, REST API, and other integrations. Simply select your knowledge base ID to expose it through the gateway:
Amazon Bedrock Managed Knowledge Base preserves the flexibility developers expect from Amazon Bedrock. Every foundation model available on Bedrock can power the generation step, and developers can select from different embedding and re-ranking models to optimize retrieval for their specific use case, enabling teams to fine-tune accuracy and cost-performance without changing infrastructure. Unlike managed solutions that lock you into specific model providers, Amazon Bedrock Managed Knowledge Base separates the infrastructure management (connectors, parsing, storage, retrieval orchestration) from model selection. This means you can:
- Take advantage of the latest models โ Adopt the latest embedding, re-ranking, and foundation models as they become available to improve accuracy, latency, and cost for your application without rebuilding your RAG pipeline.
- Optimize for price-performance โ Choose smaller, faster models for simple queries and more capable models for complex reasoning tasks, all using the same knowledge base infrastructure.
- Use Bedrock embedding models โ While Smart Parsing provides optimized defaults, you can configure Bedrock embedding models when your domain requires specialized semantic understanding.
- Maintain consistency with existing applications โ If youโre already using Bedrock Knowledge Bases APIs (
Retrieve,StartIngest,StopIngest,IngestKnowledgeBaseDocuments), Managed Knowledge Base uses the same APIs, so migration requires no code changes, just point to the new knowledge base ID.
Amazon Bedrock Managed Knowledge Base is available today in the US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney, Tokyo), Europe (Dublin, Frankfurt, London), and AWS GovCloud (US-West) Regions. For Regional availability and future roadmap, visit AWS Capabilities by Region. With Bedrock Managed Knowledge Base, you pay for what you use with no upfront commitments. Pricing is based on two dimensions: the size of indexed data stored and the number of retrievals performed (on-demand). For detailed pricing information, visit the Original Postricing/" shape="rect">Amazon Bedrock pricing page. Bedrock is also a part of the AWS Free Tier that new AWS customers can use to get started at no cost and explore key AWS services. These capabilities work with any open source framework such as CrewAI, LangGraph, LlamaIndex, and Strands Agents, and with any foundation model. Bedrock services can be used together or independently, and you can get started using your favorite AI-assisted development environment with the AgentCore open source MCP server. To learn more and get started quickly, visit the Bedrock Knowledge Bases Developer Guide. Daniel Abib ย Updated on June 19, 2026 โ Fixed correct screenshots to create a new Managed KB.
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.

