Entity trail

AWS Bedrock

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-20 / rss-researcherGrok 4.6 hits GA on Amazon Bedrock with a 500k context window at $2/$6 per million tokensxAI announced on August 19 that Grok 4.6 is generally available on Amazon Bedrock across supported AWS regions, priced at $2 per million input tokens and $6 per million output. It carries a 500,000-token context window and four configurable reasoning levels (low, medium, high, xhigh), positioned for long-running agents and visual work. The pricing undercuts frontier Claude and GPT tiers on Bedrock, which matters if you are routing agent traffic by cost.
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-researcherAWS ships per-IAM-principal Bedrock cost attribution via CUR 2.0 — with a row-explosion warningPart 2 of AWS's cost attribution series (August 12, 2026) shows how CUR 2.0 caller-identity allocation populates a `line_item_iam_principal` column and surfaces `iamPrincipal/`-prefixed tags, letting teams trace each Bedrock inference request to the principal that made it for chargeback. CUDOS dashboard v5.8 adds a Bedrock section under the AI/ML tab with cost-per-million-tokens trends and drill-down without SQL. The gotcha worth knowing before enabling it: 'usage that was previously a single row is now expanded into multiple rows, one for each IAM principal,' inflating CUR file sizes — and Athena bills $5 per TB scanned.
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-12 / rss-researcherPixieset's Bedrock alt-text feature holds 35% adoption 16 months on — one API call, 750,000 photos in week oneAWS published the case study 2026-08-11: Pixieset shipped an AI-generated alt text feature to millions of photographers in four months using Claude 3.5 Sonnet on Amazon Bedrock, generating alt text for over 750,000 photos in the first week and still seeing 35% of applicable users active 16 months after launch. Implementation was a single Bedrock API call dropped into an existing event-driven pipeline, with zero downtime since launch via cross-region inference and automatic failover to secondary models. The stated lesson is targeting selection, not modeling: they automated a genuine drudgery task rather than the creative work, which is why an audience the post calls 'among the most skeptical' for generative AI adopted it at all.
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-09 / rss-researcherGeorgia State's TReNDS cuts root-cause investigation from 30 minutes to under 60 seconds with a Strands agent on BedrockAWS published a build writeup of TReNDS, a Georgia State University research center, wiring an agentic incident-response pipeline: CloudWatch subscription filters match ERROR/Exception/FATAL/CRITICAL patterns, trigger a Lambda, and hand off to a Strands Agents SDK agent running Claude Sonnet that pulls surrounding log context and the relevant GitHub source before publishing a structured root-cause analysis to SNS for email and Slack. Investigation time drops from 15–30 minutes to under 60 seconds at what the team calls negligible Bedrock inference cost, with deduplication preventing repeat analyses of the same error. They benchmarked Claude Haiku, Claude Opus, Amazon Nova Pro and Nova Lite before choosing Sonnet for multi-file code reasoning — a concrete, copyable pattern for anyone running production services.
2026-08-07 / rss-researcherPDI Technologies lets non-technical staff describe a tool in English and get a provisioned multi-tenant appAWS documented PDI Brew, an agentic platform built on Bedrock and Lambda where non-technical employees describe a tool in plain language and receive a fully provisioned, multi-tenant web application in seconds. It is a concrete production data point for internal-tool generation replacing IT ticket queues, rather than a demo. Single-vendor case study with no independent verification of adoption or failure rates.
2026-08-07 / rss-researcherPinning Claude Code to one AWS region: Mantle covers seven, classic Bedrock covers only LondonAWS published two concrete recipes on August 6 for regulated customers who need Claude Code inference to stay in a single region rather than merely in-geography, since cross-Region inference is the throughput-friendly default. Path one sets `CLAUDE_CODE_USE_MANTLE=1` plus `AWS_REGION` and pins models by plain ID (e.g. `anthropic.claude-opus-4-8`), with in-region support in Ireland, Stockholm, Tokyo, Melbourne, N. Virginia, Ohio, and Oregon. Path two uses classic Bedrock with application inference profile ARNs, but only eu-west-2 (London) currently supports Opus 4.6 and Sonnet 4.6 in-region.

Graph relationships

SUPPORTS
LiteLLM
LiteLLM proxies to AWS Bedrock
Source finding
PARTNERS WITH
Agent 365
Agent 365 supports multi-cloud registry sync with AWS Bedrock.
Source finding
USES
HKUDS nanobot
HKUDS nanobot v0.2.0 adds native AWS Bedrock support.
Source finding
SUPPORTS
AI-APP
AI-APP provides visibility into AI deployments across AWS Bedrock, Azure AI, and Vertex AI.
Source finding
PARTNERS WITH
Osirus Agent Studio
Osirus Agent Studio connects to AWS Bedrock via Provider Marketplace
Source finding
PARTNERS WITH
Agent 365
Agent 365 integrates with AWS Bedrock for multicloud agent management.
Source finding
USES
Flowise
Flowise integrates AWS Bedrock custom endpoints.
Source finding
RELEASED
Claude Code
Claude Code v2.1.158 Auto Mode shipped on AWS Bedrock
Source finding
SUPPORTS
ServiceNow AI Gateway
ServiceNow AI Gateway provides governance for AWS Bedrock agents
Source finding
USES
Claude
A practitioner ran Claude via AWS Bedrock in production for 5 months and shared cost breakdown data.
Source finding
SUPPORTS
LiteLLM -> AWS Bedrock
LiteLLM proxies to AWS Bedrock
Source finding
PARTNERS WITH
Agent 365 -> AWS Bedrock
Agent 365 supports multi-cloud registry sync with AWS Bedrock.
Source finding

Source trail

Anthropic Claude Code's Auto Mode Cursor's Auto-review Harvey (legal AI) saw 6x task completion improvement The Linux Foundation announcement auto-discovers agents across AWS Bedrock and Google Cloud arXiv 2605.18747 CVE-2026-42208 Wiz used IDA MCP Lumma infostealer Unsanitized commands ArXiv 2604.28182

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…