Deployment Platform Cheat-Sheet
Where to run Claude — Bedrock, Vertex, Foundry, or the direct API — by cloud standardization, residency, and feature freshness.
Pick the primary platform from the strictest binding constraint (usually residency/compliance), then add a secondary for feature freshness. Confirm current model/feature availability per platform before you commit.
| Cloud + obligation | Primary | Secondary | Why |
|---|---|---|---|
| AWS-standardized, regulated | Amazon Bedrock (in-region) | Direct API for non-regulated tasks | Keeps regulated data in-region under the account's compliance envelope |
| Google Cloud, regulated | Vertex AI (in-region) | Direct API for non-regulated tasks | Inherits GCP IAM / VPC-SC / residency controls |
| Azure, regulated | Microsoft Foundry | Direct API for non-regulated tasks | Uses existing Entra ID, networking, procurement |
| Any cloud, no obligation | Direct Anthropic API | Home cloud if lock-in matters later | Newest features first, lowest integration overhead |
| Multi-cloud, mixed | Managed platform for the strictest slice | Direct API for everything unregulated | Let the regulated slice dictate the primary |
Two traps
Managed cloud platforms lag the direct API on new features — don't assume same-day parity. And 'Claude Platform on AWS' is a different product from 'Amazon Bedrock' (different operator and freshness).
All CCAR-P references
Independent, unofficial study material from Claude Cert Prep. Not affiliated with Anthropic.