# Grounding options for AgentCore agents (August 2026)

| Option | Status | What it does | Wire today? |
| ------ | ------ | ------------ | ----------- |
| **Amazon Bedrock Managed Knowledge Base** (AgentCore) | **GA** (Jun 17, 2026) | Managed RAG: connectors (S3, SharePoint, Confluence, Google Drive, OneDrive, Web Crawler), hybrid + agentic retrieval, Gateway target | **Yes** — primary ship-now path for unstructured grounding |
| **Bedrock Knowledge Bases (classic)** | GA | You manage more of the retrieval stack; still valid for existing KB estates | Yes — migrate or dual-run; do not rip-and-replace blindly |
| **AgentCore Memory** | GA | Session + long-term user/conversation state — not a document library | Yes — complementary to KB, not a substitute |
| **AgentCore Web Search** | GA | Cited web grounding inside Gateway / account boundary | Yes — for live public facts; not for private runbooks |
| **AWS Context** (org knowledge graph) | **Coming soon** | Identity-aware knowledge graph over structured + domain relationships (Iceberg-portable metadata) | **No** — roadmap signal only; design a seam, do not block shipping |

## Opinionated default

Ground production agents on **Managed Knowledge Base + Gateway** now. Keep Memory for conversational state. Track AWS Context for org-wide relationship graphs — do not invent API calls against a service that is not GA.