Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

AWS details OAuth patterns for Snowflake agents via AgentCore

AI summary

The AWS Machine Learning Blog details three OAuth configurations tested end-to-end for connecting AI agents to Snowflake’s managed MCP server through Amazon Bedrock AgentCore Gateway: Snowflake OAuth, three-legged OAuth with an external identity provider, and two-legged OAuth using a shared service user. AWS says AgentCore Identity manages credential brokering, token storage, refresh, and user-to-token binding, while also claiming support for an on-behalf-of TOKEN_EXCHANGE grant for unattended workloads. The gateway exposes Snowflake Cortex Search and Cortex Analyst through a unified MCP tool catalog.

In-depth insight

The guide gives developers a concrete comparison of grant types, identity mapping, SSO, audit behavior, and machine-to-machine access for authenticating AI agents that use Snowflake tools.

Enterprises today need a clear way to extend their authentication and authorization controls into the agentic layer, often requiring either broad service account permissions or custom-built auth integrations that add operational overhead. When an AI agent running on Amazon Bedrock AgentCore (a platform to build, connect, and optimize agents at scale, with any framework or model) needs to call the Snowflake-managed MCP server (which exposes Snowflake Cortex Agents as one of its tool types) through the Model Context Protocol (MCP), the first question enterprises must answer is: how does the agent authenticate? In this post, we walk through three Open Authorization (OAuth) configurations we tested on Amazon Bedrock AgentCore Identity, a capability of Amazon Bedrock AgentCore: Snowflake OAuth (per-user, no external Identity Provider, or IdP), three-legged OAuth with a third-party Identity Provider (corporate single sign-on, or SSO), and two-legged OAuth with a third-party Identity Provider (shared service user). Amazon Bedrock AgentCore Identity also supports an on-behalf-of (OBO) grant (TOKEN_EXCHANGE) that delivers per-user identity for unattended workloads without a consent prompt. We focus on the three configurations we tested end-to-end, flagging where OBO fits as we go. By the end, you will be able to identify which pattern suits your enterprise scenario.

#Amazon Bedrock AgentCore Gateway#Amazon Bedrock AgentCore Identity#Snowflake Cortex AI#Snowflake Cortex Search#Snowflake Cortex Analyst#Snowflake-managed MCP server#Okta#Microsoft Entra ID

Original · 22 min readRead the original
Group chat

No comments yet. Start the conversation.