Entity trail

Bedrock AgentCore

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

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

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-14 / rss-researcherSolv Labs proves agent payments in under 4 seconds with hardware attestation inside AWS Nitro EnclavesThis August 12, 2026 AWS writeup details Solv Labs combining Bedrock AgentCore payments (launched May 2026 with Coinbase and Stripe) with its ORACLE policy engine and ICME's PreFlight verification layer, so every autonomous agent payment is authorized, risk-priced, and auditable before settlement. An integrity service signs execution records inside AWS Nitro Enclaves, with the attestation document binding signing keys to enclave image measurements (PCR0/PCR1/PCR2) so records cannot be rewritten after the fact. Measured overhead is the useful part: full transaction under 4 seconds end-to-end, governance under 1 second, proof verification under 1 second — over the x402 agent payment standard.
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-researcherAgentCore gateway rate limits publish real numbers: 80,000 TPM for restricted models, 20 RPM per Basic userAWS shipped per-user, per-target rate limiting on the Bedrock AgentCore gateway on August 6, covering MCP targets, inference targets, and HTTP passthrough with three metrics — requests (RPS/RPM, all targets), tokens (TPM, inference only), and connections (CPS, all targets). Limits scope by JWT claims (`$.context.jwt.sub`, `.role`, `.azp`) or IAM identities (`$.context.iam.principal`, `.sourceIdentity`), and by `targetName`, `toolName`, or `qualifiedModelId`. The CLI examples give usable defaults: 100 RPM/50 CPS for Basic tiers, 300 RPM/150 CPS for Advanced, 20 RPM per individual, and token caps of 80,000/40,000/20,000 TPM by tier.
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-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-08-06 / rss-researcherAWS engineers tunnel MCP from a cloud agent to a laptop through a Chrome extensionAn AWS post details a bridge letting a cloud-hosted Bedrock AgentCore agent call MCP servers running on a user's own machine, chaining four hops: SigV4-signed WebSocket from AgentCore to a browser extension, Chrome native messaging (32-bit little-endian length framing) from extension to a local bridge, then stdio JSON-RPC to the MCP server. Presigned URLs expire after 5 minutes and auto-renew every 2 seconds so expiry is invisible; AWS credentials never leave the machine. It's a notably hacky answer to a real problem — cloud agents can't see local files or tools — and the recommended hardening list (JWT handshakes, Ed25519 payload signing, filesystem allowlists) signals how much is left to the implementer.
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.

Graph relationships

PARTNERS WITH
Stripe
Bedrock AgentCore launched with Stripe payment integration.
Source finding
PARTNERS WITH
Coinbase
Bedrock AgentCore launched with Coinbase payment integration.
Source finding
USES
Model Context Protocol
AWS demonstrated deploying an MCP server against Bedrock AgentCore.
Source finding
USES
Solv Labs
Solv Labs combines Bedrock AgentCore payments with its policy engine.
Source finding
USES
Lambda
Bedrock AgentCore deploys Lambda functions.
Source finding
USES
AWS CDK
Bedrock AgentCore deployment uses AWS CDK.
Source finding
PARTNERS WITH
Slack
Bedrock AgentCore integrates with Slack via AWS guide.
Source finding
USES
Agent Factory
Agent Factory uses Amazon Bedrock AgentCore for high-complexity operations.
Source finding
USES
Solv Labs -> Bedrock AgentCore
Solv Labs combines Bedrock AgentCore payments with its policy engine.
Source finding
USES
Agent Factory -> Bedrock AgentCore
Agent Factory uses Amazon Bedrock AgentCore for high-complexity operations.
Source finding

Source trail

AWS's August 12 writeup AWS announced serverless fine-tuning for NVIDIA Nemotron 3 on SageMaker semantic layer for agentic AI using Stardog on Bedrock AgentCore four deployment patterns for Unsloth-quantized models The walkthrough two WAF patterns for AgentCore Runtime made the managed AgentCore harness generally available CIO TrueFoundry TechCrunch reports AWS published

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…