For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/es/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/es/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/es/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-limitations.md.
Ir al contenido

Encryption at Rest requirements and limitations

Ver como Markdown

Check which Dedicated Servers, regions and configurations support Encryption at Rest, and the limitations that apply at launch

Objective

This guide lists the conditions a Dedicated Server must meet to use Encryption at Rest, and the limitations that currently apply.

Info

The encryption key stays inside each disk. OVHcloud manages the passphrase that unlocks the disks, and it is never sent to you. Using your own keys is not available. For more information, read What is Encryption at Rest on a dedicated server?

Requirements

Instructions

The tables below summarise eligibility and limitations. Check them before you enable Encryption at Rest.

Eligibility

A server must meet every condition below:

TopicCondition
RangeScale 2026 Dedicated Servers. Other ranges are not eligible yet.
RegionEurope and Canada. Other regions are not available yet.
BootThe server boots through the standard OVHcloud network boot.
NetworkOVHcloud Link Aggregation (OLA) is not enabled.
Server stateThe server is in service. Encryption at Rest cannot be enabled on a suspended or blocked server.

To check a given server, read it with the OVHcloud API v2 and ask for the availability of its actions (see Manage Encryption at Rest on a dedicated server with the API):

With the actions=true parameter, the response lists the ENABLE_ENCRYPTION_AT_REST action with its status: AVAILABLE, UNAVAILABLE (the blockedBy field gives the reasons, for example NOT_ELIGIBLE) or UNDETERMINED.

Incompatibilities

Some features cannot be combined with Encryption at Rest:

FeatureStatus
OVHcloud Link Aggregation (OLA)Not compatible. Using both requires the Private Boot feature, which is not available yet. Until then, the two features are mutually exclusive.
Custom boot scriptNot compatible.
Windows rescue modeNot compatible. The Linux rescue mode is supported, and the disks are unlocked automatically, as at a normal boot.

Limitations

The following limitations apply:

TopicLimitation
GranularityAll the disks of the server, or none. You cannot select disks one by one.
SchedulingThe operation starts immediately. It cannot be scheduled or tied to a maintenance window.
DurationUp to 24 hours from end to end, longer if an intervention in the datacentre is needed. Other operations on the server are refused while it runs.
DataEnabling erases all the data and requires an OS reinstall. Disabling cryptographically erases the disks and also requires an OS reinstall.
DisablingAvailable from the OVHcloud Console and the OVHcloud API. Disabling erases the disks and requires an OS reinstall.
KeysThe encryption key stays inside each disk. OVHcloud manages the passphrase that unlocks the disks. Customer keys and manual unlocking are not available.
NotificationsNo alerts on unlock events.
AutomationAvailable through the OVHcloud API v2. Not available in the OVHcloud Terraform provider.
PricingIncluded, at no extra charge.

Go further

Enable or disable Encryption at Rest on a dedicated server

Understanding link aggregation on dedicated servers

How to activate and use rescue mode

Encryption at Rest on dedicated servers: FAQ

Join our community of users.

¿Le ha resultado útil esta página?