Did You Know Signing In to AWS Partner Central's MCP Server Just Got Way Easier?

Hi everyone, it's Shiichan! Today I've got a nice little authentication update for AWS Partners, let's take a look!

AWS What's New aws.amazon.com

What was announced?

This comes from AWS What's New. The AWS Partner Central agents MCP Server now supports OAuth through AWS Sign-In. Partners can access Partner Central agents from tools they already use, like Amazon Quick and Kiro, using their existing AWS identities.

The story so far

Previously, accessing Partner Central agents from your existing tools meant setting up and maintaining your own MCP proxy with SigV4 credentials, or signing in to AWS Partner Central through the AWS Management Console with IAM credentials. Either way, partners had to shoulder extra authentication setup and upkeep.

What changes

With OAuth support, partners can authorize tools to access Partner Central agents using their existing AWS identities, sign-in methods, IAM permissions, and governance controls, without installing or maintaining additional authentication software.

This applies to workflows like co-sell engagements, AWS funding applications, and AWS Marketplace seller setup, all accessible directly from tools you already use, via OAuth.

Administrators can still govern access with IAM policies, global condition keys, token introspection and revocation APIs, dynamic client registration, and CloudTrail audit events.

Dive Deep

This OAuth support is available through the AWS Partner Central agents MCP Server, in the US East (N. Virginia) Region.

Wrap-up

• AWS Partner Central agents MCP Server now supports OAuth via AWS Sign-In
• Partners can use existing AWS identities from tools like Amazon Quick and Kiro
• No more need to build and maintain your own SigV4 proxy
• Admins retain control via IAM policies, token introspection/revocation APIs, CloudTrail, and more
• Available in US East (N. Virginia)

A quiet but solid win for any AWS Partner who's been running their own auth proxy!