# AWS October 2026 ICYMI: Bedrock Models, AgentCore Gateway, and Strands Updates > Source: > Published: 2026-11-11 00:00:00+00:00 **Amazon Web Services published an [ICYMI recap on November 11, 2026](https://aws.amazon.com/blogs/machine-learning/icymi-what-landed-for-ai-builders-in-october-2026/?ref=explainx)** that bundles **October Bedrock model launches**, **[AgentCore](https://aws.amazon.com/bedrock/agentcore/?ref=explainx) production features**, and **Strands open-source agent tooling**. The thesis: builders need **model choice**, **failover**, **grounded outputs**, and **visible cost** as agents enter core workflows. This guide translates the AWS post into **decisions for teams already on Bedrock** — and points to deeper explainx.ai coverage where we already reviewed individual launches. ## TL;DR table from AWS October | Area | October highlight (per AWS) | |---|---| | Models | Haiku 5.5, GPT-6.1 Terra GA, Nova 2.5 Sonic, GLM 5.3, Pegasus 1.5 | | AgentCore | CLI 1.0 GA, gateway fallback, Step Functions as tools | | Quality | Structured JSON on all Claude Bedrock models; web search domain filters | | Cost | AgentCore memory usage pricing; Bedrock Cost Explorer dimensions | | Strands | Bidi voice GA, Box sandbox preview, Evals red teaming | ## Match the model to the task Routing workloads to the cheapest capable Bedrock model ID for each agent task AWS frames October as **right model per workload**, not one flagship for everything. ### Claude Haiku 5.5 for subagents Anthropic positions Haiku 5.5 as **cheaper parallel workers** with **effort controls**. AWS cites ~** 75% lower cost** than Haiku 4.5 on many tasks. Pattern: **Opus plans**, **Haiku executes** coding, browser, and tool chores. See our [GLM on Bedrock enterprise IDs guide](https://explainx.ai/blog/glm-5-3-amazon-bedrock-enterprise-coding-model-ids-2026) for another **specialist model** pattern. ### GPT-6.1 Terra generally available AWS says Terra matches **GPT-6 Astra** on **Agents' Last Exam** with **3x faster** completion and **50%+ lower** token prices versus GPT-6.1 Sol and GPT-5.6 Terra. Inputs up to **1M tokens** suit document-heavy agents. We covered Terra economics in [GPT-6.1 Terra launch benchmarks](https://explainx.ai/blog/gpt-6-1-terra-launch-1-5-dollar-pricing-computer-use-benchmarks-2026). Bedrock GA matters if your IAM and VPC endpoints already live on AWS. ### Nova 2.5 Sonic for voice Speech-to-speech with better **tool-calling** at same price tier as Nova 2 Sonic, per AWS. Pair with [Deepgram bidirectional streaming metering](https://explainx.ai/blog/aws-sagemaker-bidirectional-streaming-usage-metering-deepgram-2026) if you meter telephony stacks. ### GLM 5.3 and Pegasus 1.5 specialists **GLM 5.3** targets long-horizon coding for **eligible enterprise** Bedrock customers. **TwelveLabs Pegasus 1.5** turns full videos into **time-coded metadata** in one pass — useful for media RAG without a custom ingestion DAG. ### GovCloud expansions Haiku 5.5 and GPT-5.6 families with **cross-region inference** plus **Daybreak Red** for authorized security work. Regulated teams get more IDs without abandoning **US sovereignty** constraints. ## AgentCore: from laptop to operations ### AgentCore CLI 1.0 AWS says CLI **1.0** rebuilds startup time and unifies commands for harnesses, runtimes, memory, identity, gateways, and payments. Existing projects migrate with **one command**. Local iteration aligns with [AWS emulator for agent testing](https://explainx.ai/blog/aws-emulator-local-testing-agents-maintained-november-2026) and [AgentCore FAST template](https://explainx.ai/blog/aws-genai-23-open-source-reusable-assets-agentcore-fast-november-2026) assets we covered November 11. ### Gateway model fallback Failover routing when a primary Bedrock model throttles or becomes unreachable **InvokeModel APIs** through **AgentCore Gateway** can follow a **provider chain** when primaries throttle. Circuit breaker skips bad destinations. Private VPC targets can use **your private CA**. That is the AWS-native answer to [LiteLLM-style gateways](https://explainx.ai/blog/respan-gateway-open-source-rust-ai-gateway-plugins-litellm-alternative-2026) for Bedrock-only shops. ### Step Functions as tools Expose **existing workflows** — refunds, provisioning, approvals — without rewriting business rules inside LLM prompts. Agents choose **when**; Step Functions enforce **how**. Compare with [Trovata treasury agents on AgentCore](https://explainx.ai/blog/trovata-treasury-agents-bedrock-agentcore-aws-2026) for finance-shaped examples. ## Trust layers: JSON, search, guardrails ### Structured outputs on all Claude Bedrock models Schema-compliant **JSON without custom parsers**, per AWS. Critical for ticketing, ERP, and CMDB agents. ### Web search domain filters OpenAI Responses API path on Bedrock search supports **allow/block lists** (up to 100 domains each) plus **geography**. **Guardrails contextual grounding** Standard tier matches Classic pricing with broader language support. For decision-layer cheap checks before expensive models, see [AgentCore evaluations with Jev and Strands Decider](https://explainx.ai/blog/amazon-bedrock-agentcore-evaluations-decision-models-jev-strands-decider-screening-layer-guide-2026). ## FinOps: memory and Cost Explorer Spend visibility broken down by Bedrock model, provider, and inference feature ### AgentCore memory pricing Short-term memory bills on **data moved**, not flat events. AWS claims **most workloads cheaper**, especially small payloads. TTL on long-term memory controls retention cost. Pair with [Bedrock tokenomics data lake](https://explainx.ai/blog/amazon-bedrock-tokenomics-data-lake-finops-2026) if finance wants model-level chargeback. ### Cost Explorer dimensions **Model, provider, inference type, feature** breakdowns in Cost Explorer, Budgets, and dashboards — no extra fee, per AWS. **Advanced Prompt Optimization** can shorten prompts when eval scores hold. ## Strands open source lane ### Bidi Agents GA Two-way **speech-to-speech** agents with **background reconnect** past provider session limits. Supports **Nova Sonic, OpenAI, Gemini** in Strands. ### Strands Box preview Local **policy sandbox** with deterministic tool enforcement across direct calls, MCP, and generated code. Works with any model/framework — think [agent sandbox comparison](https://explainx.ai/blog/agent-sandboxes-coding-agents-compared-e2b-modal-daytona-guide-2026) but AWS-flavored. ### Strands Evals red teaming Adversarial **prompt injection** suites with transcript replay. **Structured output field scoring** gives partial credit — better signal than all-or-nothing JSON tests. AWS cites **~98% ticket cost drop** when an internal system switched classification to **Strands Decider** — see [Strands Decider ticketing post](https://explainx.ai/blog/amazon-strands-decider-internal-ticketing-sonnet-replacement-2026). ## What to do this week on AWS 1. **Inventory agents** still hard-coded to one model ID — add gateway fallback chains. 2. **Move brittle JSON prompts** to structured output APIs. 3. **Expose one Step Function** as a gateway tool before building a new agent workflow. 4. **Turn on Bedrock cost dimensions** and alert on single-model spikes. 5. **Run Strands Evals** on production agent definitions before holiday traffic. ## How October fits earlier November explainx.ai posts November runs already covered **FAST assets**, **UAEF evaluation framework**, and **agent registry push sync**. October ICYMI is the **platform layer** underneath those templates: | November explainx.ai post | October ICYMI dependency | |---|---| | [GenAI 23 assets catalog](https://explainx.ai/blog/aws-genai-23-open-source-reusable-assets-agentcore-fast-november-2026) | AgentCore CLI 1.0 resource surface | | [Agent registry CloudTrail sync](https://explainx.ai/blog/aws-agent-registry-push-sync-cloudtrail-eventbridge-2026) | Production agent identity assumptions | | [Kimi K3 on Bedrock guide](https://explainx.ai/blog/kimi-k3-1-pro-amazon-bedrock-highspeed-opencode-guide-2026) | Model catalog expansion theme | ## Deep dive: why gateway fallback is not optional anymore Before October, many Bedrock agents hard-wired one `modelId`. Throttling during peak news cycles or regional inference maintenance then became **silent user-facing outages**. AgentCore Gateway fallback encodes retry logic **once** at the edge: - Clients keep existing **InvokeModel** SDK calls. - Operators maintain an **ordered list** with circuit breaking. - Private models inside VPC attach with **customer CAs** . Implementation tips AWS does not spell out in the ICYMI: 1. Put **fast cheap models** at the end of the chain, not the start — you want graceful degradation, not silent quality collapse. 2. Log **which hop served** each request for chargeback. 3. Pair with [SageMaker streaming metering patterns](https://explainx.ai/blog/aws-sagemaker-bidirectional-streaming-usage-metering-deepgram-2026) when audio agents sit behind the same gateway. ## Deep dive: structured outputs versus tool schemas Structured JSON on Claude models reduces the classic agent failure mode: **valid-looking text that fails JSON.parse**. Still define **JSON Schema** in one repo and generate both: - Bedrock structured output config - Client-side validators AWS mentions **Advanced Prompt Optimization** shortening prompts when eval scores hold — run it only after schema tests exist, or you risk shorter prompts that drop rare fields finance needs. ## Deep dive: Pegasus and multimodal RAG TwelveLabs Pegasus 1.5 on Bedrock is easy to underestimate. Full-video metadata in one pass changes **chunking strategy**: - You may index **time-coded events** instead of naive frame grabs. - Search queries can target **spoken phrases plus on-screen text** jointly. Prototype with a single compliance training video before rebuilding your entire media pipeline. Compare costs against [Multimodal Knowledge Agent benchmarks](https://explainx.ai/blog/multimodal-knowledge-agent-mka-benchmark-google-2026) if Google-side tooling is also in play. ## Deep dive: Strands Box versus production AgentCore runtime **Strands Box** is developer-preview **local policy**. **AgentCore runtime** is managed production. Use Box to **author policies** and AgentCore to **enforce them at scale**. Red teaming in Evals should run against **the same tool manifest** you deploy — injecting tools only in prod invalidates jailbreak tests. ## Regulated industry notes GovCloud additions plus **Daybreak Red** signal AWS wants **security operations agents** inside compliance boundaries. Document **which model never leaves GovCloud** in your system security plan before auditors ask. Cross-reference [UAEF universal agent evaluation framework](https://explainx.ai/blog/aws-uaef-universal-agent-evaluation-framework-2026) when mapping evaluations to October feature drops. ## Build-your-own October adoption calendar | Week | Focus | Success metric | |---|---|---| | 1 | Enable Cost Explorer Bedrock dimensions | Top-3 model spend identified | | 2 | Wire gateway fallback on one prod agent | Zero throttle pages in load test | | 3 | Convert one workflow to Step Functions tool | Agent prompt size drops measurably | | 4 | Run Strands Evals red team suite | At least one fixed jailbreak path | Announce wins to finance using **AgentCore memory** new pricing receipts — small payloads should show invoice movement within a billing cycle. ## Ultrafast mode and coding assistants AWS notes **GPT-6.1 Sol Ultrafast mode** for latency-sensitive coding assistants on Bedrock. Treat Ultrafast as a **separate SLO tier** in your router: route only keystroke-completion style tasks, not multi-file refactors, unless evals prove quality holds. Document the mode in runbooks so on-call engineers know throttling fallbacks may land on **non-Ultrafast** IDs mid-incident. ## Community models versus enterprise gates **GLM 5.3** availability is **eligible enterprise customers** only on Bedrock. Do not bake GLM into public-facing agent SLAs until entitlement checks pass in your payer account. AWS closes the ICYMI with links to **Bedrock**, **AgentCore CLI**, and **Strands Harness SDK** — treat those three URLs as the official on-ramps, not secondary blogs, when you file internal architecture decision records. ## Related reading *Release list accurate to AWS Machine Learning Blog ICYMI published November 11, 2026.*