Product reference pages are available in English only.
Compute Services

Confidential VM

What Is It?

Confidential VM is a Compute Engine server type that encrypts your VM's memory at the CPU level, so even with full administrative access to the physical host, the hypervisor sees only ciphertext. It protects data in use, the state that encryption at rest and encryption in transit do not cover. IONOS CLOUD provides the physical host, hypervisor, and network, while you keep control of your operating system, applications, encryption keys, and attestation policies. With remote attestation, you can verify the exact state of the Trusted Execution Environment (TEE) before you release secrets to it.

Quick Facts

Aspect Details
Type Hardware-isolated virtual machine in a Trusted Execution Environment (TEE)
Hardware security technology AMD SEV-SNP (Secure Encrypted Virtualization with Secure Nested Paging)
Host CPU AMD EPYC Turin
Location Germany / Frankfurt am Main (de/fra/2)
Memory encryption AES, with a unique key per VM generated and held by the AMD Secure Processor
CPU resources Dedicated CPU cores, not shared with other virtual machines on the same host
Core and RAM configurations Same as Dedicated Core Server
Server type (API) ENTERPRISE
Image Custom Linux image built with a LAUNCH_ARTIFACTS partition (standard IONOS CLOUD images cannot be used)
Immutable after creation cores, ram, cpuFamily, availabilityZone
Attestation Optional; you deploy and operate your own attestation service (open-source reference: SNPGuard)
Measurement SHA-384 digest of OVMF firmware, Linux kernel, initial ramdisk, and kernel command-line parameters, computed at every VM start
Disk encryption Not by default; you implement LUKS2 inside the image
Network encryption Not by default; you implement TLS, WireGuard, or VPN inside the VM
Firmware provenance OVMF builds with SLSA Level 2 provenance, recorded in the Sigstore Rekor transparency log

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

Who Holds the Encryption Keys?

Key Held by Purpose
Memory encryption key AMD Secure Processor (hardware) Encrypts VM RAM in real time. The hardware generates it per VM; it never leaves the silicon.
Volume Master Key (VMK) The user Unlocks the LUKS-encrypted disk. Released into VM memory only after the VM's identity is verified.
Attestation signing key AMD (VCEK/VLEK, through AMD's Key Distribution Service) Signs the hardware attestation report so you can verify it.

LAUNCH_ARTIFACTS Partition Contents

Files Type Mandatory/Optional Purpose Location
launch-config.json Config (JSON) Mandatory Guest launch configuration. VM startup configuration read by the IONOS CLOUD platform. The file size cannot exceed 1 KB. -
firmware-code.fd Guest firmware (UEFI/OVMF) binary compiled with SNP_KERNEL_HASHES. Mandatory UEFI firmware that initialises the VM before the kernel loads. You can download them from IONOS CLOUD builds. The file size cannot exceed 50 MB. -
vmlinuz Compressed Linux kernel binary Mandatory The kernel launched by the firmware. The file size cannot exceed 50 MB. /boot directory
initrd.img Initial ramdisk archive Mandatory Boots before the OS. If you are using attestation, embed the attestation client inside the initrd. Without attestation, the initrd is still required but does not need an attestation agent. The file size cannot exceed 150 MB. /boot directory
kernel-params.txt Plain text, single line Mandatory Kernel command-line parameters passed to the kernel at startup. The file size cannot exceed 4 KB. /boot/grub/grub.cfg or /proc/cmdline (running kernel)
id-block.bin Binary Optional ID Block that binds the VM identity to a measurement. The file must be exactly 96 bytes. -
id-auth.bin Binary Optional Authentication information for the ID Block. The file must be exactly 4096 bytes. -

What You Can Do

Run Workloads with Hardware-Encrypted Memory

VM memory is encrypted by the CPU from the moment the VM starts, with or without attestation. AMD Secure Nested Paging detects and blocks hypervisor attempts to replay, remap, or modify VM memory pages. IONOS CLOUD can see that your VM exists, its allocated cores and RAM, and API actions, but not your memory contents, your encrypted disk contents, or your workload.

Verify the Platform with Remote Attestation

The AMD Secure Processor computes a measurement of the VM's software stack and records it in a hardware-signed attestation report. Your attestation service checks the report against your registered measurement policy and releases the Volume Master Key into the VM's encrypted memory only if all checks pass. The initrd then decrypts the LUKS2 root filesystem and the OS starts.

Note: Without an attestation service, the VM still starts, but there is no cryptographic verification of the software stack and the initrd must unlock the root filesystem on its own.

Bring Your Own Image

You build a custom Linux image with an encrypted root filesystem and a LAUNCH_ARTIFACTS partition (ext4, GPT). Images are verified at upload time. The VM's CPU family and vCPU count come from the vcpu-model and vcpu-count fields of launch-config.json, so you do not set cpuFamily or cores when you create the VM.

Create and Operate VMs in the DCD or the API

Create a Confidential VM in the Data Center Designer (DCD) in Canvas or Xpress mode, or with an ENTERPRISE server-create call in the Cloud API. In the DCD, CPU architecture and cores are read-only and derived from the image; you set the RAM once at provisioning. To restart, use the DCD Reset action or the API.

Attach Additional Data Volumes

You can attach multiple Block Storage volumes. Each must be encrypted with LUKS2, with keys managed through your attestation service or an external KMS. You can increase a storage volume's size, then expand the LUKS container and filesystem from inside the VM.

Verify Firmware Provenance

Download verified OVMF firmware builds from the ionos-cloud/edk2 releases and check their SLSA provenance before you embed them in your image.

Harden the Guest Kernel

For production, build a minimal hardened kernel without console, input, serial, USB, and management-channel drivers, and with loadable modules disabled (CONFIG_MODULES=n). Attestation then confirms that exactly this kernel is running.

Debug from Inside the TEE

Connect through SSH after the VM completes attestation. Serial console and VNC are also supported.

Best For

Scenario Why It Fits
Regulated industry compliance Financial services (DORA, NIS2), healthcare, and manufacturers get verifiable technical controls and a cryptographic audit trail of VM integrity at every startup
Sovereign data processing IONOS CLOUD holds no memory keys and no disk keys and has no administrative path to plaintext data
Platform hosting Partners building confidential platforms give their own users a runtime environment they can verify independently
Secure multi-party data collaboration Federated learning coordinators and TEE-backed query engines process sensitive data that no party, including IONOS CLOUD, can access
Verified multi-tenant SaaS isolation Per-tenant Confidential VMs, each tied to a user-controlled attestation service, give verifiable isolation and EU data residency

Consider Alternatives If

If You Need... Consider Why
To scale CPU or RAM up after creation Dedicated Core Server or vCPU Server Both support upscaling CPU, RAM, NICs, and storage volumes
Standard IONOS CLOUD images, or the SSH keys, Cloud-init, and Enable backup settings of DCD Xpress mode Dedicated Core Server or vCPU Server Confidential VMs need a custom image, and those Xpress settings are not available for them
A location other than Frankfurt (de/fra/2) Dedicated Core Server or vCPU Server Confidential VM is not offered in other locations (see Quick Facts)

Key Considerations

Billing & Costs

  • Main billing: Priced by hardware configuration. Published rates: 0.047 EUR per core per hour and 0.005 EUR per GB RAM per hour (price group PG F)
  • Custom quotes: Contact your account manager for a quote for your regional footprint
  • Capacity: Your contract limits and the available AMD SEV-SNP hardware capacity in the zone set your VM quota. Contact your account manager or support to reserve capacity

Limitations

  • No live migration: Host maintenance causes user-visible downtime and a complete re-attestation after the host restarts. Design workloads to tolerate restarts (redundant VMs, redundant attestation services, graceful shutdown handling)
  • Fixed vCPU count and memory: To change them, prepare a new image and deploy a new VM (see Immutable after creation in Quick Facts)
  • No in-guest restart: Running reboot or shutting down inside the VM terminates it; it does not restart automatically
  • No suspend or resume
  • No hot-plug: You cannot add or remove a NIC or disk while the VM is running. Stop the VM, make the change, restart it, and re-attest
  • No cloud-init: Build image customization into the image at build time
  • No startup volume snapshots: Back up images and manage your build pipeline outside IONOS CLOUD
  • No debug mode: The fixed guest policy disables debug mode, so external memory inspection is impossible
  • Reduced host-side visibility: Host-side tools, memory introspection, live dumps, and external debuggers cannot work
  • Performance overhead: Memory encryption adds CPU cycles to every memory operation; memory-intensive workloads are most affected
  • No in-place key rotation: Rotating the Volume Master Key requires rebuilding and redeploying the VM
  • Side channels: Simultaneous multi-threading is always enabled and cannot be disabled per VM
  • Attestation reachability: The attestation service must be reachable from the VM subnet before start, because VPN is not available during the initrd phase. If it is unreachable, the VM cannot get its disk keys and does not finish starting
  • Shared responsibility: Support cannot extend to in-guest issues (image content, OS configuration, application problems). Application security, secrets handling (never embed secrets in images), and guest-side monitoring are your responsibility
  • Skills required: Linux kernel expertise, cryptographic literacy, and the operational maturity to run a security-critical service

Management Options

  • Data Center Designer (DCD), Canvas and Xpress modes (contract owners, administrators, or users with the Create Data Center privilege)
  • Cloud API
  • SDKs listed in the IONOS CLOUD SDK and tools overview