Amazon Bedrock AgentCore Identity now permits agents to authenticate against internal identity providers using private certificate authorities (CAs). This update removes the need for public endpoints when your organization self-hosts services like Keycloak or PingFederate within a VPC.
Amazon Bedrock AgentCore has upgraded its underlying harness to the Strands framework. This update introduces built-in capabilities like web retrieval, task planning, and automatic context management, alongside new lifecycle hooks for deterministic control over agent execution.
Amazon has published a reference architecture for connecting Bedrock AgentCore to private REST APIs and MCP servers in restricted network environments. By utilizing a VPC Lattice resource gateway placed in a dedicated network-account VPC, traffic between agents and internal tools is forced through a central inspection firewall.
Amazon Bedrock has launched a new memory-aware capability for AgenticRetrieveStream. This feature automates the storage, extraction, and retrieval of user-specific facts and conversation histories, allowing agents to provide context-aware responses while maintaining strict document-level access control.
Amazon has released a next-generation runtime for Bedrock AgentCore designed to handle complex, long-running AI agent workloads. The update brings hardware-isolated environments with faster startup times, increased compute capacity, and improved cost efficiency through usage-based billing.
Amazon introduced a pattern for securing multi-tenant AI agents by ensuring that RAG search queries are scoped to specific users. The solution uses ACL-aware knowledge bases combined with a request interceptor in the AgentCore Gateway to deterministically inject verified user identities into tool calls, preventing LLMs or prompt injections from accessing unauthorized data.
Taxbit has deployed a secure, role-aware AI assistant using Amazon Bedrock AgentCore to automate product documentation support. The agent uses RAG to ground answers in verified content while strictly enforcing PII masking, regional data residency, and user-role permissions.
Amazon introduced Web Answer on Bedrock AgentCore, a managed tool that simplifies agent-based web research. It automates the entire pipeline from searching and verifying facts to synthesizing cited answers, delivering results via MCP.
Amazon Bedrock AgentCore now supports Session endpoints, allowing developers to view and interact with web applications live as an AI coding agent builds them. By routing traffic through an authenticated, isolated microVM session, changes appear in the browser instantly without requiring separate deployments.
Eon, a data protection ISV running on AWS, replaced per-tool credentials and local MCP servers with a single Amazon Bedrock AgentCore MCP Gateway. The gateway uses Cedar-based policies to enforce least-privilege access for both human engineers and an autonomous SRE agent running Claude on Amazon Bedrock, routing calls to MCP servers hosted on AgentCore Runtimes across multiple AWS accounts. Developer onboarding time dropped from about two days to about two minutes after rolling the system out to 100+ developers and roughly 10,000 sessions.
AWS published a governance framework called Trust in Depth, designed to let AI agents operate with more autonomy while staying within enforceable limits. It combines scoping agent permissions before deployment, giving each agent a verifiable identity, enforcing boundaries at runtime via policy gateways, and observing agent behavior afterward. The framework leans on automated reasoning (mathematical proof) for rules that can be precisely defined, and human judgment for ambiguous cases, using AWS tools like Bedrock AgentCore, Guardrails, Kiro, Strands, Agent Registry and CloudWatch Omni.