# Amazon — Secure OAuth patterns for Snowflake Cortex AI through Amazon Bedrock AgentCore

- Company: Amazon (amazon.com)
- Announced: 2026-11-17T20:25:23+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/secure-oauth-patterns-for-snowflake-cortex-ai-through-amazon-bedrock-agentcore/
- Record: https://forck.live/items/37547-secure-oauth-patterns-for-snowflake-cortex-ai-through-amazon-bedrock-agentcore
- Subject: Bedrock / Nova

Amazon's guide walks through three OAuth configurations it tested end-to-end for connecting AI agents on Amazon Bedrock AgentCore to the Snowflake-managed MCP server. The first is Snowflake OAuth, where Snowflake acts as its own authorization server and each user authenticates directly through the Authorization Code grant with no external identity provider. The second is three-legged OAuth through a third-party IdP, where users sign in with corporate SSO and Snowflake trusts IdP-issued JWTs via its External OAuth security integration. The third is two-legged OAuth, where a shared service user authenticates through the client_credentials grant with no user interaction or consent, which the post says suits machine-to-machine workloads. AgentCore Identity acts as the credential broker, owning the token vault, refresh and user-to-token binding, and fetching, caching and refreshing tokens automatically. The patterns were tested with Okta and Microsoft Entra ID, and the post notes that the external-IdP patterns follow standard OAuth flows and can extend to other OAuth-protected MCP servers if token claims, scopes and audience settings are validated.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/secure-oauth-patterns-for-snowflake-cortex-ai-through-amazon-bedrock-agentcore/:

> 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).

---

Record: https://forck.live/items/37547-secure-oauth-patterns-for-snowflake-cortex-ai-through-amazon-bedrock-agentcore
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
