llm-catalog-archive

Change

d7a7468

d7a74687f4690a01b9667d03ec9a16c37a0126e5 · commit on GitHub

aws-blog-feed: changed (687276 bytes, HTTP 200)

raw/aws-blog-feed/response.xml modified

Lines added
+4,159
Lines removed
-4,204
Stored bytes at this commit
687,276
Timestamp
observed
Raw artifact at this commit
raw/aws-blog-feed/response.xml
Recorded headers
observed_at2026-09-09T04:42:47.947Z
origin_datenull
status200
final URLhttps://aws.amazon.com/blogs/machine-learning/feed/
etagnull
last-modifiedWed, 09 Sep 2026 00:16:42 GMT
dateWed, 09 Sep 2026 04:42:47 GMT
agenull
cache-controlnull
cf-cache-statusnull
content-encodingnull
content-lengthnull
@@@ -5,7 +5,7 @@
<atom:link href="https://aws.amazon.com/blogs/machine-learning/feed/" rel="self" type="application/rss+xml"/>
<link>https://aws.amazon.com/blogs/machine-learning/</link>
<description>Official Machine Learning Blog of Amazon Web Services</description>
- <lastBuildDate>Fri, 04 Sep 2026 21:45:52 +0000</lastBuildDate>
+ <lastBuildDate>Tue, 08 Sep 2026 22:06:58 +0000</lastBuildDate>
<language>en-US</language>
<sy:updatePeriod>
hourly </sy:updatePeriod>
@@@ -13,203 +13,145 @@
1 </sy:updateFrequency>
<item>
- <title>Deploy a multimodal WhatsApp ordering assistant with Amazon Bedrock AgentCore</title>
- <link>https://aws.amazon.com/blogs/machine-learning/deploy-a-multimodal-whatsapp-ordering-assistant-with-amazon-bedrock-agentcore/</link>
+ <title>Take on your most ambitious work with GPT-6 Astra on Amazon Bedrock</title>
+ <link>https://aws.amazon.com/blogs/machine-learning/take-on-your-most-ambitious-work-with-gpt-6-astra-on-amazon-bedrock/</link>
- <dc:creator><![CDATA[Salman Ahmed]]></dc:creator>
- <pubDate>Fri, 04 Sep 2026 21:45:52 +0000</pubDate>
- <category><![CDATA[Amazon Bedrock AgentCore]]></category>
- <category><![CDATA[Expert (400)]]></category>
- <category><![CDATA[Technical How-to]]></category>
- <guid isPermaLink="false">1cc1445c2783ef202a00ff4aadacbc028620a9eb</guid>
-
- <description>Learn how to deploy a multimodal WhatsApp ordering assistant that takes customer orders through text, voice notes, and real-time voice calls on a single business number, built on Amazon Bedrock AgentCore with Amazon Nova 2. The channel and ordering layers stay separate, and one sha
- <content:encoded>&lt;p&gt;This post shows how to deploy a multimodal WhatsApp ordering assistant built with &lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-get-started-toolkit.html" target="_blank" rel="noopener"&gt;Amazon Bedrock AgentCore&lt;/a&gt; and
-&lt;p&gt;A single WhatsApp Business number hosts the assistant. A customer can text the restaurant, send a voice note, or place a voice call. An AI agent takes the order end to end, from greeting to confirmation. All three channels share one backend and one cross-channel memory. A customer who texts
-&lt;p&gt;The solution uses the &lt;a href="https://developers.facebook.com/docs/whatsapp/cloud-api/" target="_blank" rel="noopener"&gt;Meta WhatsApp Business Platform&lt;/a&gt; as the customer front door. Amazon Bedrock AgentCore hosts the agents. &lt;a href="https://aws.amazon.com/nova/models/" tar
-&lt;h2 id="solution-overview"&gt;Solution overview&lt;/h2&gt;
-&lt;p&gt;The design keeps three things apart: (1) the WhatsApp layer handles the conversation, (2) three agent runtimes run the conversations for their channels, and (3) the backend holds the menu, carts, orders, and locations. Inbound traffic arrives on a single HTTPS webhook, is acknowledged with
-&lt;p&gt;The customer front door is the &lt;a href="https://developers.facebook.com/docs/whatsapp/cloud-api/" target="_blank" rel="noopener"&gt;Meta WhatsApp Business Platform&lt;/a&gt;. It exposes the Cloud API webhook, Messages API, Media API, and Calling API. Meta manages this service. You set it
-&lt;p&gt;You use the AWS CDK to deploy the following AWS resources as a set of stacks in dependency order, grouped here by function.&lt;/p&gt;
-&lt;ul&gt;
- &lt;li&gt;&lt;a href="https://aws.amazon.com/api-gateway/" target="_blank" rel="noopener"&gt;Amazon API Gateway&lt;/a&gt; provides two REST APIs. The first is a regional HTTPS webhook on an AWS managed certificate. It’s the only public endpoint. The second is an AWS Identity and Access Management (
- &lt;li&gt;&lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener"&gt;AWS Lambda&lt;/a&gt; runs the webhook ingest, the webhook worker, the message sender, and the ordering business logic.&lt;/li&gt;
- &lt;li&gt;&lt;a href="https://aws.amazon.com/sqs/" target="_blank" rel="noopener"&gt;Amazon Simple Queue Service (Amazon SQS)&lt;/a&gt; provides the inbound queue, with a dead-letter queue, that decouples the quick acknowledgment from the rest of the processing.&lt;/li&gt;
- &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html" target="_blank" rel="noopener"&gt;AgentCore runtime&lt;/a&gt;, a capability of Amazon Bedrock AgentCore, hosts the three agents. Each conversation runs in its own microVM. Sessions stay is
- &lt;li&gt;Amazon Nova 2 Lite (text through the Converse API) and Amazon Nova 2 Sonic (speech-to-speech for voice) are invoked through &lt;a href="https://aws.amazon.com/bedrock/" target="_blank" rel="noopener"&gt;Amazon Bedrock&lt;/a&gt;.&lt;/li&gt;
- &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html" target="_blank" rel="noopener"&gt;AgentCore Gateway&lt;/a&gt;, a capability of Amazon Bedrock AgentCore, is a managed MCP server that exposes the backend REST API as MCP tools the agents call by name.&
- &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory.html" target="_blank" rel="noopener"&gt;AgentCore memory&lt;/a&gt;, a capability of Amazon Bedrock AgentCore, is one shared, cross-channel record keyed by a hashed customer ID.&lt;/li&gt;
- &lt;li&gt;&lt;a href="https://aws.amazon.com/dynamodb/" target="_blank" rel="noopener"&gt;Amazon DynamoDB&lt;/a&gt; stores customer profiles, orders, menu items, carts, and locations. It also holds a &lt;em&gt;last inbound&lt;/em&gt; window table for the WhatsApp layer.&lt;/li&gt;
- &lt;li&gt;&lt;a href="https://aws.amazon.com/location/" target="_blank" rel="noopener"&gt;Amazon Location Service&lt;/a&gt; handles geocoding and nearest-location lookups.&lt;/li&gt;
- &lt;li&gt;&lt;a href="https://aws.amazon.com/kinesis/video-streams/" target="_blank" rel="noopener"&gt;Amazon Kinesis Video Streams (Amazon KVS)&lt;/a&gt; provides a signaling channel that the voice-call runtime uses to mint credentials for the managed Traversal Using Relays around NAT (TURN) relay
- &lt;li&gt;&lt;a href="https://aws.amazon.com/vpc/" target="_blank" rel="noopener"&gt;Amazon Virtual Private Cloud (Amazon VPC)&lt;/a&gt; with a single network address translation (NAT) gateway is the outbound path for the voice-call runtime. This is the only runtime that requires a VPC.&lt;/li&gt;
- &lt;li&gt;&lt;a href="https://aws.amazon.com/secrets-manager/" target="_blank" rel="noopener"&gt;AWS Secrets Manager&lt;/a&gt; holds the Meta Access Token, App Secret, and Verify Token, created as empty containers you populate out-of-band. &lt;a href="https://aws.amazon.com/systems-manager/" target
- &lt;li&gt;&lt;a href="https://aws.amazon.com/ecr/" target="_blank" rel="noopener"&gt;Amazon Elastic Container Registry (Amazon ECR)&lt;/a&gt;, &lt;a href="https://aws.amazon.com/codebuild/" target="_blank" rel="noopener"&gt;AWS CodeBuild&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/s3/" target
- &lt;li&gt;&lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt; captures logs and metrics, and &lt;a href="https://aws.amazon.com/kms/" target="_blank" rel="noopener"&gt;AWS Key Management Service (AWS KMS)&lt;/a&gt; encrypts data at rest.&lt;
-&lt;/ul&gt;
-&lt;h2 id="architecture-diagram"&gt;Architecture diagram&lt;/h2&gt;
-&lt;p&gt;Figure 1 shows the full architecture. The diagram organizes the solution into labeled groups A through G that carry the request path. Two supporting groups sit outside that path, handling a build pipeline that runs once at deploy time to build the agent images and security and monitoring se
-&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
- &lt;a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-1.png" alt="Architecture diagram of
- &lt;p class="wp-caption-text"&gt;Figure 1: Multimodal WhatsApp ordering architecture on AWS&lt;/p&gt;
-&lt;/div&gt;
-&lt;ul&gt;
- &lt;li&gt;A. WhatsApp ingress and delivery: The webhook API Gateway, the ingest, worker, and sender Lambdas, and the Amazon SQS queue. The ingest verifies the Meta signature and enqueues the message. The worker handles the remaining processing. The Sender Lambda delivers replies.&lt;/li&gt;
- &lt;li&gt;B. Agent runtimes: Three agents on AgentCore runtime, each an ARM64 container, one per channel: chat (Amazon Nova 2 Lite), voice note (Amazon Nova 2 Sonic), and voice call (Amazon Nova 2 Sonic over Web Real-Time Communication, or WebRTC). Only the voice-call runtime runs in a VPC.&lt;/li&
- &lt;li&gt;C. Artificial intelligence and machine learning (AI/ML): Amazon Nova 2 Lite and Amazon Nova 2 Sonic invoked through Amazon Bedrock, plus the shared AgentCore memory keyed by a hashed &lt;code&gt;customer_id&lt;/code&gt; for cross-channel continuity.&lt;/li&gt;
- &lt;li&gt;D. MCP server (managed): AgentCore Gateway exposes the backend REST API as discoverable MCP tools (&lt;code&gt;GetMenu&lt;/code&gt;, &lt;code&gt;AddToCart&lt;/code&gt;, &lt;code&gt;PlaceOrder&lt;/code&gt;, and more) that every runtime calls by name.&lt;/li&gt;
- &lt;li&gt;E. API and compute: The IAM-authorized backend API Gateway and the ordering Lambdas that hold the business logic.&lt;/li&gt;
- &lt;li&gt;F. Data storage: Amazon DynamoDB stores customer profiles, orders, menu items, carts, and locations.&lt;/li&gt;
- &lt;li&gt;G. Networking and location: Amazon Location Service for geocoding and nearest-location lookups, the Amazon KVS managed TURN relay for voice-call media, and the VPC with a NAT gateway as the outbound path for the voice-call runtime.&lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;Two supporting groups sit outside the request path. The build pipeline (AWS CDK, AWS CodeBuild, Amazon ECR, and Amazon S3) runs once at deploy time to build and store the ARM64 agent images. It is not in the path of any request. Security and monitoring (AWS Secrets Manager, AWS Systems Mana
-&lt;p&gt;The following steps trace a single request end to end through the architecture:&lt;/p&gt;
-&lt;ol type="1"&gt;
- &lt;li&gt;Meta delivers an inbound webhook (text, voice note, or call event) to the Webhook API Gateway and the Webhook Ingest Lambda.&lt;/li&gt;
- &lt;li&gt;The ingest verifies the Meta signature, enqueues to Amazon SQS, and returns &lt;code&gt;200&lt;/code&gt; within Meta’s window.&lt;/li&gt;
- &lt;li&gt;The Webhook Worker derives a pseudonymous &lt;code&gt;customer_id&lt;/code&gt; using the pepper in AWS Systems Manager Parameter Store.&lt;/li&gt;
- &lt;li&gt;The worker fetches media from the Meta Media API and invokes the matching agent on Amazon Bedrock AgentCore runtime (chat, voice note, or voice call) with &lt;code&gt;session_id = customer_id&lt;/code&gt;.&lt;/li&gt;
- &lt;li&gt;The runtime reads the customer’s long-term insights from AgentCore memory at session start.&lt;/li&gt;
- &lt;li&gt;It runs the conversation with Amazon Nova 2 Lite (text) or Amazon Nova 2 Sonic (voice) through Amazon Bedrock.&lt;/li&gt;
- &lt;li&gt;AgentCore Gateway is the managed MCP server. It exposes the backend REST API as MCP tools the agent calls by name.&lt;/li&gt;
- &lt;li&gt;Tools route through the backend API Gateway to AWS Lambda, Amazon DynamoDB, and Amazon Location Service. Voice-call media uses the Amazon KVS TURN relay (runtime in a VPC).&lt;/li&gt;
- &lt;li&gt;Replies go out through the Sender Lambda (text) or the worker (voice). Events are written back to memory at session end.&lt;/li&gt;
- &lt;li&gt;AWS CDK builds ARM64 images through AWS CodeBuild into Amazon ECR. Amazon CloudWatch logs components and AWS KMS encrypts data at rest.&lt;/li&gt;
-&lt;/ol&gt;
-&lt;p&gt;In short, every request flows from Meta’s webhook through the ingest, queue, worker, and agent runtime to the backend tools, then back to the customer on WhatsApp.&lt;/p&gt;
-&lt;h2 id="channel-flows"&gt;Channel flows&lt;/h2&gt;
-&lt;p&gt;All three channels share the same front door, backend tools, and memory. What differs is the media on the wire and the runtime that handles it.&lt;/p&gt;
-&lt;p&gt;Text message: A text message arrives on the webhook. The worker derives &lt;code&gt;customer_id&lt;/code&gt; and invokes the chat runtime, which reads memory, streams Amazon Nova 2 Lite through the Converse API, and calls backend tools through the MCP gateway as needed. Replies go through t
-&lt;p&gt;Figure 2 shows the text flow, from the inbound webhook through Amazon Nova 2 Lite on the Converse API to the reply delivered by the Sender Lambda.&lt;/p&gt;
-&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
- &lt;a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-2.gif" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-2.gif" alt="Text-message flow from
- &lt;p class="wp-caption-text"&gt;Figure 2: Text flow with Amazon Nova 2 Lite&lt;/p&gt;
-&lt;/div&gt;
-&lt;p&gt;Voice note (speech-to-speech): A voice note arrives as an audio message. The worker downloads the OGG Opus bytes and invokes the voice-note runtime. After reading memory, the audio is decoded to 16 kHz pulse-code modulation (PCM) and fed into a bounded Amazon Nova 2 Sonic speech-to-speech s
-&lt;p&gt;Figure 3 shows the voice-note flow, a bounded Amazon Nova 2 Sonic speech-to-speech session that returns a spoken reply with no transcription in the path.&lt;/p&gt;
-&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
- &lt;a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-3.gif" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-3.gif" alt="Voice-note flow with a
- &lt;p class="wp-caption-text"&gt;Figure 3: Voice note flow with Amazon Nova 2 Sonic&lt;/p&gt;
-&lt;/div&gt;
-&lt;p&gt;Voice call (WebRTC): The customer selects Call, and Meta’s Calling API delivers a connect webhook with the WebRTC Session Description Protocol (SDP) offer. The worker relays it to the voice-call runtime in &lt;code&gt;turnOnly&lt;/code&gt; mode, because it has no public IP. TURN credentials
-&lt;p&gt;Figure 4 shows the voice-call flow, where WebRTC media is relayed through the Amazon KVS managed TURN relay and Amazon Nova 2 Sonic drives the conversation.&lt;/p&gt;
-&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
- &lt;a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-4.gif" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-4.gif" alt="Voice-call flow with We
- &lt;p class="wp-caption-text"&gt;Figure 4: Voice call flow with Amazon Nova 2 Sonic&lt;/p&gt;
-&lt;/div&gt;
-&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt;
-&lt;p&gt;This solution has prerequisites in two areas: your AWS account and your Meta WhatsApp setup. Complete both prior to running the deployment, because it asks you for specific WhatsApp values and the agent cannot reply until they are in place.&lt;/p&gt;
-&lt;h3 id="aws-prerequisites"&gt;AWS prerequisites&lt;/h3&gt;
-&lt;ul&gt;
- &lt;li&gt;You need an active AWS account with Amazon Bedrock model access enabled for Amazon Nova 2 Lite (&lt;code&gt;amazon.nova-2-lite-v1:0&lt;/code&gt;) and Amazon Nova 2 Sonic (&lt;code&gt;amazon.nova-2-sonic-v1:0&lt;/code&gt;) in your deployment Region. Your IAM user or role must have permissi
-&lt;/ul&gt;
-&lt;p&gt;The agent containers build inside AWS CodeBuild on ARM64, so you do not need Python, Docker, or audio toolchains locally. Deploy in an AWS Region where Amazon Nova 2 Lite, Amazon Nova 2 Sonic, and AgentCore runtime, Gateway, and memory are all available. The US East (N. Virginia) Region (us
-&lt;p&gt;For model availability by Region, refer to &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html" target="_blank" rel="noopener"&gt;Supported models by AWS Region in Amazon Bedrock&lt;/a&gt;.&lt;/p&gt;
-&lt;h3 id="whatsapp-business-platform-meta-prerequisites"&gt;WhatsApp Business Platform (Meta) prerequisites&lt;/h3&gt;
-&lt;p&gt;The WhatsApp side is set up once in the Meta consoles, as a prerequisite rather than a step in this walkthrough. No AWS API can create a Meta app for you, so complete it first and have the values on hand before you deploy. For a demo, the Meta sandbox test number, which is available at no a
-&lt;p&gt;Have these items ready before you deploy.&lt;/p&gt;
-&lt;ul&gt;
- &lt;li&gt;A Meta Developer App with the WhatsApp product added, linked to a Business portfolio. Adding the product provisions a WhatsApp Business Account (WABA) and a sandbox test number at no additional cost. Refer to &lt;a href="https://developers.facebook.com/docs/whatsapp/cloud-api/get-started"
- &lt;li&gt;The App ID and App Secret. The App Secret is the key Meta uses to sign each webhook, and the webhook Lambda recomputes that signature.&lt;/li&gt;
- &lt;li&gt;An Access Token. The temporary token works for a quick test and expires in about 24 hours. For something longer-lived, create a &lt;a href="https://developers.facebook.com/documentation/business-messaging/whatsapp/access-tokens" target="_blank" rel="noopener"&gt;System User token&lt;/a&gt
- &lt;li&gt;The Business portfolio ID (the setup CLI can auto-discover the Phone Number ID and WABA ID).&lt;/li&gt;
- &lt;li&gt;A Verify Token that you invent. It is a hard-to-guess string Meta echoes back during the one-time &lt;a href="https://developers.facebook.com/docs/graph-api/webhooks/getting-started" target="_blank" rel="noopener"&gt;webhook verification handshake&lt;/a&gt;.&lt;/li&gt;
- &lt;li&gt;For voice calls, the &lt;a href="https://developers.facebook.com/docs/whatsapp/cloud-api/calling" target="_blank" rel="noopener"&gt;WhatsApp Calling API&lt;/a&gt; enabled on the number.&lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;Store none of these in source control. The Access Token, App Secret, and Verify Token are secrets and go into AWS Secrets Manager during deployment, not into the CDK templates.&lt;/p&gt;
-&lt;h2 id="deploy-the-solution-with-aws-cdk"&gt;Deploy the solution with AWS CDK&lt;/h2&gt;
-&lt;p&gt;The full solution is in the &lt;a href="https://github.com/aws-samples/sample-multimodal-whatsapp-restaurant-agent" target="_blank" rel="noopener"&gt;sample repository on GitHub&lt;/a&gt;. The repository contains three agent containers, the AWS CDK infrastructure code, and setup scripts tha
-&lt;div class="hide-language"&gt;
- &lt;pre&gt;&lt;code class="language-bash"&gt;git clone https://github.com/aws-samples/sample-multimodal-whatsapp-restaurant-agent.git
-cd sample-multimodal-whatsapp-restaurant-agent
-./scripts/preflight-check.sh
-./scripts/deploy-all.sh --deploymentPrefix qsr-wa&lt;/code&gt;&lt;/pre&gt;
-&lt;/div&gt;
-&lt;p&gt;The script provisions every stack in dependency order. It passes each stack’s outputs to the next. First it deploys the shared VPC. Then it deploys the backend: Amazon DynamoDB, Amazon Location Service, the ordering Lambdas, and the backend REST API. Next it deploys AgentCore Gateway and th
-&lt;p&gt;How the WhatsApp values reach the deployment matters for security. The CDK creates empty Secrets Manager containers for the three secrets. It does not take a secret as a CDK parameter, which would bake it into the synthesized template. You populate the secret values out-of-band, while the n
-&lt;div class="hide-language"&gt;
- &lt;pre&gt;&lt;code class="language-bash"&gt;cd scripts/whatsapp-setup
-npm start # choose "Pre-deploy", then "Post-deploy" after deploy
-node whatsapp-setup.mjs --doctor # read-only end-to-end check&lt;/code&gt;&lt;/pre&gt;
-&lt;/div&gt;
-&lt;p&gt;Once the webhook is subscribed and the secrets are populated, the number is live and the agent replies across all three channels.&lt;/p&gt;
-&lt;h2 id="acknowledging-fast-and-processing-asynchronously"&gt;Acknowledging fast and processing asynchronously&lt;/h2&gt;
-&lt;p&gt;Meta expects a prompt HTTP response with a &lt;code&gt;200 OK&lt;/code&gt; status code. Taking an order, fetching media, invoking an agent, and relaying call signaling needs a little more than that brief acknowledgment window allows. So the work splits in two. The Webhook Ingest Lambda does
-&lt;h2 id="one-memory-across-three-channels"&gt;One memory across three channels&lt;/h2&gt;
-&lt;p&gt;What makes this feel like one assistant is shared memory. A single AgentCore memory resource is keyed by a hashed &lt;code&gt;customer_id&lt;/code&gt;, and all three runtimes use the same key. Each runtime reads the customer’s long-term insights at session start and writes events back at th
-&lt;h2 id="connecting-the-agents-to-backend-tools-with-mcp"&gt;Connecting the agents to backend tools with MCP&lt;/h2&gt;
-&lt;p&gt;No AgentCore runtime calls the backend Lambda functions directly. AgentCore Gateway is a managed MCP server. Each AgentCore runtime connects to it as an MCP client over HTTPS, authenticated with the runtime’s IAM role, and discovers the tools by name. Each runtime carries its own role, so t
-&lt;h2 id="storing-menus-carts-and-orders"&gt;Storing menus, carts, and orders&lt;/h2&gt;
-&lt;p&gt;Amazon DynamoDB tables cover the workflow. They are Customers (profiles for recognizing returning customers), Orders (history with pickup location and channel), Menu (items, prices, and availability), Carts (in-progress carts with a time-to-live), and Locations (coordinates, hours, and tax
-&lt;h2 id="finding-a-pickup-location"&gt;Finding a pickup location&lt;/h2&gt;
-&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/location/latest/developerguide/what-is.html" target="_blank" rel="noopener"&gt;Amazon Location Service&lt;/a&gt; helps a customer find a pickup spot without much typing. The agent passes a ZIP code or address to be geocoded into coordinates. The backe
-&lt;h2 id="recognizing-a-customer-without-a-login"&gt;Recognizing a customer without a login&lt;/h2&gt;
-&lt;p&gt;A WhatsApp customer doesn’t sign in, so the system uses the phone number as the basis for identity. It hashes the E.164 number with a secret pepper in AWS Systems Manager Parameter Store, and the result becomes the &lt;code&gt;customer_id&lt;/code&gt; (&lt;code&gt;"wa-" + sha256(E164 || Pep
-&lt;h2 id="ordering-walkthrough"&gt;Ordering walkthrough&lt;/h2&gt;
-&lt;p&gt;There is no web UI or test client. Message or call the WhatsApp Business number from a phone with WhatsApp installed. This example shows a typical exchange (lines prefixed “Agent” are the assistant’s replies, tool calls in brackets).&lt;/p&gt;
-&lt;div class="hide-language"&gt;
- &lt;pre&gt;&lt;code class="language-text"&gt;Customer: What's on the menu near 75201?
-
-Agent: [tools: GeocodeAddress, GetNearestLocations, GetMenu]
- Here's what's available at Amazing Burgers - Dallas:
- - Burger Combo ($8.99)
- - Chicken Tenders ($6.49)
- ...
-
-Customer: A burger combo and a milkshake, please.
-
-Agent: [tools: AddToCart, GetCart]
- Added to your cart:
- - 1x Burger Combo - $8.99
- - 1x Milkshake - $3.49
- Total: $12.48. Want me to place the order?
-
-Customer: Yes.
-
-Agent: [tools: PlaceOrder]
- Your order is placed and is being prepared for pickup at
- Amazing Burgers - Dallas. I'll let you know when it's ready.&lt;/code&gt;&lt;/pre&gt;
-&lt;/div&gt;
-&lt;p&gt;Voice notes and voice calls run the same flow through Amazon Nova 2 Sonic. You speak your order and the agent replies with voice. As the order advances, the order-notifier delivers proactive status updates back to WhatsApp. You can follow conversations in Amazon CloudWatch Logs.&lt;/p&gt;
-&lt;h2 id="cost"&gt;Cost&lt;/h2&gt;
-&lt;p&gt;You pay for the AWS services the system uses, and separately for Meta’s WhatsApp messaging fees. Costs scale primarily with conversation volume and the share of voice traffic, which consumes more resources per session than text. This example deploys all three channels (text, voice note, and
-&lt;h2 id="things-to-consider"&gt;Things to consider&lt;/h2&gt;
-&lt;p&gt;WhatsApp can also receive images and documents. This solution focuses on order taking and does not act on those attachments. If your use case needs them, you can configure the backend and the chat agent to handle them, because Amazon Nova 2 Lite is already multimodal. The agent could read a
-&lt;p&gt;The pattern also reaches beyond restaurants. The core building blocks are one business number, several conversation channels, shared memory, and MCP tools in front of a backend. The same shape fits retail support, healthcare intake, field service scheduling, and many other domains. You adap
-&lt;p&gt;For production deployments, consider enabling &lt;a href="https://aws.amazon.com/bedrock/guardrails/" target="_blank" rel="noopener"&gt;Amazon Bedrock Guardrails&lt;/a&gt; to add content filtering and grounding validation. This helps make sure agent responses stay within policy boundaries a
-&lt;h2 id="clean-up-resources"&gt;Clean up resources&lt;/h2&gt;
-&lt;p&gt;To avoid ongoing charges, remove the resources when you are done. The cleanup script destroys stacks in reverse order, each consumer before its producers.&lt;/p&gt;
-&lt;div class="hide-language"&gt;
- &lt;pre&gt;&lt;code class="language-bash"&gt;./scripts/cleanup-all.sh --dry-run # preview without removing anything
-./scripts/cleanup-all.sh # delete every stack the deploy created&lt;/code&gt;&lt;/pre&gt;
-&lt;/div&gt;
-&lt;p&gt;Cleanup is destructive. It deletes the order history in Amazon DynamoDB, the pepper in Parameter Store, the Secrets Manager secrets, and the images in Amazon ECR. Back up anything you want to keep first. It does not touch the Meta side, so unsubscribe the webhook and revoke tokens in the Me
+ <dc:creator><![CDATA[Tanvi Girinath]]></dc:creator>
+ <pubDate>Tue, 08 Sep 2026 22:06:58 +0000</pubDate>
+ <category><![CDATA[Amazon Bedrock]]></category>
+ <category><![CDATA[Announcements]]></category>
+ <category><![CDATA[Intermediate (200)]]></category>
+ <guid isPermaLink="false">68d48019de714857964056351fc4d79e51c3ab9f</guid>
+
+ <description>GPT-6 Astra from OpenAI is now generally available on Amazon Bedrock. It brings deeper reasoning and sharper judgment to your most demanding tasks, running on the Amazon Bedrock inference engine built for high performance, security, and scale.</description>
+ <content:encoded>&lt;p&gt;&lt;em&gt;GPT-6 Astra from OpenAI brings greater depth and judgment to your most demanding tasks and runs on the Amazon Bedrock inference engine built for high performance, security, and scale.&lt;/em&gt;&lt;/p&gt;
+&lt;p&gt;Organizations are already running AI agents that write code, analyze data, and automate complex workflows at production scale on Amazon Bedrock. GPT-6 Astra raises the potential of what those agents can deliver. It applies deeper reasoning and sharper judgment to complex business decisions,
+&lt;p&gt;Today, GPT-6 Astra, the latest and most capable OpenAI model, is generally available on &lt;a href="https://aws.amazon.com/bedrock/" target="_blank" rel="noopener"&gt;Amazon Bedrock&lt;/a&gt;. You can call the &lt;a href="https://aws.amazon.com/bedrock/openai/" target="_blank" rel="noopener
+&lt;h2 id="greater-depth-for-complex-decisions"&gt;Greater depth for complex decisions&lt;/h2&gt;
+&lt;p&gt;GPT-6 Astra brings greater depth to work that requires you to reconcile competing inputs, trace dependencies, and determine what to prioritize. When performing financial analysis, it can help you reconcile conflicting data sources and identify discrepancies that could change a recommendatio
+&lt;p&gt;For workflows that reuse the same context across requests, such as recurring document review, codebase analysis, or agents grounded in company standards, GPT-6 Astra supports both implicit and explicit prompt caching. With explicit caching, you can set cache breakpoints to control which con
+&lt;h2 id="layered-security-and-governance-for-production-ai"&gt;Layered security and governance for production AI&lt;/h2&gt;
+&lt;p&gt;Model-level safeguards work alongside the security and governance controls of Amazon Bedrock. OpenAI evaluated GPT-6 Astra through its &lt;a href="https://cdn.openai.com/pdf/18a02b5d-6b67-4cec-ab64-68cdfbddebcd/preparedness-framework-v2.pdf" target="_blank" rel="noopener"&gt;Preparedness Fr
+&lt;p&gt;Amazon Bedrock protects your inference data and governs access at every model invocation. Zero-operator access is enforced at the chip, so even AWS operators can’t access your prompts and completions during inference. Data is encrypted in transit and at rest. Access is governed by your AWS
+&lt;p&gt;Your inference data isn’t used for model training, and using GPT-6 Astra doesn’t require you to opt into sharing your data with OpenAI. For &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/abuse-detection.html" target="_blank" rel="noopener"&gt;automated abuse detection&lt;/
+&lt;h2 id="build-code-and-work-with-astra"&gt;Build, code, and work with Astra&lt;/h2&gt;
+&lt;p&gt;You can use&amp;nbsp;GPT-6 Astra for inference, knowledge work, and software development.&lt;/p&gt;
+&lt;h3 id="for-platform-and-application-teams"&gt;Integrate Astra into your applications&lt;/h3&gt;
+&lt;p&gt;You can integrate GPT-6 Astra directly into your applications using supported Amazon Bedrock APIs. Use it to power autonomous agents that handle complex, multistep workflows, build internal tools that analyze and synthesize documents at scale, or create customer-facing applications that req
+&lt;h3 id="for-business-and-operations-teams"&gt;Turn complex tasks into finished deliverables&lt;/h3&gt;
+&lt;p&gt;ChatGPT Work is a productivity agent for turning complex business tasks into finished deliverables. With GPT-6 Astra, it can gather information across applications and files, use the web, and produce spreadsheets, slides, documents, and sites. You can control which applications and websites
+&lt;p&gt;ChatGPT Work is available through the ChatGPT desktop app for Mac and Windows. New enterprise plugins introduced alongside this release extend browser-use capabilities across business intelligence tools, Workday, Navan, and Avalara for tasks across data analytics, operations, and finance. T
+&lt;h3 id="for-development-teams"&gt;Build, test, and ship code faster&lt;/h3&gt;
+&lt;p&gt;Codex is a software engineering agent that works with local files, repositories, terminals, developer tools, and development environments to write features, fix bugs, run tests, and open pull requests. When you configure Codex to use GPT-6 Astra on Amazon Bedrock, it applies Astra’s reasoni
+&lt;p&gt;You can access Codex through the ChatGPT desktop app, CLI, VS Code, JetBrains IDEs, and Xcode. For AWS development, the&amp;nbsp;&lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/quick-start.html" target="_blank" rel="noopener"&gt;Agent Toolkit for AWS&lt;/a&gt;&amp;nbs
+&lt;h2 id="get-started"&gt;Get started&lt;/h2&gt;
+&lt;p&gt;You can get started in the &lt;a href="https://us-east-1.console.aws.amazon.com/bedrock/home?region=us-east-1#/" target="_blank" rel="noopener"&gt;Amazon Bedrock console&lt;/a&gt; or programmatically through supported Amazon Bedrock APIs. For information about supported &lt;a href="https://
+&lt;p&gt;&lt;em&gt;Interested in how Amazon Bedrock can support your team? &lt;a href="https://pages.awscloud.com/Amazon-Bedrock-Contact-Us.html" target="_blank" rel="noopener"&gt;Connect with us&lt;/a&gt; to start the conversation.&lt;/em&gt;&lt;/p&gt;
+&lt;p style="clear: both"&gt;&lt;/p&gt;
+&lt;hr style="width: 100%"&gt;
+&lt;h2&gt;About the authors&lt;/h2&gt;
+&lt;footer&gt;
+ &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt;
+ &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
+ &lt;img class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21849-1.jpg" alt="Tanvi Girinath" width="100" height="133"&gt;
+ &lt;/div&gt;
+ &lt;h3 class="lb-h4"&gt;Tanvi Girinath&lt;/h3&gt;
+ &lt;p style="overflow: hidden"&gt;Tanvi is a Product Marketing Manager for Amazon Bedrock at Amazon Web Services (AWS), where she helps customers adopt and scale AI applications and agents with Amazon Bedrock.&lt;/p&gt;
+ &lt;/div&gt;
+ &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt;
+ &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
+ &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21849-2.jpg" alt="Chris Dickens" width="100" height="133"&gt;
+ &lt;/div&gt;
+ &lt;h3 class="lb-h4"&gt;Chris Dickens&lt;/h3&gt;
+ &lt;p style="overflow: hidden"&gt;Chris is a Member of Product Staff at OpenAI focused on the OpenAI APIs. His work includes collaboration with AWS on Amazon Bedrock to make OpenAI’s frontier models widely accessible to developers.&lt;/p&gt;
+ &lt;/div&gt;
+ &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt;
+ &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
+ &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21849-3.jpg" alt="Manish Rathaur" width="100" height="133"&gt;
+ &lt;/div&gt;
+ &lt;h3 class="lb-h4"&gt;Manish Rathaur&lt;/h3&gt;
+ &lt;p style="overflow: hidden"&gt;Manish is a Senior Product Manager for Amazon Bedrock.&lt;/p&gt;
+ &lt;/div&gt;
+&lt;/footer&gt;</content:encoded>
+
+
+
+ </item>
+ <item>
+ <title>Pathway’s brain-inspired architecture development on Amazon SageMaker HyperPod</title>
+ <link>https://aws.amazon.com/blogs/machine-learning/pathways-brain-inspired-architecture-development-on-amazon-sagemaker-hyperpod/</link>
+
+ <dc:creator><![CDATA[Paulo Aragão]]></dc:creator>
+ <pubDate>Tue, 08 Sep 2026 19:12:51 +0000</pubDate>
+ <category><![CDATA[Amazon SageMaker HyperPod]]></category>
+ <category><![CDATA[Announcements]]></category>
+ <category><![CDATA[Intermediate (200)]]></category>
+ <category><![CDATA[Amazon SageMaker]]></category>
+ <category><![CDATA[distributed training]]></category>
+ <category><![CDATA[PyTorch]]></category>
+ <guid isPermaLink="false">7b62a76bc3853bd9ada742693ec9cd3b09d199a8</guid>
+
+ <description>Pathway's Baby Dragon Hatchling (BDH) is a brain-inspired, post-transformer architecture that reasons in latent space instead of emitting chain-of-thought tokens. See how Pathway develops and scales BDH on Amazon SageMaker HyperPod, and how BDH-CQ set a new cost-efficiency mark on
+ <content:encoded>&lt;p&gt;As AI systems take on more complex tasks, much of the industry’s progress has come from increasing model scale, training data, context length, and inference-time computation. Instead of externalizing reasoning work as a chain-of-thought (generating extra tokens se
+&lt;p&gt;Large language models (LLMs) have transformed AI, changing how we approach tasks from code generation to creative writing. However, fundamental questions remain about general intelligence and their ability to reason over long time periods in a coherent way. Their architecture, kept roughly
+&lt;p&gt;Pathway’s BDH integrates with well-known frameworks such as PyTorch and uses &lt;a href="https://aws.amazon.com/sagemaker/ai/hyperpod/" target="_blank" rel="noopener"&gt;Amazon SageMaker HyperPod&lt;/a&gt; to scale out their training. Amazon SageMaker HyperPod helps their applied AI scienti
+&lt;h2 id="transformers-architecture-and-fundamental-limitations"&gt;Transformers: architecture and fundamental limitations&lt;/h2&gt;
+&lt;p&gt;The transformer architecture, while widely adopted for natural language processing (NLP), faces significant limitations in both training and inference workloads.&lt;/p&gt;
+&lt;p&gt;During training, transformers struggle with systematic generalization beyond their training data, particularly for long chain-of-thought reasoning tasks, and require massive amounts of data and computational effort to compensate for this limitation. The transformer architecture’s dense comp
+&lt;p&gt;At inference, transformers face other inefficiencies: the structure of their attention mechanism limits scalability, while their dense activation patterns, even with Mixture of Experts techniques, result in excessive computation and memory bandwidth usage. The fixed context window and growi
+&lt;p&gt;These challenges are fundamentally tied to the architecture’s design choices rather than only implementation details, suggesting the need for alternative approaches that better align with both computational efficiency and natural intelligence principles.&lt;/p&gt;
+&lt;blockquote&gt;
+ &lt;p&gt;&lt;em&gt;“Today’s AI pays a steep token cost for reasoning, but that cost is imposed by architecture, not by any law of intelligence. Currently, every reasoning step consumes context, adds latency, and burns compute. We show that a different architecture changes the game and opens up a wh
+&lt;/blockquote&gt;
+&lt;p&gt;— Zuzanna Stamirowska, CEO and co-founder, Pathway&lt;/p&gt;
+&lt;h2 id="bdh-a-unified-architecture-for-artificial-and-natural-intelligence"&gt;BDH: A unified architecture for artificial and natural intelligence&lt;/h2&gt;
+&lt;p&gt;&lt;a href="https://pathway.com/" target="_blank" rel="noopener"&gt;Pathway&lt;/a&gt;’s vision is to fundamentally change the way models think. Their BDH architecture is a post-transformer model that continually learns, evolves, and reasons. BDH’s architecture represents a new way to build
+&lt;p&gt;As in the brain, the interactions of BDH are defined to be sparse and local, and the connections between the neurons encode the memory and reasoning functions. This sparse activation profile (only 5 percent of neurons are typically active at a given time) supports efficient computation. The
+&lt;p&gt;BDH implements attention through a linear mechanism that operates on fixed, high-dimensional states without incurring the increased complexity characteristic of transformer models for long contexts. This allows the model to process longer sequences more efficiently, without the context leng
+&lt;p&gt;Recently, Pathway built &lt;a href="https://arxiv.org/pdf/2608.09888" target="_blank" rel="noopener"&gt;BDH-CQ, a reasoning system built on top of BDH&lt;/a&gt;. It extends BDH with in-context learning and latent iterative reasoning for visual problem-solving.&lt;/p&gt;
+&lt;p&gt;As the following sections show, BDH-CQ excels at in-context learning. Its recurrent computations over latent states support efficient parallel hypothesis exploration, where communities of neurons can represent different candidate solutions for a problem at hand. The model achieves a reasoni
+&lt;blockquote&gt;
+ &lt;p&gt;&lt;em&gt;“Customers are increasingly exploring how to move advanced reasoning from experimentation into production, where performance, efficiency, and scalability all matter. Pathway’s work training BDH-CQ on Amazon SageMaker HyperPod points to a promising path toward deploying high-perfo
+&lt;/blockquote&gt;
+&lt;p&gt;— Nicolas Tarducci, Head of Solution Architecture for Startups EMEA, Amazon Web Services&lt;/p&gt;
+&lt;h2 id="developing-bdh-architecture-on-amazon-sagemaker-hyperpod"&gt;Developing BDH architecture on Amazon SageMaker HyperPod&lt;/h2&gt;
+&lt;p&gt;Pathway uses &lt;a href="https://aws.amazon.com/sagemaker/ai/hyperpod/" target="_blank" rel="noopener"&gt;Amazon SageMaker HyperPod&lt;/a&gt; for developing its BDH architecture. Amazon SageMaker HyperPod is a purpose-built infrastructure solution for training LLMs and foundation models (FM
+&lt;p&gt;For Pathway to develop AI architectures beyond transformers, comprehensive observability of their training infrastructure is critical. Amazon SageMaker HyperPod integration with advanced monitoring tools, such as &lt;a href="https://aws.amazon.com/prometheus/" target="_blank" rel="noopener"
+&lt;p&gt;This comprehensive observability stack helps reduce development cycles when iterating on new architectural approaches, optimizes cost-performance ratio for resource-intensive training, and ensures reliability and reproducibility of results across training runs. For more information about th
+&lt;p&gt;Amazon Elastic Fabric Adapter (EFA) integrates natively with the NVIDIA CUDA platform for GPU-accelerated computation and the NVIDIA Collective Communications Library (NCCL) for communication across GPUs. It allows distributing data, weights, activations, and more, in a reliable and scalabl
+&lt;h2 id="proof-of-bdh-architecture-bdh-cq-achieving-29.2-pass2-on-arc-agi"&gt;Proof of BDH architecture: BDH-CQ achieving 29.2% pass@2 on ARC-AGI&lt;/h2&gt;
+&lt;p&gt;BDH-CQ achieved 29.2 percent pass@2 on the ARC-AGI benchmark at a cost of US $0.0007 per task.&lt;/p&gt;
+&lt;p&gt;Thanks to Pathway’s new approach to reasoning, in-context task acquisition and iterative latent computation, BDH-CQ changed the cost-accuracy Pareto frontier on the ARC-AGI-1 benchmark, as of August 2026.&lt;/p&gt;
+&lt;p&gt;ARC-AGI-1 presents an AI system with a small number of before-and-after examples that illustrate an unknown visual rule. The system must then infer that rule and apply it to a new grid, a capability often associated with human-like intelligence. BDH-CQ performs iterative computation inside
+&lt;p&gt;The pattern that ARC-AGI explores resembles real-world challenges where systems must reason reliably as information and constraints change, such as investigating cyber security incidents, coordinating transportation networks, responding to real-time industrial operations, and operating auto
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
-&lt;p&gt;This post walked through the architecture and deployment of a multimodal WhatsApp ordering assistant that takes an order end to end over text, voice notes, and voice calls on a single business number. An asynchronous webhook accepts traffic fast and queues the rest of the work. Three runtim
+&lt;p&gt;BDH is a new large language model architecture inspired by scale-free biological networks. It draws on principles biology got right, namely local interaction, sparse activity, persistent state, and continual adjustment, and applies them to a modern sequence model. It offers a GPU-friendly i
+&lt;p&gt;To begin exploring and implementing the BDH architecture, you can access detailed &lt;a href="https://arxiv.org/abs/2608.09888" target="_blank" rel="noopener"&gt;technical documentation&lt;/a&gt; and a sample implementation through Pathway’s &lt;a href="https://github.com/pathwaycom/bdh" ta
+&lt;p&gt;Teams that push the boundaries of AI model development can use Amazon SageMaker HyperPod to maintain efficiency and reliability at scale. Amazon SageMaker HyperPod training offers a robust solution to common challenges in large model training. To learn more about Amazon SageMaker HyperPod,
&lt;p style="clear: both"&gt;&lt;/p&gt;
&lt;hr style="width: 100%"&gt;
&lt;h2&gt;About the authors&lt;/h2&gt;
&lt;footer&gt;
&lt;div class="blog-author-box" style="padding-top: 2.0em"&gt;
&lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
- &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-5.jpg" alt="Salman Ahmed" width="100" height="133"&gt;
+ &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/02/ML-21697-1.jpg" alt="Paulo Aragão" width="100" height="133"&gt;
&lt;/div&gt;
- &lt;h3 class="lb-h4"&gt;Salman Ahmed&lt;/h3&gt;
- &lt;p style="overflow: hidden"&gt;Salman is a Senior Technical Account Manager at AWS, specializing in helping customers design, implement, and optimize their AWS environments. He combines deep networking expertise with a passion for exploring emerging technologies to help organizations get the mo
+ &lt;h3 class="lb-h4"&gt;Paulo Aragão&lt;/h3&gt;
+ &lt;p style="overflow: hidden"&gt;Paulo is a Principal WW Specialist Solutions Architect focused on helping customers build their Frontier AI strategy on AWS. With over 20 years of experience dealing with High Performance Computing and AIML projects, he is passionate about working backwards from c
&lt;/div&gt;
&lt;div class="blog-author-box" style="padding-top: 2.0em"&gt;
&lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
- &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-6.jpg" alt="Sergio Barraza" width="100" height="133"&gt;
+ &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/02/ML-21697-2.jpg" alt="Rodrigo Merino" width="100" height="133"&gt;
&lt;/div&gt;
- &lt;h3 class="lb-h4"&gt;Sergio Barraza&lt;/h3&gt;
- &lt;p style="overflow: hidden"&gt;Sergio is a Senior Technical Account Manager at AWS, helping customers design and optimize cloud solutions. With more than 25 years in software development, he guides customers through AWS services adoption. Outside work, Sergio is a multi-instrument musician play
+ &lt;h3 class="lb-h4"&gt;Rodrigo Merino&lt;/h3&gt;
+ &lt;p style="overflow: hidden"&gt;Rodrigo is a Generative AI Solutions Architect Manager at AWS. With over a decade of experience deploying emerging technologies, from IoT to GenAI, Rodrigo guides customers to accelerate their AI/ML and generative AI journeys. He specializes in helping organizatio
&lt;/div&gt;
&lt;div class="blog-author-box" style="padding-top: 2.0em"&gt;
&lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
- &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/ML-21164-7.jpg" alt="Ravi Kumar" width="100" height="133"&gt;
+ &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/02/ML-21697-3.jpg" alt="Ludovic Arnould" width="100" height="133"&gt;
&lt;/div&gt;
- &lt;h3 class="lb-h4"&gt;Ravi Kumar&lt;/h3&gt;
- &lt;p style="overflow: hidden"&gt;Ravi is a Senior Technical Account Manager in AWS Enterprise Support who helps customers in the travel and hospitality industry to streamline their cloud operations on AWS. He is a results-driven IT professional with over 20 years of experience. Ravi is passionate
+ &lt;h3 class="lb-h4"&gt;Ludovic Arnould&lt;/h3&gt;
+ &lt;p style="overflow: hidden"&gt;Ludovic is a Frontier AI Model Solutions Architect at Pathway, specializing in the design and deployment of advanced AI solutions for enterprise customers. He holds a PhD in Machine Learning from Sorbonne Université and has published research at ICML, ICLR, and AI
&lt;/div&gt;
&lt;/footer&gt;</content:encoded>
@@@ -217,461 +159,659 @@ Agent: [tools: PlaceOrder]
</item>
<item>
- <title>Designing lifecycle policies for AgentCore memory</title>
- <link>https://aws.amazon.com/blogs/machine-learning/designing-lifecycle-policies-for-agentcore-memory/</link>
+ <title>Amazon SageMaker Feature Store introduces UpdateRecord for feature-level writes</title>
+ <link>https://aws.amazon.com/blogs/machine-learning/amazon-sagemaker-feature-store-introduces-updaterecord-for-feature-level-writes/</link>
- <dc:creator><![CDATA[Akarsha Sehwag]]></dc:creator>
- <pubDate>Fri, 04 Sep 2026 17:20:04 +0000</pubDate>
- <category><![CDATA[Advanced (300)]]></category>
- <category><![CDATA[Amazon Bedrock AgentCore]]></category>
+ <dc:creator><![CDATA[Mona Mona]]></dc:creator>
+ <pubDate>Tue, 08 Sep 2026 18:29:15 +0000</pubDate>
+ <category><![CDATA[Amazon Machine Learning]]></category>
+ <category><![CDATA[Amazon SageMaker AI]]></category>
+ <category><![CDATA[Announcements]]></category>
+ <category><![CDATA[Artificial Intelligence]]></category>
+ <category><![CDATA[Intermediate (200)]]></category>
<category><![CDATA[Technical How-to]]></category>
- <category><![CDATA[Thought Leadership]]></category>
- <guid isPermaLink="false">bf15bf1accc979b1b510192d304b5091e2a44dc0</guid>
+ <guid isPermaLink="false">ea7f9667a432b227c77a23d10cd0038932138567</guid>
- <description>Long-running AI agents accumulate outdated memories that degrade quality and create compliance risk. Learn how to design memory lifecycle policies for Amazon Bedrock AgentCore: scoring, consolidating, and pruning agent memories on a nightly AWS Step Functions workflow, with a deplo
- <content:encoded>&lt;p&gt;Memory lifecycle policies help long-running agents on Amazon Bedrock AgentCore stay effective by systematically managing what they remember and forget. Your agent generates memories from every conversation it conducts. If you don’t actively manage these memories,
-&lt;p&gt;After months of production use, problems emerge. We observed a customer support agent reference a billing dispute resolved four months earlier, treating it as active. Another agent repeated outdated deployment advice because its memory still contained a superseded runbook.&lt;/p&gt;
-&lt;p&gt;In this post, we introduce memory lifecycle management for AI agents: the practice of systematically scoring, consolidating, and pruning agent memories over time. We walk through a deployable architecture using &lt;a href="https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-agentco
-&lt;p&gt;This solution targets agents that accumulate high volumes of interaction data over weeks or months, such as customer support agents, sales advisors, and IT helpdesk bots. For lower-volume agents like personal assistants, you might start with time-to-live (TTL) expiration and General Data Pr
-&lt;h2 id="solution-overview"&gt;Solution overview&lt;/h2&gt;
-&lt;p&gt;This solution combines a shared memory taxonomy with three lifecycle policies that run as a nightly workflow. We begin with the memory types that shape those policies.&lt;/p&gt;
-&lt;h3 id="memory-types"&gt;Memory types&lt;/h3&gt;
-&lt;p&gt;Before designing lifecycle policies, we need a shared vocabulary for what agents remember. We categorize agent memory into three types, each with different retention requirements.&lt;/p&gt;
+ <description>Amazon SageMaker Feature Store now supports feature-level writes. With the new UpdateRecord API, you can update one or more feature values in a single call without reading or rewriting the entire record. It is available for both the Standard (Amazon DynamoDB) and In-Memory (Amazon
+ <content:encoded>&lt;p&gt;We are excited to announce &lt;a href="https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_feature_store_UpdateRecord.html"&gt;&lt;em&gt;feature-level writes&lt;/em&gt;&lt;/a&gt; for Amazon SageMaker Feature Store. &lt;a href="https://aws.amazon.com/sage
+&lt;h2 id="the-challenge-full-record-writes-for-every-change"&gt;The challenge: Full-record writes for every change&lt;/h2&gt;
+&lt;p&gt;A Feature Group is a logical collection of features that are related, and are used by one or more ML models to either train a new model or generate inference predictions. Until now, updating even a single feature value in a feature group required a full read-modify-write cycle using &lt;a h
+&lt;ol type="1"&gt;
+ &lt;li&gt;&lt;strong&gt;Read&lt;/strong&gt; the complete record (all features) by using &lt;a href="https://docs.aws.amazon.com/boto3/latest/reference/services/sagemaker-featurestore-runtime/client/get_record.html" target="_blank" rel="noopener"&gt;GetRecord&lt;/a&gt;.&lt;/li&gt;
+ &lt;li&gt;&lt;strong&gt;Merge&lt;/strong&gt; the new value in application code.&lt;/li&gt;
+ &lt;li&gt;&lt;strong&gt;Write&lt;/strong&gt; the entire record back with &lt;a href="https://docs.aws.amazon.com/boto3/latest/reference/services/sagemaker-featurestore-runtime/client/put_record.html" target="_blank" rel="noopener"&gt;PutRecord&lt;/a&gt;.&lt;/li&gt;
+&lt;/ol&gt;
+&lt;p&gt;This pattern added extra latency per update, consumed unnecessary read capacity, and introduced race conditions when multiple pipelines concurrently updated different features in the same record. In the worst case, one pipeline’s write could silently overwrite another’s. This is a classic l
+&lt;p&gt;Beyond latency and correctness issues, the read-modify-write pattern also carries a cost overhead. The additional GetRecord calls required before each write generate extra &lt;a href="https://aws.amazon.com/sagemaker/ai/pricing/" target="_blank" rel="noopener"&gt;Read Capacity Units (RCUs)&
+&lt;h2 id="introducing-updaterecord"&gt;Introducing UpdateRecord&lt;/h2&gt;
+&lt;p&gt;The &lt;a href="https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_feature_store_UpdateRecord.html" target="_blank" rel="noopener"&gt;UpdateRecord API&lt;/a&gt; call removes the read-modify-write cycle. You provide only the features that you want to change, and Amazon SageMaker F
+&lt;h3 id="updaterecord-api-data-flow"&gt;UpdateRecord API data flow&lt;/h3&gt;
+&lt;p&gt;The following diagram illustrates how the UpdateRecord API processes a partial write request and synchronizes with the offline store.&lt;/p&gt;
+&lt;div id="attachment_138746" style="width: 1634px" class="wp-caption alignleft"&gt;
+ &lt;img aria-describedby="caption-attachment-138746" loading="lazy" class="size-full wp-image-138746" src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/09/03/Screenshot-2026-09-03-at-11.34.17 AM.png" alt="" width="1624" height="710"&gt;
+ &lt;p id="caption-attachment-138746" class="wp-caption-text"&gt;Figure 1: UpdateRecord API data flow to the online and offline stores&lt;/p&gt;
+&lt;/div&gt;
+&lt;p&gt;The client application calls the UpdateRecord API with only the changed features. The Feature Store service validates AWS Identity and Access Management (IAM) permissions, checks EventTime ordering to reject stale writes, and performs an atomic merge. The blue arrow represents the single op
+&lt;h3 id="request-shape"&gt;Request shape&lt;/h3&gt;
+&lt;div class="hide-language"&gt;
+ &lt;pre&gt;&lt;code class="language-plaintext"&gt;POST /FeatureGroup/{FeatureGroupName}/Record
+
+{
+ "RecordIdentifierValueAsString": "user_123",
+ "Features": [
+ { "FeatureName": "risk_score", "ValueAsString": "0.87" },
+ { "FeatureName": "last_login", "ValueAsString": "2026-07-21T08:15:00Z" }
+ ],
+ "TtlDuration": { // optional

Diff display stops at 400 lines. The line counts above are from the whole diff. 94 lines shown here cut at 300 characters. The raw artifact at this commit is linked above.