Industry story
AWS Partner Central MCP Server adds OAuth via AWS Sign-In
agent-framework mcp orchestration security
AWS quietly closed a real friction point for partners building AI agents on top of Partner Central. Before this update, connecting tools like Amazon Q or Kiro to co-sell workflows, funding applications, and Marketplace seller setup required standing up a separate MCP proxy with SigV4 credentials. OAuth via AWS Sign-In collapses that into the IAM policies and CloudTrail audit trails partners already run. Less infrastructure to maintain, and agent access that's actually auditable.
Full analysis
AWS has added OAuth authentication support to its Partner Central agents MCP Server (Model Context Protocol is an open standard for connecting AI agents to external tools and data), allowing AWS partners to authorize agent access using their existing AWS identities and sign-in methods. Previously, partners had to set up a separate MCP proxy with SigV4 credentials or log in through the AWS Management Console; OAuth eliminates that extra infrastructure step.
With this change, partners can use tools like Amazon Q (Quick) and Kiro to access Partner Central agents for co-sell engagements, AWS funding applications, and AWS Marketplace seller setup, all governed by existing IAM policies, token introspection/revocation APIs, dynamic client registration, and CloudTrail audit events. The feature is currently available in the US East (N. Virginia) Region.
Comments