Official Amazon announcements — model releases, product launches and research, each one summarized with every source covering it, by AIBriefs. RSS
Launch·Developers·1 source
AWS now manages NVIDIA Dynamo on SageMaker HyperPod, splitting prompt processing and token generation across GPUs. AWS cites GLM-5.3's FP8 weights exceeding the 640 GB of GPU memory on a single ml.p5.48xlarge instance before KV cache and runtime.
How-To·Developers·1 source
AWS's post targets agents with dozens of tools and large structured inputs, where token consumption and latency are the main blockers to production UX. It notes each extra tool invocation re-injects the full JSON payload into the LLM context.
How-To·Developers·1 source
AWS argues the biggest cost lever is whether to call a model at all, since teams route input validation, formatting, and routing through an LLM. Each call is cheap alone but compounds at production scale.
Launch·Developers·1 source
The new routing strategy reads cache state reported by the model container and sends each request to an instance holding a long cached prompt match that isn't too busy. It targets real-time endpoints on Amazon SageMaker AI.
How-To·Developers·1 source
AWS published a technical how-to for extending enterprise authentication and authorization controls into the agentic layer when an AI agent on Amazon Bedrock AgentCore calls Snowflake Cortex AI. It targets the common workaround of broad service-account permissions or custom-built auth integrations that add operational overhead.
Launch·Developers·1 source
AWS announced AI data preparation capabilities in Amazon SageMaker for building training and evaluation datasets. AWS says fine-tuning open-weight models, running reinforcement learning, and building evaluation suites all depend on high-quality data.
Launch·Business·1 source
AWS Forward Deployed Engineering is now available in 15 countries, including the U.S., Mexico, Brazil, Canada, Australia, Singapore, India, South Korea, Japan, the UK, Germany, the Netherlands, France, Sweden and Saudi Arabia. It serves both commercial and public sector customers.
How-To·Developers·1 source
AWS published a technical walkthrough for building WhatsApp AI agents on Amazon Bedrock AgentCore, aimed at developers in Latin America, India, and Southeast Asia where WhatsApp is a dominant business channel. AWS calls WhatsApp a genuinely difficult surface to build on.
How-To·Developers·1 source
AWS published a technical walkthrough for running OpenTSLM, a model for reasoning over time-series data, via SageMaker JumpStart. The post frames it around industrial use cases like preventing production stoppages and diagnosing vehicle faults.
How-To·AI Agents·1 source
AWS customer story details how LoanPro used Amazon Bedrock AgentCore to build an agentic assistant that pulls borrower account data for loan servicing calls. Co-written by AWS's Mariah Miller and LoanPro's Colin Terry.
How-To·Policy·1 source
AWS's post targets platform and application teams building agentic AI platforms that govern the applications, tools, skills, models, and storage agents use. It argues generative AI's nondeterministic nature adds complexity prior software practices didn't anticipate.
How-To·Health·1 source
ArisGlobal's NavaX automates adverse-event case processing for pharmacovigilance, regulatory, medical affairs, clinical and quality workflows. The life-sciences vendor chose Amazon Bedrock to scale generative AI inference.
Launch·AI Agents·1 source
AWS's Managed Knowledge Base gains Agentic Retrieve, letting knowledge-grounded agents carry context across turns so follow-up questions about policies or procedures reflect what users previously told the app.
How-To·AI Agents·1 source
AWS argues multi-agent failures are rarely the model's fault — coordination is a distributed systems problem, and many teams lack distributed systems instincts. The post catalogs design patterns, anti-patterns, and lessons drawn from manufacturing.
How-To·Developers·1 source
AWS walks through converting legacy mainframe Assembler batch jobs to Java using Amazon Bedrock and AWS Transform, aimed at banking, insurance, and airline customers whose critical programs depend on retiring specialists.
How-To·Developers·1 source
Novo Nordisk, maker of diabetes and obesity medicines, uses Amazon Bedrock AgentCore to modernize manufacturing process documents across a global production network bound by strict quality rules. AWS published the case study as a customer solution.
Launch·Developers·1 source
Tabular search answers questions from CSV, XLSX, and XLS files via agentic retrieval, looking up values and running calculations across every relevant row in one or more tables or sheets.
How-To·Policy·1 source
Denied Topics blocks a content category by plain-language description applied semantically rather than by keyword, but the same mechanism can match more than intended — a topic named Finance, for example, can over-block.
How-To·Developers·1 source
Retrieval instructions in Amazon Bedrock Managed Knowledge Base let teams set voice and answer behavior per tenant, so shared product and policy documents return different answers to different audiences.
How-To·Developers·1 source
AWS published a technical how-to on reusing cached context — system prompts, reference documents, tool definitions, or prior conversation — across requests for open-weight models on Amazon Bedrock.
How-To·Developers·1 source
The South Korean energy and chemical company splits model development and operations between process engineers and dedicated ops staff, connecting engineer-built models to production workflows via SageMaker Pipelines.
How-To·Developers·1 source
AWS post walks through using NVIDIA NeMo Switchyard on Amazon Bedrock to send each coding-agent request to the right model, noting a single task can take a few model calls or dozens. It frames cost around the task rather than one call.
How-To·Developers·1 source
AWS blog post covers architecture patterns for cutting cold-start latency in Amazon Bedrock AgentCore runtime, where each agent session runs in its own isolated serverless environment. Aimed at agents behind interactive experiences where a person waits for the first response.
Launch·Science·1 source
OpenFold3-preview, an open-source biomolecular structure prediction model from the OpenFold Consortium and Columbia's AlQuraishi Lab, can now be deployed from Amazon SageMaker JumpStart with a few lines of code into a customer's own AWS environment.
How-To·Developers·1 source
AWS post details how AssemblyAI runs GPU-heavy speech-to-text pipelines — acoustic models, language models, post-processing — on Amazon EC2 Spot instances to cut inference costs at scale.
How-To·Developers·1 source
Bedrock traces every inference call back to the IAM principal that made it, with identity and organizational tags flowing into AWS Cost and Usage Reports (CUR 2.0) and Cost Explorer. Data stays inside the AWS environment.
How-To·Developers·1 source
AWS's technical walkthrough covers capturing production inference data on SageMaker HyperPod to detect drift, surface failure patterns, and feed real inputs back into retraining. It targets gaps no pre-curated dataset covers, such as domain jargon, unexpected formats, and shifting user behavior.
Launch·Developers·2 sources
SGLang-Neuron is publicly available via an AWS Deep Learning Container, released by RadixArk with Annapurna Labs, for serving models and generating RL rollouts on Trainium. SGLang already supports NVIDIA, AMD, Intel and Google chips, so teams can switch hardware without changing software.
How-To·AI Agents·1 source
Natera's lab engineering team, led by Ariel Jirau, built SWARM (Systematic Workflow Analytics and Resolutions Manager) with AWS to keep cell-free DNA testing instruments running, since equipment downtime disrupts sample processing.
How-To·Developers·1 source
Cache duration, service tier, reasoning effort, and maxTokens can change how many tokens Bedrock processes and the rate applied to them, per AWS's guide. The post argues bills keep climbing even after prompt and application-logic tuning.
How-To·Developers·1 source
Part 2 of an AWS series on controlling Amazon Bedrock spend, following part 1's model of IAM principal-tag attribution, Cost and Usage Report 2.0, model invocation logging, and three-tier enforcement.
How-To·Developers·1 source
AWS's technical how-to pairs Amazon Bedrock foundation models with LiteLLM so developers get quick access to models while platform teams keep visibility and usage control. The setup targets latency and error monitoring plus cost oversight for internal AI coding assistants.
Launch·AI Agents·1 source
AWS says 40% of large enterprises are now scaling AI agents, up from 27% a year ago. The post cites METR data showing the task length frontier agents can complete autonomously doubles roughly every four months.
How-To·Developers·1 source
The Agent Toolkit for AWS now includes a migration guide moving customer-managed Bedrock knowledge bases to the fully managed version, which removes per-data-source vector store provisioning, embedding model tuning, and capacity planning.
How-To·AI Agents·1 source
AWS's technical how-to covers using the A2A protocol so agents built and run by different organizations can discover each other, communicate, and exchange tasks without exposing internals.
How-To·Developers·1 source
AWS published a technical how-to on scoping agent access to Bedrock Managed Knowledge Base tools, aimed at orgs running hundreds of agents across many data sources and tools. It uses Amazon Bedrock AgentCore and Knowledge Bases.
How-To·AI Agents·1 source
AWS's Agent DLC post covers moving LLM agents that call tools, orchestrate APIs, and answer questions over internal knowledge from demo to release, with pre-release engineering steps. It references Amazon Bedrock AgentCore.
How-To·AI Agents·1 source
AWS tutorial targets Java teams moving agents from prototype to production, pairing Amazon Bedrock with Spring AI on existing JVM tooling and CI/CD pipelines. It argues agent frameworks alone don't cover scalability, governance, security, or operational concerns.
How-To·Developers·1 source
AWS published a technical how-to on running OpenAI Codex through Amazon Bedrock so platform teams avoid standing up a second model-access, identity, and operations stack. The post covers using Codex to explore unfamiliar code, make changes, and handle repetitive engineering work.
How-To·Developers·1 source
Silent data corruption returns a wrong but plausible number from hardware like a GPU without raising an error, letting bad values flow into gradients and weights of every replica. Loss can look normal for hours before teams notice.
Launch·AI Agents·3 sources
The new API gives agents access to information newer than their model's training data, covering recent events, product releases, prices, and regulations. It replaces the previous route of delivering web search to agents through AgentCore Gateway.
How-To·Developers·1 source
AWS's monthly roundup covers October 2026 additions across Amazon Bedrock and Bedrock AgentCore, framed around model choice, production trust for agents, and cost visibility. The post is a recap of already-shipped features rather than a new launch.
How-To·Developers·1 source
AWS published a how-to for automating AWS Agent Registry record updates whenever a published MCP server adds a tool or changes its schema, avoiding stale metadata for consumers. The registry is a capability of Amazon Bedrock AgentCore.
How-To·AI Agents·1 source
AWS customer post co-written with DXC's Nick Tamburro describes a multi-model substrate on Bedrock for agents acting on production servers at banks and hospitals. It cites recent public incidents where autonomous agents took destructive actions their operators never intended.
How-To·Developers·1 source
AWS's post argues teams waste time rebuilding RAG pipelines, document processors, and agent scaffolding instead of reusing existing components. It is tagged Intermediate (200) and Technical How-to, aimed at Amazon Bedrock builders.
How-To·Developers·1 source
AWS blog post describes agents built on AWS Quick that speed up the product development lifecycle, with human approval steps baked into the workflow. The post argues AI-driven software delivery is outpacing upstream product processes.
How-To·AI Agents·1 source
UAEF targets teams running agents across LangGraph, LangChain, Strands Agents, and Amazon Bedrock AgentCore, whose differing execution records make cross-framework evaluation hard. It provides closed-loop evaluation that normalizes message, tool-call, and handoff structures across frameworks.
Launch·Developers·1 source
Usage-based metering targets real-time speech AI billing: customers pay for the endpoint infrastructure hosting the model, while model providers listing on AWS are billed separately.
Launch·Developers·1 source
Kimi K3.1 Pro Highspeed is a post-trained version of Kimi K3 with the same 3T-class open-weight architecture and a 1-million-token context window, trained with substantially more post-training compute.
How-To·AI Agents·1 source
AWS's guide covers three evaluation approaches on AgentCore Evaluations: built-in evaluators, DeepEval, and AutoEval. It targets teams that currently spot-check outputs and watch latency instead of measuring whether agents meet business needs at scale.
How-To·AI Agents·1 source
Trovata's AI-native treasury solution runs on Amazon Bedrock and AgentCore, targeting banking data fragmented across dozens of bank portals and manual reporting trapped in spreadsheets. Legacy Treasury Management Systems are cited as unable to scale for modern enterprise needs.
How-To·AI Agents·1 source
TCS uses Amazon Bedrock AgentCore to automate large-scale testing for banking, financial services, and insurance clients, where release delays stem from testing rather than application code. The post is co-written by TCS's Varun Valsan.
How-To·Developers·1 source
AWS's walkthrough targets teams running thousands of model invocations a day across multiple accounts, where the aggregate bill is visible but per-request detail is not. It builds an observability data lake for Amazon Bedrock workloads.
How-To·AI Agents·1 source
AWS blog post explains how AWS Quick lets users encode repeatable tasks — weekly status updates, release notes, project management, ticket creation — as agents and skills instead of re-explaining them each time.
How-To·Developers·1 source
AWS walks through single-shot versus agentic retrieval patterns on Amazon Bedrock Managed Knowledge Base, using a banking assistant that answers document-checklist questions and then compares requirements across sole proprietorships, LLCs, and partnerships.
Launch·AI Models·1 source
Super VL is the vision-language model in the Nemotron 3.5 family, a 120B-parameter mixture-of-experts that activates 12B parameters per token. It joins Nemotron 3 Nano, Nano Omni, Super, Ultra and Nemotron 3.5 Lightning on AWS, deployable via SageMaker Studio or the Python SDK.
How-To·AI Agents·1 source
AWS published a seven-layer composable reference architecture for running enterprise AI agents in production on Amazon Bedrock AgentCore, aimed at handling thousands of concurrent user requests securely. It targets reliability under real traffic rather than demo conditions.
How-To·AI Agents·1 source
AWS customer story details how CrossnoKaye grounds industrial AI agents using Amazon Bedrock AgentCore, addressing plant data and control logic split across PLCs and DCS from different vendors.
Analysis·AI Models·1 source
A Hugging Face blog post co-published with Amazon introduces higher-order pruning of experts (HOPE) for keeping partner experts together in mixture-of-experts models. The post is titled "Your Experts Have Partners. There's HOPE for Keeping Them Together."
Launch·Developers·1 source
AWS says SageMaker GPU endpoints previously required a whole accelerator per model, so an ml.p4d.24xlarge with eight A100s held only eight models. MIG support lets multiple models share a single GPU to raise utilization.