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.
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.
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.
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.
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.
Tamnoon built Tami, an agentic orchestrator on Amazon Bedrock that investigates cloud security findings from CNAPPs and cloud providers, scores remediation safety, and generates fixes with guardrails. The company reports a greater than 90% reduction in critical cloud exposure within 90 days with zero production issues. The system uses four specialized agents (investigation, safety-scoring, remediation, code-generation) each calling different foundation models through Bedrock, with Bedrock Guardrails and Cross-Region inference providing safety and scale.
Orca Security built Discovery AI, an Amazon Bedrock-based agent that turns plain-English security questions into structured queries against its Sonar system, which tracks over 900 cloud resource types. Rather than relying on one large model with the full schema stuffed into every prompt, the production version splits the work across nine specialized stages and multiple foundation models. The result: dramatically lower cost, faster responses, and better accuracy on complex queries, now running live since March 2026.
Amazon Web Services researchers published a method called 'priming' that converts pretrained Transformer models into hybrid architectures mixing attention and state space model (SSM) layers, reusing existing weights instead of retraining from scratch. The approach cuts pretraining costs by over 99% and lets a 32-billion-parameter hybrid model match its source Transformer's quality while decoding up to twice as fast. Amazon tested three SSM types and released an open-source model zoo, training code, and serving tools under Apache 2.0.
AWS published a joint engineering write-up with Postman describing how Agent Mode, Postman's AI-native interface for API testing and documentation, was built to run in production at scale. Rather than model quality, the team found that tool sprawl and missing context were the biggest obstacles to reliable agent behavior. The post details architectural patterns including dynamic tool scoping, schema-based query access, dedicated context handlers, and how Amazon Bedrock provides model flexibility, cross-Region inference, data residency controls, and prompt caching.