Skip to main content

Security and data location

This page answers the questions security and compliance teams usually ask about Object Storage: where the data is, how it's protected, and what you're responsible for.

Where your data is stored​

RegionData centreCountry
DX1Equinix DX1, DubaiUnited Arab Emirates
VIE2Digital Realty, ViennaAustria
  • A bucket is stored in the region where you create it.
  • Data is not copied to another region unless you turn on replication yourself or ask us to set up geo-replication.
  • Each region is a separate storage cluster.

Encryption​

How it works
At restData is encrypted with AES-256 at the storage layer. The keys are managed inside the storage platform.
In transitEndpoints use HTTPS. You can require TLS 1.2 or newer with a bucket policy.
Server-side encryption optionsNot offered. SSE-S3, SSE-C and SSE-KMS aren't supported.

Because encryption at rest uses platform-managed keys, it protects against lost or stolen disks, not against someone with access to your account. If you need data that only you can read, encrypt it before upload, for example with restic or an rclone crypt remote. See the backup target guide.

Redundancy​

Every object is stored either as several copies or with erasure coding, spread across different servers. If a disk or a whole server fails, your data stays available and is rebuilt automatically.

Redundancy protects against hardware failure, not against deletion. For protection against deletion, use versioning and Object Lock. For protection against the loss of a whole site, use replication.

Access control​

  • Access needs an access key pair. Keys can be disabled, rotated and deleted at any time.
  • Bucket policies limit access by user, action, folder, IP address and TLS version.
  • Object Lock in Compliance mode prevents deletion or overwrite until a retention date.
  • New buckets are private. Only the owner has access until you add a policy.

Your responsibilities​

  • Keep access keys secret, and rotate them regularly.
  • Give each application or server its own S3 user with only the permissions it needs.
  • Encrypt sensitive data before upload if you need control over the keys.
  • Test that you can restore your data.

More information​

Was this page helpful?