AWS Expands Bedrock AgentCore as Agent Knowledge Retrieval Becomes Managed Infrastructure
AWS announced Managed Knowledge Base, Web Search on AgentCore and AgentCore harness general availability on June 17, 2026.
AWS announced several Amazon Bedrock AgentCore updates at AWS Summit New York on June 17, 2026. The releases include Managed Knowledge Base, Web Search on AgentCore, AgentCore harness general availability, policy integrations and optimization capabilities, showing that production AI agents are becoming managed infrastructure around knowledge, execution and governance.
Key takeaways
AWS announced multiple Amazon Bedrock AgentCore updates during AWS Summit New York on June 17, 2026. The main releases include Amazon Bedrock Managed Knowledge Base, Web Search on AgentCore, AgentCore harness general availability and new policy and optimization capabilities.
Managed Knowledge Base is designed to reduce the work required to build enterprise RAG pipelines. It brings together connectors, parsing, storage, retrieval, embeddings, reranking and model selection as a managed capability. Web Search on AgentCore lets agents retrieve current web information inside the AWS environment and return source URLs, snippets, titles and publication dates.
For ENHE AI readers, the practical lesson is that agent selection should include knowledge access, source traceability, permission controls, account isolation, observability, cost management and recovery options. Production AI agents are becoming infrastructure, not just model prompts.
What this means for everyday users
ENHE users should use this as an AI agent platform checklist. Cloud, local and workflow automation tools should be evaluated by source traceability, knowledge connectors, tool permissions, account security, observability, cost controls and failure recovery.
Tools you may use
Related reading
IskayPet Connects SharePoint to a Managed Knowledge Base: Validate Permissions Before Answers
AWS published IskayPet’s corporate knowledge assistant case study on October 22, 2026. The system connects Amazon Bedrock Managed Knowledge Bases to existing SharePoint repositories and answers cited questions across retail operations, veterinary care, onboarding, and procurement in four languages and three countries. This article turns the case into a practical acceptance plan for knowledge owners. It checks source scope, inherited permissions, hybrid retrieval, duplicate and fragment removal, citation quality, feedback, and token cost before expansion. It also separates the customer’s reported production results from what another organization should expect. A managed retrieval stack reduces infrastructure work, but it does not remove content ownership, access reviews, evaluation datasets, or human verification of important answers.
Bayer Shares Production Lessons From 22 Specialist Agents: HTTP Success Is Not Task Success
AWS published Bayer Crop Science’s Agentic Decision Engine case study on October 23, 2026. The production system runs 22 specialist agents over governed analytics workflows, models, logs, and visualization tools. This article turns the architecture into five reusable acceptance checks for enterprise agent teams: persist the state needed to resume work, define identity and authorization at every boundary, scope each agent’s tool catalog, distinguish transport success from task success, and release to a gated group before broader access. It also explains why Bayer’s adoption and resolution figures are evidence about one implementation, not promises for another organization. The focus is operational proof, least privilege, rollback, and observable outcomes rather than prompt polish.
Nine-Stage AI Agent Evaluation Checklist: From First Commit to Production Drift
AWS published a nine-stage production AI-agent evaluation framework built around Amazon Bedrock AgentCore on October 16, 2026. It follows an agent from defining quality and comparing experiments through merge checks, deployment gates, canary scoring, adversarial testing, drift detection, live pulse monitoring, and feedback-driven improvement. The framework evaluates five dimensions—safety, quality, performance, cost, and operational control—at tool, individual-agent, and multi-agent levels. This durable guide converts the public framework into a vendor-neutral checklist for ordinary teams, with minimum evidence, ownership, and stop conditions designed to catch soft failures where latency and uptime remain normal while answer quality quietly declines over time.
Three agents produce a track together on persistent AgentCore runtimes
On September 30, AWS published a hands-on example in which three specialized agents collaborate to render, generate, and clear a music track on Amazon Bedrock AgentCore Runtime Instances. The sample colocates agents on one GPU-backed instance, gives them persistent shared storage, and uses a shared session ID for handoffs and resumable work. AWS says Runtime Instances can host agents built with different frameworks; the walkthrough uses Strands and a file-backed session manager. It is an implementation example, not evidence of unattended production readiness. Deploying it provisions cloud resources such as runtimes, storage, and container repositories, so teams should estimate ongoing charges, narrow IAM permissions, and test cleanup and failure isolation before adapting the pattern.
OpenAI combines legal search, specialized instructions, and governance controls in Astra for Law
OpenAI introduced Astra for Law on September 17, combining GPT-6 Astra with a legal search index, instructions for legal analysis and writing, and an ecosystem of professional plugins. OpenAI says the index searches United States case law, statutes, regulations, court rules, and administrative decisions across more than 230 million URLs. On 200 questions from a private Vals AI Legal Research Bench validation set, the complete setup passed an overall correctness check on 54.0% of questions, versus 38.7% for GPT-6 Astra with web search alone at the highest reasoning effort. Initial access is limited to selected firms, with API availability planned later, and lawyers must still verify authority and jurisdiction.
AWS shows how AgentCore can deliver the same MCP tools and interactive widgets across compatible AI hosts
AWS published a technical walkthrough for running MCP Apps on Amazon Bedrock AgentCore on September 11. In the reference architecture, an AI host discovers MCP tools and resources, invokes a tool through WAF and AgentCore Gateway, and receives structured content from business logic implemented with Lambda and DynamoDB. When a tool points to a resource URI, the host reads self-contained widget HTML and renders it in a sandboxed iframe with the structured result injected through the MCP Apps lifecycle. AWS presents MCP Apps as a host-agnostic standard, so one server can provide the same tools and widgets to compatible AI hosts. The production guidance still requires strict argument validation, trust-boundary controls, caller restrictions, monitoring, and cost review.
Summary
Amazon Bedrock AgentCore's new capabilities show that production AI agents need managed knowledge, execution, governance and optimization infrastructure, not only stronger models.
FAQ
What is this ENHE AI article about?
AWS announced several Amazon Bedrock AgentCore updates at AWS Summit New York on June 17, 2026. The releases include Managed Knowledge Base, Web Search on AgentCore, AgentCore harness general availability, policy integrations and optimization capabilities, showing that production AI agents are becoming managed infrastructure around knowledge, execution and governance.
Why is this AI update worth watching?
AWS announced new Amazon Bedrock AgentCore capabilities on June 17, 2026. Managed Knowledge Base packages enterprise RAG infrastructure into a managed capability. Web Search on AgentCore gives agents current web grounding while keeping queries inside the AWS environment. AgentCore harness is generally available and wraps runtime, memory, identity, observability and tool access. The update shows production AI agents shifting toward governed knowledge and execution infrastructure.
What does it mean for everyday AI users?
ENHE users should use this as an AI agent platform checklist. Cloud, local and workflow automation tools should be evaluated by source traceability, knowledge connectors, tool permissions, account security, observability, cost controls and failure recovery.
Where can readers continue learning on ENHE AI?
Readers can continue with ENHE AI software apps, AI skill tutorials, and AI account service guidance to turn the news signal into practical action.



