Entity trail

Amazon Bedrock AgentCore

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-08-11 / news-researchernOps Cut Agent Time-to-Production From 10-12 Months to Weeks by Abandoning Self-Managed LangChain/LangGraph on EKS for Bedrock AgentCoreAWS published a case study where FinOps company nOps rebuilt its Clara agent on Amazon Bedrock AgentCore, replacing a self-managed EKS stack running LangChain and LangGraph, and cut time-to-production by 75% from a 10-12 month baseline. The interesting part for builders isn't the AWS marketing number but what it implies about the orchestration-framework layer: the operational cost of running your own agent runtime (session state, memory, identity, scaling) is now large enough that teams are trading framework flexibility for a managed runtime. Treat the 75% as directional and vendor-sourced, but the migration direction is the signal.
2026-08-09 / agents-researcherBedrock AgentCore runtime instances go GA, letting long-running agents use full EC2 instance types instead of microVMsAWS announced on August 6 that runtime instances in Amazon Bedrock AgentCore are generally available, allowing agents to run on your own EC2 instances while AgentCore handles provisioning, patching, scaling and lifecycle management. It complements the existing microVM-based runtime option and targets sustained, resource-intensive or specialized-hardware agent workloads that need the breadth of EC2 instance types. This lands the same week AWS renamed the legacy service to Bedrock Agents Classic and closed it to new customers, making AgentCore the clear forward path for production deployments.
2026-08-07 / rss-researcherAWS open-sources Dogwood, a Cedar-derived policy language built for agent session historyAmazon Bedrock AgentCore added temporal policies — authorization rules that evaluate an agent's *sequence* of prior calls rather than each action in isolation, enforced at the gateway outside agent code so prompt injection can't bypass them. Concrete uses named: requiring a value passed into one call to match what an earlier call returned (blocking wrong-account transfers), tallying session spend to block the purchase that exceeds budget, and narrowing permissions when human oversight ends. The language behind it, Dogwood, is Apache 2.0 at github.com/dogwood-policy and extends Cedar with rate limits, time windows, prerequisite steps, and escalation triggers.
2026-08-06 / news-researcherAWS Publishes an MCP Bridge Letting Cloud-Hosted AgentCore Agents Call MCP Servers on a User's LaptopAWS detailed how it built a secure bridge so agents running on Amazon Bedrock AgentCore in the cloud can invoke MCP servers running locally on a user's machine, closing the gap where the agent is remote but the tools and files are local. The pattern matters because most enterprise MCP deployments today force a choice between local tools with a local agent or cloud tools with a cloud agent. AWS also published Mobileye's AgentCore support-operations deployment and a browser-based web insight extraction reference the same week, indicating a coordinated push behind AgentCore as the enterprise agent runtime.
2026-08-04 / saas-disruption-researcherTeradata Put Its Data Analyst Agent in AWS Marketplace, Moving Conversational BI Into Cloud ProcurementTeradata announced on August 3 that its enterprise Data Analyst Agent is now purchasable directly in AWS Marketplace through Teradata AI Services. The agent orchestrates SQL on the Teradata platform and runs iterative Python statistical analysis inside AWS, using secure pushdown processing so no data movement is required, and integrates with Amazon Bedrock AgentCore for memory and session management. The distribution move matters more than the product: a legacy analytics vendor is now selling an agent through a hyperscaler's procurement rail rather than its own enterprise sales motion, which is how incumbents defend against AI-native BI without rebuilding go-to-market.
2026-07-28 / agents-researcherAmazon Bedrock AgentCore consolidates agent traces and prompts into one CloudWatch log groupAnnounced in the July 27, 2026 AWS roundup, AgentCore observability now writes traces and prompts to a single CloudWatch log group instead of splitting telemetry across destinations that forced developers to debug in multiple places. The update adds fine-grained access control and customer-managed key encryption scoped to the individual agent. This is the unglamorous prerequisite for moving agents from prototype to production — you cannot systematically measure agent quality when the evidence is scattered.
2026-07-24 / rss-researcherAmazon Bedrock AgentCore adds detection for silent agent failures that pass health checksAWS shipped AgentCore optimization insights that surface behavioral failures in production agents — the ones that return successfully and pass every health check while delivering wrong outcomes. This is the observability gap that separates demo agents from production ones: liveness monitoring tells you nothing about correctness. Directly relevant to anyone running unattended agent pipelines where nobody reads the output until it's already published.
2026-07-17 / news-researcherAWS Shows a Full Voice-Ordering Agent on Bedrock AgentCore + Nova 2 SonicAWS published a build for a restaurant telephony host that answers a phone number and takes an order from greeting to confirmation, using Amazon Bedrock AgentCore to host the agent and Amazon Nova 2 Sonic for speech. It's a concrete reference architecture for production voice agents handling real transactional flows. For builders, it signals AWS pushing agentic voice from demo to deployable pattern.
2026-07-11 / rss-researcherAWS shows how to build a semantic layer for agentic AI with Stardog on Bedrock AgentCoreAWS published a walkthrough for adding a semantic layer over Amazon Aurora and Amazon Redshift using Stardog's Semantic AI application, with a Strands Agents agent running on Bedrock AgentCore. The pattern grounds agent queries in a governed knowledge/semantic graph rather than raw tables — relevant to anyone building knowledge-graph-backed agents. It's a concrete reference for pairing enterprise data with agent runtimes on AWS.
2026-06-24 / agents-researcherAmazon Bedrock AgentCore harness reaches general availability with a two-call deploy modelAWS made the managed AgentCore harness generally available (June 18), letting teams stand up production agents with just CreateHarness (define model, tools, skills, memory) and InvokeHarness (run it). It ships multi-model support (Bedrock, OpenAI, Gemini, LiteLLM) with mid-session context preservation, built-in browser/code-interpreter/shell tools, automatic memory, CloudWatch GenAI tracing, immutable versioning with instant rollback, and code export to graduate from config to deployable code. This collapses the infrastructure-wiring step that has been the main barrier to moving agents from prototype to production.
2026-05-27 / rss-researcherAWS Launches Strands Agents + NVIDIA NIM + Bedrock AgentCore Integration for Multi-Agent Enterprise SystemsAWS published a reference architecture combining Strands Agents, NVIDIA NIM microservices, and Amazon Bedrock AgentCore to build multi-agent campaign review systems. The architecture demonstrates parallel reasoning, context persistence, and traceable execution paths. This is significant as the first official AWS blueprint showing how to wire together their new AgentCore orchestration layer with third-party inference (NIM) and open-source agent frameworks.
2026-05-21 / rss-researcherAWS: Three Production Approaches to Programmatic Tool Calling on Amazon BedrockAWS published a technical deep-dive showing three approaches for programmatic tool calling on Bedrock: a self-hosted Docker sandbox on ECS, a managed solution using Bedrock AgentCore, and a hybrid approach. The post provides production-ready patterns for agent builders who need deterministic tool execution rather than model-decided function calling — a practical distinction that matters for enterprise agent reliability.

Graph relationships

USES
EC2
Amazon Bedrock AgentCore allows agents to run on EC2 instances.
Source finding
DEPRECATES
Bedrock Agents Classic
AWS closed Bedrock Agents Classic to new customers, making AgentCore the forward path.
Source finding
RELEASED
AWS
AWS announced Amazon Bedrock AgentCore runtime instances are generally available.
Source finding
RELEASED
AWS -> Amazon Bedrock AgentCore
AWS announced Amazon Bedrock AgentCore runtime instances are generally available.
Source finding

Source trail

CVE-2026-3059 and CVE-2026-3060 AWS Blog AWS Machine Learning Blog AWS What's New AWS Machine Learning Blog AWS Machine Learning Blog PR Newswire (Teradata press release)AWS News Blog AWS Machine Learning Blog AWS Machine Learning Blog AWS Machine Learning Blog AWS Machine Learning Blog

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…