Hetzner Object Storage (S3-compatible, Ceph-backed)

Quake AI concept: S3 Compatibility

• Hetzner Object Storage endpoint format is location-scoped: {bucket}.{location}.your-objectstorage.com (e.g. my-bucket.fsn1.your-objectstorage.com); Quake AI uses a regional endpoint. Credentials are project-scoped and must be regenerated per project.
• Hetzner does not publish a full S3 compatibility matrix; advanced operations (S3 Select, Object Lock, Replication, Lifecycle rules) are not documented as supported. Both Hetzner and Quake AI use Ceph RGW, so core S3 CRUD, multipart upload, and SigV4 auth work on both.
• Hetzner credentials are project-bound access key/secret pairs separate from Hetzner API tokens; the same S3 credential cannot be used across projects. Quake AI EC2 credentials are tied to a Keystone user and scoped per project via role assignments.
• Hetzner Object Storage locations (fsn1, nbg1, hel1) are distinct endpoints; buckets in different locations require separate credentials and aliases. Quake AI object storage uses a single regional endpoint per deployment.