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.
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.