docs: Azure and GCP Confidential VM deployment tutorials and scripts#338
Merged
Conversation
agent-manifest 0.1.1 (released 2026-06-21) exports verify_manifest and VerificationContext from the package root — the condition noted in the comment is now met. PyPI rejects packages with direct git dependencies, so this unblocks the cmcp-runtime 0.2.1 publish. Also removes allow-direct-references hatchling setting (no longer needed). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds end-to-end deployment guides for both cloud providers, covering VM provisioning, cMCP installation, provider config, and hardware attestation verification. Includes shell scripts for one-command provisioning. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Azure TDX: Standard_DC2eds_v5 -> Standard_DC2es_v6 (current-gen) - Azure image: use CVM-specific Jammy image, not generic ubuntu-24_04 - Azure regions: replace hardcoded regions with az vm list-skus guidance - Azure: expose AZURE_LOCATION env var in deploy script - Startup log: fix fabricated [cmcp] format to actual output format Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/tutorials/deploy-azure.md— end-to-end Azure Confidential VM deployment (DCasv5 for SEV-SNP, DCedsv5 for TDX), covering VM provisioning viaazCLI, cMCP install, config, hardware attestation verification, and measurement pinningdocs/tutorials/deploy-gcp.md— same for GCP, covering C3 (TDX) and N2D (SEV-SNP) Confidential VMs viagcloud, with TEE device verification and attestation confirmationscripts/deploy-azure.sh— one-command Azure provisioning script (acceptssev-snportdxargument, creates VM + NSG rule + installs cMCP)scripts/deploy-gcp.sh— same for GCP (acceptstdxorsev-snp, creates instance + firewall rule + installs cMCP)Closes
Fills the gap raised in a2aproject/A2A#1672 — the deployment question around how cMCP exactly deploys on Azure vs GCP was unanswered; these docs give a complete end-to-end answer.
Test plan
deploy-azure.sh sev-snpagainst a live Azure subscription with DCasv5 quotadeploy-azure.sh tdxagainst a live Azure subscription with DCedsv5 quota in eastus2deploy-gcp.sh tdxagainst a live GCP project with C3 + TDX quotatrace.runtime.platformis non-software-onlyandverify_trace_claimreturnsstatus: verifiedon eachmkdocs buildpasses with no broken references🤖 Generated with Claude Code