From 75be502490a260149e6beb16fa0cf7ab05da188a Mon Sep 17 00:00:00 2001 From: Moritz Sanft <58110325+msanft@users.noreply.github.com> Date: Fri, 5 Apr 2024 15:19:12 +0200 Subject: [PATCH] Update docs/docs/overview/clouds.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Daniel Weiße <66256922+daniel-weisse@users.noreply.github.com> --- docs/docs/overview/clouds.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/overview/clouds.md b/docs/docs/overview/clouds.md index 4f6b60187..a7b1361e8 100644 --- a/docs/docs/overview/clouds.md +++ b/docs/docs/overview/clouds.md @@ -5,7 +5,7 @@ What works on which cloud? Currently, Confidential VMs (CVMs) are available in v For Constellation, the ideal environment provides the following: 1. Ability to run arbitrary software and images inside CVMs -2. CVMs based on AMD SEV-SNP (available in EPYC CPUs since the Milan generation) or Intel TDX (available in Xeon CPUs since the Sapphire Rapid generation) +2. CVMs based on AMD SEV-SNP (available in EPYC CPUs since the Milan generation) or Intel TDX (available in Xeon CPUs since the Sapphire Rapids generation) 3. Ability for CVM guests to obtain raw hardware attestation statements 4. Reviewable, open-source firmware inside CVMs 5. Capability of the firmware to attest the integrity of the code it passes control to, e.g., with an embedded virtual TPM (vTPM)