> 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/api-how-tos.md).

# API How-Tos

IONOS CLOUD Confidential VM how-to guides for provisioning, image preparation, and VM creation.

This topic contains step-by-step guides for provisioning and managing <code class="expression">space.vars.ionos\_cloud</code> Confidential VM resources.

{% hint style="info" %}
**Prerequisites:**

Confirm the following before starting:

* You have an active <code class="expression">space.vars.ionos\_cloud</code> account in the **Germany / Frankfurt am Main (de/fra/2)** data center.
* You have confirmed Confidential VM-capable location availability with <code class="expression">space.vars.ionos\_cloud</code>.
* You are experienced with Linux image building, `LUKS2` disk encryption, and API-based infrastructure management.
* *(Optional)* You have a deployment plan for your attestation service, including network reachability from the Confidential VM at startup.
  {% endhint %}

{% hint style="info" %}
**Note:**

* To prepare a Confidential VM image, create a Confidential VM, and attest a Confidential VM, use the [<mark style="color:blue;">IONOS Cloud API v6</mark>](https://docs.ionos.com/cloud/api-reference/cloud-api-v6/) or the `ionosctl` CLI.
* **Attestation is optional:** You do not need an attestation service to run a Confidential VM. If you want to verify your VM's integrity and use attestation-based key release, set up an attestation service before preparing your image. For more information about the <code class="expression">space.vars.ionos\_cloud</code> reference toolchain, refer to [<mark style="color:blue;">SNPGuard</mark>](https://github.com/ionos-cloud/snp-guard).
  {% endhint %}

## Pre-upload validation

Before uploading your image to <code class="expression">space.vars.ionos\_cloud</code>, verify that it meets all requirements. For a complete checklist covering partition structure, required files, firmware validation, and measurement registration, see [<mark style="color:blue;">Step 4: Verify your image</mark>](/cloud/compute-services/compute-engine/confidential-computing-vm/api-how-tos/prepare-confidential-vm-image.md#verify-your-image).

The upload handler validates these same requirements and rejects images that fail any checks.

## Quick links

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Prepare a Confidential VM Image</strong></mark></td><td>Build a bootable image with the required firmware, attestation client, and <code>LAUNCH_ARTIFACTS</code> partition.</td><td><a href="/cloud/compute-services/compute-engine/confidential-computing-vm/api-how-tos/prepare-confidential-vm-image.md">Prepare a Confidential VM Image</a></td></tr><tr><td><mark style="color:blue;"><strong>Create a Confidential VM</strong></mark></td><td>Create a startup volume and provision a Confidential VM with AMD SEV-SNP hardware encryption enabled.</td><td><a href="/cloud/compute-services/compute-engine/confidential-computing-vm/api-how-tos/create-confidential-vm.md">Create a Confidential VM</a></td></tr><tr><td><mark style="color:blue;"><strong>Attest a Confidential VM </strong></mark><em><mark style="color:blue;"><strong>(Optional)</strong></mark></em></td><td>Cryptographically verify that your Confidential VM runs an unmodified software stack on genuine AMD SEV-SNP hardware.</td><td><a href="/cloud/compute-services/compute-engine/confidential-computing-vm/api-how-tos/attest-confidential-vm.md">Attest a Confidential VM</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.