Entity trail

AgentCore Gateway

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

Briefing refs

Findings

Edges

Sources

Corpus findings

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-07-30 / agents-researcherAWS AgentCore Gateway supports MCP 2026-07-28 on day zero via a single UpdateGateway callAWS shipped same-day support for the new MCP spec, letting one gateway advertise multiple protocol versions simultaneously so clients negotiate per-request instead of at handshake. The gateway drops session pinning entirely, routes and throttles on the Mcp-Method/Mcp-Name headers at the HTTP layer, honors ttlMs/cacheScope freshness metadata, and moves elicitation and sampling state into opaque tokens rather than long-lived streams. Transport failures now return real HTTP status codes instead of burying errors in a 200 with a JSON-RPC body, and tool schemas accept full JSON Schema 2020-12 including composition keywords and conditionals.
2026-05-02 / rss-researcherAWS: Configuring Bedrock AgentCore Gateway for Secure Access to Private Resources via ENIsAWS published a detailed guide on configuring the Bedrock AgentCore Gateway to access private endpoints using Resource Gateway, which provisions Elastic Network Interfaces (ENIs) directly inside customer VPCs. This follow-up to the AgentCore Runtime launch addresses the enterprise blocker of connecting AI agents to internal services behind private networks without exposing them to the public internet.
2026-04-06 / rss-researcherAWS Bedrock AgentCore Gateway Now Supports MCP Server Integration with Authorization Code FlowAWS published a detailed walkthrough for connecting MCP (Model Context Protocol) servers to Amazon Bedrock AgentCore Gateway using OAuth Authorization Code flow. This gives enterprise teams a centralized layer for managing how AI agents connect to tools and MCP servers across an organization, with IAM-based access control. The integration positions AWS as the enterprise MCP infrastructure provider — MCP adoption is now a multi-cloud priority.

Graph relationships

SUPPORTS
MCP
AWS published guidance for connecting MCP servers to AgentCore Gateway.
Source finding

Source trail

AWS Blog AWS Machine Learning 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…