Amazon Bedrock AgentCore Adds Three OAuth Patterns for Secure Access to Snowflake Cortex AI
Amazon Bedrock AgentCore Identity now supports three OAuth authentication patterns for connecting AI agents to Snowflake Cortex AI via the MCP server: Snowflake OAuth, three-legged OAuth with an external IdP, and two-legged OAuth. This gives developers more flexibility to meet identity, compliance, and audit requirements when integrating AI agents with Snowflake.
What changed?
Amazon Bedrock AgentCore Identity has introduced support for three distinct OAuth authentication patterns when AI agents connect to Snowflake Cortex AI tools via the Snowflake-managed MCP server. The newly supported patterns are: (1) Snowflake OAuth (per-user, no external IdP), (2) three-legged OAuth with a third-party Identity Provider (such as Okta or Microsoft Entra ID) for corporate SSO, and (3) two-legged OAuth using a third-party IdP for service accounts. AgentCore Identity acts as a credential broker, handling token fetching, caching, and user-to-token binding. These patterns have been verified with Okta and Microsoft Entra ID, but custom OAuth2 integration is also supported.

Why does it matter to an everyday developer?
These OAuth patterns allow developers to match their organization's security and compliance needs when connecting AI agents to Snowflake Cortex AI. Developers can now achieve per-user attribution, enforce corporate SSO, or secure machine-to-machine workflows without user consent. The patterns support automatic token management and per-user auditability, minimizing operational overhead compared to custom authentication solutions. However, developers should be aware that when issuer-locking an MCP scope to an external IdP, only the configured pattern is allowed and fallback is not supported unless configured per schema or database.
What can the developer do now?
Developers can select and configure the OAuth pattern that best aligns with their use case. For per-user, direct authentication, configure Snowflake OAuth with AgentCore Identity as the credential provider. For corporate SSO, set up three-legged OAuth with an external IdP, updating Snowflake's security integration and the OAUTH_AUTHORIZATION_SERVER parameter as required. For service accounts and backend workflows, configure two-legged OAuth using client credentials. Ensure chosen token claims, scopes, and audience settings are validated for any external SaaS provider. Adjust schema or database-level settings if multiple authentication patterns are required within the same account.
