The architecture connects Amazon Bedrock AgentCore to a Snowflake-managed server via the Model Context Protocol to surface advanced Cortex capabilities. Bedrock's Gateway unifies these tools, while AgentCore Identity automatically oversees token refreshes, user-to-token binding, and the token vault. Three tested OAuth configurations accommodate various enterprise requirements, ranging from direct Snowflake authentication to integrations with external identity providers like Okta and Microsoft Entra ID. Additionally, organizations can deploy an on-behalf-of token exchange grant to maintain per-user identities during unattended automated workloads without prompting for consent.
Key points
Enterprises can select from three distinct OAuth patterns depending on whether they need…: Enterprises can select from three distinct OAuth patterns depending on whether they need direct authentication, corporate single sign-on, or machine-to-machine access.
Two-legged OAuth enables automated machine-to-machine workloads by relying on a shared se…: Two-legged OAuth enables automated machine-to-machine workloads by relying on a shared service user without interactive consent.
Patterns utilizing external identity providers follow standardized flows that can readily…: Patterns utilizing external identity providers follow standardized flows that can readily extend to other protected tool servers.
Sources checked by our analysis pipeline: 1
Artificial Intelligence
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). Amazon Bedrock AgentCore Identity also supports an on-behalf-of (OBO) grant (TOKEN_EXCHANGE) that delivers per-user identity for unattended workloads without…
The substantial equity positions secured through prior multibillion-dollar investments solidify deep technical alliances between the artificial intelligence startup and the tech sector's largest cloud infrastructure operators. These non-voting share structures enable major cloud giants to capture financial upside and long-term compute contracts without assuming direct voting governance. Meanwhile, a broader consortium of semiconductor and software powerhouses is pouring tens of billions into private placements tie…
The company's equity value surged after it introduced a specialized integration designed specifically for sales use cases. Investors responded favorably to the commercial deployment connected to the artificial intelligence platform. This rapid positive market reaction highlights strong immediate demand for enterprise generative tools.
The audio generation platform is expanding its creative capabilities into motion by enabling users to assemble longer video productions from short segments. This integration relies on third-party generative technology provided by MiniMax. However, accessing the media creation tools requires an additional financial commitment beyond standard usage.