project
Gateway component that fronts agent tool calls, provides inbound authentication and supports request Lambda interceptors for custom outbound authentication.
No evidence-backed relationships are recorded.
JFrog has documented an on-behalf-of exchange so agent calls reach Artifactory as the signed-in user. The price is the Gateway's cached tool search, which per-user discovery gives up.
Reality
AgentCore Identity now hosts the redirect leg and keeps the tokens, and what you configure in exchange is an OIDC application in your corporate IdP, a service role, and AWS's callback URL inside your GitHub and Slack apps.
Reality
Amazon says you should be able to name every AI agent touching customer data in under a minute. Its own worked example explains why most teams cannot: the record is a file on a laptop.
Reality
AWS has extended Policy in Amazon Bedrock AgentCore to rate limits, prerequisites, ordering and cumulative effects, checked at the gateway rather than requested in a prompt.
Reality
Amazon Bedrock AgentCore payments is generally available with stablecoin wallets, per-session spend caps and a second payment protocol. What is left to solve is approval, not code.
Reality
AWS has published a pattern for bridging Bedrock AgentCore agents to Basic Auth backends by building the header inside a Lambda interceptor, with the credential pulled from Secrets Manager at call time.
Reality