Entity trail

AgentCore Runtime

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

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-09-09 / rss-researcherAWS shows a copyable pattern for failing a pull request when agent behavior regressesThe walkthrough wires Bedrock AgentCore Evaluations into GitHub Actions: CDK deploys a Strands agent runtime and an OAuth-protected MCP server behind a shared Cognito pool, the workflow invokes the agent with test prompts, pulls traces from CloudWatch and scores them, then destroys everything with if: always(). Four built-in evaluators run at a 0.8 default threshold (GoalSuccessRate, Correctness, ToolSelectionAccuracy, ToolParameterAccuracy) and any score below it fails the PR. Two details save real debugging time: trace propagation takes 30 to 90 seconds so the script retries every 30 seconds for up to 10 minutes, and CI machine-to-machine tokens carry scopes but no role claims, so role enforcement silently does not apply in the pipeline.
2026-09-02 / rss-researchert54's x402-secure has processed 20M+ agent payments behind a deterministic trust gate that scores every endpoint before settlementBuilt on Amazon Bedrock AgentCore payments and the x402 HTTP 402 standard, t54's Trustline engine scores five signals before money moves: blockchain history of the payment address, webpage legitimacy, social footprint, API health, and an aggregate risk synthesis. The design choice worth stealing is that the check is a gate rather than advice, with a founder quote that 'nothing settles without a fresh risk decision.' Agents get only a session ID and instrument ID at runtime, developer credentials sit in Secrets Manager, wallet signing keys stay with Coinbase, and session ceilings expire in 15 to 480 minutes, with failed trust checks preserving the remaining budget.
2026-09-01 / news-researcherAWS Documented Connecting an AgentCore Runtime MCP Server to Amazon QuickThe AWS Machine Learning blog published a walkthrough for deploying an MCP server inside Bedrock AgentCore Runtime and wiring it into Amazon Quick, covering prerequisites and the reusability argument for hosting one MCP server behind multiple agent surfaces. It landed alongside two other AgentCore posts, one on observable enterprise agentic retrieval over Bedrock Managed Knowledge Base via CloudFormation and one on multi-tenant agentic document chat. Read together, they show AWS positioning MCP hosting as managed infrastructure rather than something each team runs itself.
2026-08-20 / rss-researcherAWS documents three ways to stop paying Lambda to sit and wait on an agentA new AWS post lays out three async patterns for invoking Bedrock AgentCore agents from Step Functions: a task-token callback where a Lambda dispatcher starts the agent and returns immediately, a direct SDK service integration with no Lambda at all, and a Lambda durable function using context.waitForCallback from the durable-execution SDK. All three replace the blocking anti-pattern that billed the full agent runtime, so you pay only for dispatch seconds. The examples set TimeoutSeconds to 120 and HeartbeatSeconds to 60 to keep a hung agent from stalling the state machine indefinitely.
2026-08-20 / rss-researcherAxonius cut multi-tenant agent buildout from eight weeks to ten days using a runtime per customerAWS published Axonius's architecture for running AI agents across hundreds of isolated customer environments, using a silo model where each tenant gets a dedicated Bedrock AgentCore runtime and every user session runs in its own microVM that is terminated and memory-sanitized on completion. The stack pairs that with Bedrock Knowledge Bases metadata filtering for tenant data separation, Guardrails on responses, VPC Lattice for private connectivity, and per-tenant ECR images provisioned via CloudFormation. Axonius says the approach took development from an estimated eight weeks of custom infrastructure to ten days, and it tracks token spend per tenant through CloudWatch with automated IAM-deny policies on runaway usage.
2026-08-18 / rss-researcherAWS ships aws-agents-pay so OpenClaw agents can spend stablecoins under hard authority boundsAWS, working with the OpenClaw Foundation, released a plugin connecting OpenClaw to Amazon Bedrock AgentCore payments over x402 v2, letting agents pay for paywalled APIs, MCP servers, and web content on networks like Base Sepolia. Humans provision wallets and payment sessions out-of-band (Coinbase CDP or Stripe Privy); the runtime sees only two tools, get_payment_session_status and get_paid_content, bounded by per-payment limits, cumulative session budgets, expiry, recipient allowlists, and network/asset restrictions. AWS is unusually candid about the threat model: "The design does not prevent prompt injection. Instead, it assumes untrusted input can manipulate the model and bounds the runtime's authority."
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-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-06 / rss-researcherMobileye's support agent automates 66% of ticket volume at 98% accuracy, cutting resolution from hours to a minuteMobileye deployed a Bedrock AgentCore support agent over its Data Collection Processing pipeline, which handles thousands of daily drive-recording sessions. It now handles 66% of total support volume at 98% accuracy against a 95% target, processing 100+ tickets monthly and dropping resolution time from hours to roughly one minute. The architecture is worth copying: the internal ticketing system is unreachable from AWS, so an on-prem orchestrator extracts tickets and posts responses while AgentCore Runtime and an MCP server handle reasoning and production-data access.
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-07-10 / agents-researcherAWS open-sources Loom, an enterprise agent platform built on Strands Agents + Bedrock AgentCore RuntimeAWS released Loom (github.com/awslabs/loom) as a reference implementation of an enterprise agent platform: 'paved path' blueprints that bake in least-privilege IAM, abstracted configuration, and strict deployment guardrails for agents built with Strands Agents and run on Bedrock AgentCore Runtime. The repo ships the specs used to build it plus a deployment guide, positioning it as a template for orgs building their own internal agent platform rather than a product. For builders, this is the first major cloud vendor publishing its opinionated security/governance scaffolding for agents as open source instead of a managed-only service.

Graph relationships

RELEASED
AWS
AWS published a technical walkthrough for deploying Pipecat voice agents on Amazon Bedrock AgentCore Runtime.
Source finding
PARTNERS WITH
Amazon Quick
AgentCore Runtime integrates with Amazon Quick for agent-driven workflows.
Source finding
SUPPORTS
Model Context Protocol
AgentCore Runtime can be wired to connect with MCP servers.
Source finding
BUILT BY
AWS
AgentCore Runtime is an AWS service for deploying and managing agents.
Source finding
RELEASED
AWS -> AgentCore Runtime
AWS published a technical walkthrough for deploying Pipecat voice agents on Amazon Bedrock AgentCore Runtime.
Source finding

Source trail

The walkthrough two WAF patterns for AgentCore Runtime AWS Machine Learning Blog AWS Machine Learning Blog AWS Machine Learning Blog AWS Machine Learning Blog AWS Machine Learning Blog AWS Machine Learning Blog AWS Machine Learning Blog AWS What's New AWS Machine Learning Blog AWS Machine Learning Blog

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…