Amazon Web Services → Microsoft Azure
Azure equivalent of AMD SEV-SNP on Amazon EC2
AWS Nitro Enclaves and AMD SEV-SNP on EC2 map to Azure confidential computing (confidential VMs and SGX application enclaves).
About AMD SEV-SNP on Amazon EC2
| Provider | Amazon Web Services |
|---|---|
| Status | Generally available |
| What it is | Memory encryption and attestation with AMD SEV-SNP on supported AMD-based instance types (M6a, C6a, and R6a at the time of verification), for shared tenancy or Dedicated Hosts. |
| Documentation | docs.aws.amazon.com |
| Pricing | Official pricing page |
Azure mappings (1)
| Capability | Azure equivalent | Match |
|---|---|---|
| Confidential computing | Azure confidential computing (confidential VMs & enclaves) | Partial match |
VM security & operations(1)
Confidential computing Partial match
AWS Nitro Enclaves and AMD SEV-SNP on EC2 map to Azure confidential computing (confidential VMs and SGX application enclaves). Azure has a broader confidential VM lineup; AWS relies more on its Nitro System isolation plus enclaves.
- Whole-VM. Azure confidential VMs support AMD SEV-SNP (DCasv5/v6, ECasv5/v6) and Intel TDX (DCesv6, ECesv6), plus H100 confidential GPUs, with confidential OS-disk encryption and Azure Attestation. EC2 supports SEV-SNP on a smaller set of AMD types (M6a, C6a, R6a at verification).
- Enclaves. Nitro Enclaves split vCPUs and memory off a parent instance into a hardened VM with no network, storage, or shell, and integrate attestation with AWS KMS key policies. Azure's application-enclave option is Intel SGX.
- Baseline. AWS states that the Nitro System prevents operator access and that memory is always encrypted on recent processors. Azure positions confidential VMs and Trusted Launch as separate tiers.