Tag: patterns
All the articles with the tag "patterns".
-
An Agent's Credentials Cross Clouds. Its Off Switch Doesn't.
Workload identity federation lets one agent authenticate to AWS, Azure, and Google Cloud with no stored secrets, but its owner, approvals, permissions, and off switch stay split across three systems that do not talk to each other.
-
AgentCore and Foundry Wall Off the Session. Google Walls Off the Code.
Amazon Bedrock AgentCore, Microsoft Foundry Agent Service, and Google's Agent Platform draw their default security boundary around different things, ship the managed agent loop at different stages, and enforce policy at different choke points.
-
Every Cloud Sells the Same AI Stack. Each One Anchors It Somewhere Else.
A November 2026 map of AI, data, and model services across AWS, Azure, and Google Cloud, and an eight-question trace of one agent that shows where each stack is anchored.
-
Three Cloud Marketplaces, Three Commit Rules, Three Front Doors
AWS Marketplace, Microsoft Marketplace, and Google Cloud Marketplace all sell third-party AI agents and data tools against your cloud spending commitment, but they publish different rules for how much counts, and each delivers the bought agent into a different home system.
-
Every Cloud Now Sells Claude, GPT, and Grok. Who Runs Them Is Where They Differ.
Claude, OpenAI's GPT models, and Grok are on AWS, Azure, and Google Cloud, and Gemini is the one single-cloud family, so the choice comes down to who runs inference (the cloud, a partner, Anthropic, or you) and where your prompts go.
-
A shared service account cannot tell one rep's pipeline from another's
A personal agent that reaches the CRM through one shared account shows a rep every region's pipeline and leaves no record of whose question it was. Per-person token exchange fixes both, and shows a gap in agent identity.
-
Structured Outputs on Amazon Bedrock: Make the Model's Response a Contract
Updated:Structured outputs constrain a model's response to a JSON schema you supply. What they are, why they matter, where they apply, which Claude 5 models support them, what they cost, and how to call them through Amazon Bedrock, with the response shown with and without a schema.
-
One Coding Agent, Three Bedrock APIs: Wiring OpenCode to Claude, GPT, Grok, and Kimi
A tested OpenCode configuration for running Claude, OpenAI GPT, xAI Grok, and Moonshot Kimi through their native Amazon Bedrock Runtime APIs.