Encryption at Rest requirements and limitations
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.
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
- A Dedicated Server in your OVHcloud account
Instructions
The tables below summarise eligibility and limitations. Check them before you enable Encryption at Rest.
Eligibility
A server must meet every condition below:
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:
Limitations
The following limitations apply:
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.