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 has published a workflow for using Sequence-Level Knowledge Distillation (SeqKD) to fine-tune smaller models on trajectories generated by frontier models. By using a 'teacher' model to generate successful tool-use trajectories and filtering them with a programmatic scorer, teams can train compact 'student' models that perform complex reasoning at a fraction of the cost.
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.
NVIDIA has introduced Nemotron 3.5 Super VL, a 120B-parameter multimodal model featuring a 1M token context window. The model utilizes a hybrid Mamba-2 and MoE architecture to balance reasoning capabilities with efficient inference, and is now available for deployment on Amazon EKS and SageMaker HyperPod.
AWS introduced pre-built Ray Train Deep Learning Containers (DLCs) that consolidate PyTorch, CUDA, NCCL, and EFA networking libraries into a single tested image. This approach allows your team to deploy distributed training clusters on Amazon EKS without maintaining custom build pipelines or resolving complex driver compatibility issues.
AWS has updated its QA Studio reference solution, adding native support for multi-team organizational structures. The new capabilities include application-level ownership, automated health scoring based on CloudWatch metrics, and granular role-based access control.
Amazon Bedrock now supports explicit and implicit prompt caching for OpenAI models, allowing you to store and reuse static prompt prefixes like tools, instructions, and conversation history. By avoiding the re-processing of identical tokens across turns, you can significantly lower input costs and improve responsiveness in complex agent workflows.
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.
Audible has developed a controllable text-to-speech pipeline that uses LLMs to profile characters and attribute dialogue with up to 97% accuracy. By providing 'stage directions' as natural-language captions, the system ensures distinct, consistent character voices over long-form content.
Amazon has released TorchNeuron, an open-source backend that lets existing PyTorch code run on AWS Trainium accelerators without major rewrites. The release introduces a new execution mode plus layered caching to reduce recompilation, and its reliability was validated through an AI-agent-driven testing pipeline that distilled hundreds of thousands of Hugging Face models down to a manageable benchmark set. Internal large-model tests reported roughly a 33% reduction in the delay before the first training step begins.
AWS has upgraded the Amazon Polly Generative engine with more natural, expressive speech and better accuracy for numbers, addresses and confirmation codes. The update adds 14 new voices across 9 locales, bringing the total to 57 generative voices in 11 languages and 25 locales, including first-time general availability for Hindi and Finnish. It is a drop-in upgrade: voice names, APIs and pricing stay the same, so existing applications work unchanged.
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.
Amazon's MadPot honeypot network recorded an exploitation attempt against what is now tracked as CVE-2026-109618 and CVE-2026-109619 — nicknamed PHP2Shell — on October 17, 2026, four days before the vendor publicly disclosed the flaw. The request came from a commercial anonymization network, suggesting a threat actor had working exploit code ahead of the official embargo lift. When the embargo ended on October 21 at 1400 UTC, AWS says proof-of-concept code and real attack traffic hit its sensors within hours, from several distinct sets of infrastructure. AWS argues this points to a structural shift: AI-assisted analysis is making it faster to turn a patch or advisory into a working exploit, shrinking the old assumption that most attacks follow a public PoC.
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.
Cohere launched Rerank 5, its newest enterprise reranking models, in Pro and Fast tiers. Rerank 5 Pro leads major public benchmarks including BRIGHT, ViDoRe V3, BEIR and nanoMTEB, while Rerank 5 Fast offers near-leading quality at lower cost and higher throughput. The release introduces Context Focus, which returns the most relevant text spans within documents rather than whole documents, and calibrated relevance scores that read as probabilities across models and domains.
Amazon partnered with the independent nonprofit AVERI to audit the quality of its own internal safety-evaluation datasets for its AI models, not just the models' outputs. AVERI reviewed a random, anonymized sample of safety-test prompts covering areas like harmful content, cybersecurity, privacy and copyright. The review confirmed strong topical coverage, diverse testing methods and low contamination risk, but flagged gaps in multilingual coverage and multistep adversarial testing. Amazon responded with four concrete changes to its evaluation process.
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.