Leafcloud Object Storage vs OVHcloud

S3 API at leafcloud.store (europe-nl-ams1)

Path-style S3 endpoint https://leafcloud.store, region europe-nl-ams1. Works with AWS CLI, boto3, rclone, Cyberduck, MinIO mc, and other S3 SDKs. Documented features include public or private containers, bucket policies and ACLs, multipart uploads, and presigned URLs. Max object size is 5 TB via multipart. Authentication uses OpenStack EC2 credentials (openstack ec2 credentials create), not the dashboard password.

OpenStack Swift and Horizon dashboard

The same store is reachable as OpenStack object storage (Swift). Create and browse containers at create.leaf.cloud under Object Store. Native CLI uses project-scoped OpenStack auth (openstack container create / object create). Container names must be unique across all Leafcloud users. Docs say there is a limit on how many containers you can create (the exact quota is not published).

Ceph cluster with 3x replication in Amsterdam

The product page describes a Ceph backend (Apache 2.0 software) with triple replication across separate physical nodes in Amsterdam. Persistent objects sit at the Core facility. Compute Leaf sites are a different path and are not where object data is stored, according to the security pages. This is a single-region store, not a multi-region S3 deployment.

SSE-C plus TLS in transit

Official docs show S3 server-side encryption with customer-provided keys (SSE-C, AES256). Leafcloud uses the key on each request and does not store it. Lose the key and you cannot read the object. The product table also lists encryption at rest and TLS in transit as supported. DPA language is TLS 1.2+. LUKS-by-default messaging on the security pages refers to block volumes, not this object API.

Terraform state, Velero, and Nextcloud recipes

Leafcloud publishes working recipes for Terraform’s S3 backend (path-style, skip checksum/region checks, endpoint leafcloud.store), Velero Kubernetes backups (s3ForcePathStyle plus s3Url), and Nextcloud primary objectstore pointing at leafcloud.store:443. Useful if you already run those tools. Object versioning is not available, so state and backup designs must version keys themselves or copy out.

Protección anti-DDoS y vasta capacidad de red

Cada servicio OVHcloud incluye mitigación anti-DDoS ilimitada, limpiando ataques en capas 3, 4 y 7 sin tarifas por tiempo de inactividad. La red global supera 100 Tbit/s, garantizando baja latencia y alto rendimiento. No hay cargos por tráfico saliente, a diferencia de algunos rivales, lo que ayuda a controlar costes para apps intensivas en datos como streaming o copias de seguridad.

Sostenibilidad con PUE bajo y reutilización de recursos

OVHcloud reporta un power usage effectiveness (PUE) de 1,28 en sus instalaciones, superando promedios del sector. Usa 7 veces menos agua que competidores y funciona con fuentes de energía 100 % bajas en carbono. Los servidores se reutilizan para usos secundarios antes del reciclaje, apuntando a cero residuos en vertederos para 2025. Este enfoque reduce costes operativos trasladados a clientes.

Nube pública OpenStack y reversibilidad

Construida sobre OpenStack, la nube pública soporta precios pay-as-you-go con acceso API para automatización. Las opciones de nube privada evitan lock-in mediante herramientas de exportación de datos y formatos estándar. Los clientes retienen control total, sin minería de datos para anuncios. Funciones como vRack de red privada conectan servicios sin problemas entre regiones.