AWS Partner Central agents MCP Server now supports OAuth with AWS Sign-In

AWS has introduced OAuth support for accessing Partner Central agents through existing tools such as Amazon Quick and Kiro, enabling partners to authorize access using their existing AWS identities and IAM permissions. This change removes the previous requirement to set up an MCP proxy with SigV4 credentials or manually sign in via the AWS Management Console. Partners can now streamline workflows for co-sell engagements, AWS funding applications, and AWS Marketplace seller setup without installing additional software.

The new OAuth integration allows partners to use AWS Sign-In to grant tools like Amazon Quick and Kiro access to Partner Central agents directly, simplifying authentication processes. Previously, partners had to configure proxies or rely on manual console logins, which added complexity to their workflows. The update aligns with AWS’s goal of reducing operational overhead for partners while maintaining security and governance standards.

Administrators retain control over access through IAM policies, global condition keys, token introspection, revocation APIs, dynamic client registration, and CloudTrail audit events. These governance features ensure that partners can manage permissions and monitor activity without compromising security. The changes apply to the AWS Partner Central agents MCP Server, which is currently available in the US East (N. Virginia) Region.

AWS partners can now leverage OAuth to integrate Partner Central agents into their existing toolchains more efficiently. The update supports broader use cases, including co-sell engagements and funding applications, while maintaining compliance with AWS’s security and governance frameworks. For further details, AWS provides documentation on getting started with the Partner Central agents MCP Server and Sign-In with OAuth 2.0.