> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/compute-services/compute-engine/confidential-computing-vm/overview.md).

# Overview

IONOS CLOUD Confidential VM: AMD SEV-SNP hardware-encrypted VMs for regulated workloads.

Confidential VM follows a [<mark style="color:blue;">shared responsibility model</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/overview/security-and-trust-model.md#shared-responsibility-model) where <code class="expression">space.vars.ionos\_cloud</code> secures the underlying platform infrastructure, while you maintain exclusive control over everything within the TEE. For information on what falls outside the responsibility of <code class="expression">space.vars.ionos\_cloud</code>, see [<mark style="color:blue;">Security boundaries</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/overview/limitations.md#security-boundaries-end-users-responsibility).

## How a Confidential VM differs from a standard VM

| **Feature**            | **Standard VM**                  | **Confidential VM**                                                                                    |
| ---------------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Data in memory**     | Unencrypted; hypervisor-readable | Hardware-encrypted; hardware-isolated and protected. Memory contents are cryptographically unreadable. |
| **Trust model**        | Policy-based ("we won't look")   | Hardware-enforced ("we can't look")                                                                    |
| **Security guarantee** | Contractual commitment           | Cryptographic proof                                                                                    |
| **Operator access**    | Administrative path exists       | Physically impossible                                                                                  |

{% hint style="info" %}
**Important:** Confidential VMs, which run in an <code class="expression">space.vars.ionos\_cloud</code> EU data center, in the **Frankfurt-East** `de/fra/2` region, are not subject to the [<mark style="color:blue;">US CLOUD Act</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#us-clarifying-lawful-overseas-use-of-data-cloud-act). This provides a hardware-enforced sovereignty guarantee for regulated workloads.
{% endhint %}

## How IONOS CLOUD isolates your workload

The following illustration shows a Confidential VM isolated within AMD SEV-SNP Trusted Execution Environment, with the host OS, hypervisor, and cloud admin outside the trust boundary:

* **Host-side actors** (Host OS / hypervisor, Cloud / infra admin) operate outside the trust boundary; they see only ciphertext and cannot inject, inspect, or modify the VM state.
* **External attack vectors** (Memory scraper, diagnostic tools) are isolated at the hardware boundary without access path into the TEE or its workloads.
* **IONOS CLOUD** is equally excluded; the AMD CPU generates and holds encryption keys internally. For more information, see [<mark style="color:blue;">Security and trust model</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/overview/security-and-trust-model.md).

<figure><picture><source srcset="/files/78BHtMxM47W6AU23nxZd" media="(prefers-color-scheme: dark)"><img src="https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-15442e72caf92a3940f5b50b9eab06722c0d2279%2Fcc-fundamentals-light.png?alt=media" alt="Diagram showing a Confidential VM isolated inside an AMD SEV-SNP Trusted Execution Environment, with the host OS, hypervisor, and cloud admin outside the trust boundary"></picture><figcaption><p>Confidential VM on an IONOS CLOUD TEE</p></figcaption></figure>

## How do I set up a Confidential VM?

The following five steps describe the complete lifecycle from image preparation to an operating a Confidential VM.

1. **Prepare your image:** Build a custom Linux image that includes the `LAUNCH_ARTIFACTS` partition. This partition must contain a `launch-config.json`, and the expected measurement. The `initrd` boots before the OS. If you are using attestation, embed the attestation client within the `initrd`. For more information, see [<mark style="color:blue;">Prepare a confidential image</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/api-how-tos/prepare-confidential-vm-image.md).
2. **Deploy your attestation service:** *(Optional)*. Deploy and configure your attestation service in a location reachable from the Confidential VM's launch network. Register the measurement policy the service will use to verify [<mark style="color:blue;">attestation report</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#attestation-report). For the <code class="expression">space.vars.ionos\_cloud</code> open-source reference implementation, see [<mark style="color:blue;">SNPGuard</mark>](https://github.com/ionos-cloud/snp-guard). For more information, see [<mark style="color:blue;">Attest a Confidential VM</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/api-how-tos/attest-confidential-vm.md) and [<mark style="color:blue;">What is a measurement and how is it computed?</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/overview/security-and-trust-model.md#what-is-a-measurement-and-how-is-it-computed).
3. **Create a Confidential VM:** Use the <code class="expression">space.vars.ionos\_cloud\_api</code> to create a Confidential VM at a Confidential VM-capable location. Specify the launch volume built from your image and the required vCPU and memory configuration. For more information, see [<mark style="color:blue;">Create a Confidential VM</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/api-how-tos/create-confidential-vm.md).
4. **Confidential VM starts:** The `initrd` runs before the OS. If you deployed an attestation service, the attestation client embedded in the `initrd` contacts it, verification runs, the [<mark style="color:blue;">Volume Master Key (VMK)</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#volume-master-key-vmk) is released, and the root filesystem is decrypted. Without attestation, the `initrd` is responsible for unlocking the root filesystem on its own. For more information, see [<mark style="color:blue;">The startup process</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/overview/security-and-trust-model.md#the-launch-process).
5. **Operate:** Monitor attestation events and handle planned maintenance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/compute-services/compute-engine/confidential-computing-vm/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.