SLA KMS

These product-specific SLAs define the Service Availability Target for Key Management Service (KMS). It applies to each Client using the Service. Capitalized terms used herein but not defined herein shall have the meanings set forth in the Exoscale Terms and Conditions or EUSA, whichever applies.

SLA Definitons

Product Specifications

For detailed product features, technical specifications, and tutorials, please refer to the Exoscale documentation.

Shared Responsibility Model

Encryption-at-Rest at Exoscale relies on Exoscale KMS, as services such as Compute and Object Storage manage their encryption keys through it.

By default, data is encrypted using your organization’s default key. This key is fully managed by Exoscale and is subject to specific usage constraints please refer to the Limits and Quotas section.

Alternatively, you may choose to re-wrap the encryption keys used to encrypt your data under any custom KMS key of your choice. While this provides greater freedom and control over your security policies, it also shifts the responsibility for the key’s availability to your organization. If a custom key is actively referenced or required by other Exoscale services for your workloads, you are solely responsible for ensuring its continued availability.

[!WARNING]

Exoscale is not responsible for any permanent data loss or service disruption resulting from lifecycle management operations you perform on custom keys.

Exclusions

For the complete list of SLA exclusions, please refer to the General Exoscale Terms and Conditions.

Retribution

Claim Service Credit

To claim a Service Credit, open a support ticket in the Exoscale Portal within 10 business days of the incident. More details