OAuth support arrives for the AWS MCP Server

The addition of OAuth to the AWS MCP Server closes a practical gap for teams wiring AI agents into AWS: previously, connecting an agent through the Model Context Protocol often meant bolting on separate authentication machinery. Now agents authenticate via AWS Sign-In using standard OAuth flows, and every call is governed by the organization's existing IAM permissions, identities, and controls — including IAM federation and IAM Identity Center.

Mechanically, this means an agent inherits the same least-privilege posture as any other AWS principal, rather than operating through a bespoke credential path that security teams have to reason about separately. For enterprises, that governance continuity is the selling point: agentic access becomes auditable and policy-controlled by default.

The timing is pointed. It shipped the same week Darktrace disclosed a hijacked Bedrock-connected AI gateway, underscoring exactly why identity discipline for agents matters. It is one of a cluster of AWS agent-infrastructure releases (Loom, Continuum, DMS Schema Conversion agents, expanded Config rules) that collectively signal AWS is competing on making agents governable at enterprise scale, not just capable — a differentiator against OpenAI and Anthropic's more consumer-facing agent launches.