AWS released a sample that runs each Claude Code task in a separate Bedrock AgentCore runtime session inside the customer's AWS account and returns a GitHub pull request for review. The design uses Bedrock model calls, short-lived GitHub tokens, a prompt guardrail and optional private VPC networking.
Why it matters: The reference makes remote coding-agent isolation and human merge review concrete without requiring a laptop to stay online. It also concentrates repository credentials, network policy and generated code inside a cloud runtime that must be configured and…
AWS published a two-part AgentCore pattern using Okta Cross App Access to bind an agent to a signed-in user, exchange short-lived grants and enforce tool policy through AgentCore Gateway and Cedar. In AWS's test setup, removing a user stopped new grants in about one second while issued tokens lasted up to five minutes.
Why it matters: The pattern replaces shared agent service accounts with explicit user-and-agent identity and a measurable revocation window. It also shows that different target applications can have different consent and revocation behavior, so one identity design cannot be…
AWS made Web Answer generally available as a managed AgentCore Gateway tool. One MCP call returns a synthesized answer with source URLs from an Amazon-operated web index, supports domain and date filters, publishes CloudWatch metrics and costs $10 per 1,000 calls.
Why it matters: Teams can replace a custom search, retrieval, synthesis and citation pipeline with one governed service call, but they also surrender ranking, retrieval and synthesis control to a managed component whose citations still require claim-level review.
Amazon Bedrock AgentCore Runtime added Session endpoints: per-session authenticated HTTPS URLs that reach explicitly allowed ports inside a runtime microVM and preserve HTTP methods, paths and bodies while supporting HTTP/2, gRPC, server-sent events and WebSockets. AWS published a working coding-agent sample that streams a Vite preview without a separate deployment.
Why it matters: Developers can inspect the application or service an agent is running inside its isolated session instead of copying it into a second hosting environment first. The feature also creates a new externally reachable runtime boundary that needs explicit port,…
AWS released AgentCore CLI 1.0 with a rebuilt command structure for harnesses, runtimes, memory, identity, gateways and payments, plus direct resource invocation, interactive shells, JSON output and a migration command for existing projects.
Why it matters: The release makes operational AgentCore resources addressable from one stable interface instead of project-only workflows. That improves automation and inspection, but it also gives terminal sessions broader access to agent identities, runtimes and…
AWS made AgentCore payments generally available for agents to discover and pay for APIs, MCP services, and content through Coinbase and Stripe Privy wallets, x402 and MPP support, infrastructure limits, and AgentCore observability.
Why it matters: Agents can now create real financial effects through a managed enterprise path. Wallet custody, merchant identity, cumulative limits, approval rules, pricing evidence, refunds, reconciliation, disputes, and incident shutdown become runtime requirements.
AWS launched Agent Registry in general availability under the agent-registry namespace on 6 August. New customers must use it immediately; existing preview customers can use both namespaces until bedrock-agentcore shuts down on 17 September.
Why it matters: The migration changes endpoints, IAM, SDK and CLI clients, ARNs, API schemas, observability, and stored registry data rather than only renaming a service.
Amazon Bedrock AgentCore added temporal policies powered by the open Dogwood language plus identity-scoped gateway limits for requests, tokens, and connections, moving multi-step authorization and cost ceilings outside agent code.
Why it matters: A tool call can be valid alone but unsafe after earlier actions. Session-aware policy lets operators require approvals, enforce sequence, cap cumulative value, and observe decisions before switching enforcement on.
AWS expanded Amazon Bedrock AgentCore Web Search to US East Ohio, US West Oregon, Asia Pacific Sydney and AWS GovCloud US-West, adding regional and government-workload options to the managed web-grounding tool.
Why it matters: The material change is deployment locality and GovCloud access, not a new search-quality claim. Teams can place grounding closer to workloads or inside a government Region, but still need evidence that retrieval, citations and data handling meet their actual…
AWS and Motorway released code for testing tool use, reasoning and output quality before deployment, then sampling production traces. The reference gates releases on repeated success and includes a no-AWS quickstart for mock agents.
Why it matters: Agent reliability needs deterministic tool checks, calibrated judges, repeated trials and production feedback connected to one release gate.
AWS organized production agent operations around governance and security, build and operations, evaluation and observability, with versioned artifacts, multi-account controls and release gates.
Why it matters: Agent operations span identity, tools, memory, traces, evaluation, cost and incident response; treating them as ordinary prompt deployments leaves critical gaps.
AWS published a workflow for versioning evaluation examples, adding reviewed production failures and rerunning stable datasets as Bedrock AgentCore agents change.
Why it matters: An agent test suite should accumulate real failures and preserve versioned expectations instead of being rebuilt from a few hand-picked demo prompts.
AWS Agent Registry provides a private catalog for agents, tools, skills, MCP servers and custom resources. It supports URL-based metadata discovery, approval workflows, IAM or OAuth access, CloudTrail auditing, semantic and keyword search, and an MCP interface.
Why it matters: As agent estates grow, discovery and reuse need ownership, approval and audit metadata; a list of endpoints is not enough.
AWS published CloudFormation patterns for deploying Bedrock AgentCore runtimes and related resources as versioned infrastructure, including parameterized environments, rollback paths and automated scaling.
Why it matters: Treating agent infrastructure as code makes permissions, networking and runtime configuration reviewable and repeatable instead of leaving production behavior tied to console state.
AWS put AgentCore Policy and Evaluations into preview: Policy intercepts Gateway tool calls outside an agent's reasoning loop, while Evaluations scores real-world behavior with built-in or custom evaluators.
Why it matters: The combination addresses two production gaps: enforcing deterministic limits before tools execute and measuring agent quality continuously instead of relying only on predeployment benchmarks.
AWS launched Bedrock AgentCore in preview with managed runtime, memory, observability, identity, gateway, browser and code-interpreter services. The platform was designed to support agents built with different frameworks and models, including models outside Amazon Bedrock.
Why it matters: Agent deployment is shifting from prompt orchestration toward identity, state, isolation, observability and tool infrastructure as managed primitives.