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.
Amazon has released the Universal Agent Evaluation Framework (UAEF), an open-source tool designed to standardize the evaluation of AI agents. It uses adapters to normalize execution traces from various frameworks like LangChain and LangGraph into a single format, enabling consistent measurement across 36 metrics and 7 quality dimensions.
Amazon Bedrock AgentCore now includes a comprehensive catalog of built-in, third-party, and custom evaluators to monitor agent behavior in production. The platform allows you to run metrics from DeepEval and AutoEval in a managed environment, supporting on-demand, online, and batch evaluation workflows.
Amazon introduced a seven-layer reference architecture to move AI agent applications from initial prototypes to production-ready systems. The framework emphasizes a modular, pluggable design using stable contracts between layers such as data, inference, orchestration, and security.
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.
Greenlight Financial has successfully automated over 90% of its security and risk case resolution—totaling 4,000 cases monthly—by deploying a tiered multi-agent architecture on Amazon Bedrock AgentCore. The system uses a Tier 1 supervisor for high-volume triage and a Tier 2 supervisor for deep-dive investigation, significantly reducing human analyst workload.
This update introduces a gateway-based architecture to manage AI agent access at scale. By using Amazon Bedrock AgentCore Gateway and Cedar policies, you can move authorization logic away from individual tools to a central policy engine, streamlining security across hundreds of agents.
Amazon introduced a serverless Model Context Protocol (MCP) gateway built on Amazon ECS Fargate that allows AI agents to query enterprise data lakes using a metadata-driven approach. Instead of writing custom integration code for every new dataset, you define table schemas and business logic in JSON, which the system automatically registers and indexes.
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 Quick has launched Smart Approvals to automate routine agent tasks while maintaining human oversight for critical decisions. The system uses a classifier to evaluate requested actions against conversation context and user policy, preventing unnecessary interruptions without bypassing established security controls.
This update outlines a method for building a semantic knowledge base directly within PostgreSQL using the AIDB extension. By indexing schema metadata and utilizing the Model Context Protocol (MCP), you can expose database tools to agents in Amazon Bedrock AgentCore while enforcing existing row-level security.
Amazon has updated the AgentCore Gateway to support automated token exchange between Microsoft Entra ID and protected REST APIs. By leveraging this flow, AI agents can now perform actions in platforms like ServiceNow using the identity and permissions of the end-user rather than acting as a generic service account.
Amazon introduced a multi-agent system built on Bedrock AgentCore that automates engineering document evaluation and substitution. The architecture combines multimodal retrieval, deterministic Python-based tolerance checking, and hierarchical LLM orchestration.
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.
Amazon has enabled intent-driven UI automation by pairing Nova Act with the Bedrock AgentCore Browser Tool. This setup allows engineering teams to define test workflows through natural language instructions instead of maintaining rigid, selector-heavy codebases.
MoEngage successfully integrated over 400 internal REST APIs as agent tools using Amazon Bedrock AgentCore Gateway. This approach eliminated the need for manual MCP server maintenance, complex networking, and security risks associated with public internet exposure.
Amazon Bedrock AgentCore is a new service designed to streamline the deployment and management of multi-agent architectures. It handles agent hosting, secure tool access via MCP, and session isolation, enabling teams to focus on agent behavior rather than operational overhead.
AWS announced general availability of training sessions within Amazon SageMaker AI serverless model customization. Teams can write their own post-training loops — including custom loss functions and reward signals for reinforcement learning — while SageMaker AI handles GPU allocation, distributed execution, fault recovery, and checkpoint storage. Supported techniques include SFT, DPO, RLVR, RLAIF, and multi-turn RL, and users can choose LoRA or full fine-tuning. The feature supports models including gpt-oss-20b, gemma-4-31B-it, Qwen3.6-27B, and Qwen3.8-27B, and billing is based on tokens processed, pausing while a user's reward function scores responses.
AWS published a walkthrough for the Adaptive Agentic Intelligence Framework (AAIF), built on Strands Agents, which routes simple requests to small local models (via Ollama) and only sends complex requests to cloud models through Amazon Bedrock. A lightweight 1B-parameter model (llama3.2:1b) acts as an orchestrator deciding where each request should go, with an example IoT monitoring agent that uses local telemetry retrieval, local vision analysis, and cloud-based expert insights. AWS states that in the hybrid setup, roughly 80 percent of traffic can be handled locally without hitting a paid API, and the architecture can run fully on edge hardware (e.g. Raspberry Pi with 8GB memory), fully in the cloud, or in a hybrid mode.
AWS introduced Agent Registry, a managed catalog service for Model Context Protocol (MCP) servers, agents, and agent skills. Instead of hardcoding every tool into an orchestrator, agents can now search an approved, versioned catalog at runtime and build a client from the returned descriptor. A reference sample demonstrates a Discover → Instantiate → Execute loop using Amazon Bedrock AgentCore Gateway and AgentCore runtime, with Anthropic Claude Sonnet as the foundation model.
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 and Keyfactor published a reference design that fixes a known weak point in Model Context Protocol (MCP) deployments: MCP has no built-in way to authenticate which agent is actually making a request. The architecture adds three trust layers — user-to-system, agent-to-agent, and agent-to-tool-server — built on signed request envelopes, delegation assertions signed by the user, RFC 8693 audience-restricted tokens, and live OCSP revocation checks. A working example runs on Amazon Bedrock and the AWS Strands Agents SDK with Keyfactor EJBCA issuing and validating the X.509 certificates, and the full code is on GitHub.
AWS has rolled out structured outputs across every Anthropic Claude model hosted on Amazon Bedrock, reaching both the standard runtime endpoint and the newer Mantle endpoint built for agentic workloads. Instead of hoping the model returns valid JSON, developers can now lock responses to an exact schema through constrained decoding, which blocks the model from generating tokens that would break the format. A companion feature, strict tool use, applies the same guarantee to function-calling arguments so agent workflows don't fail on malformed inputs.