Contabo Object Storage is an S3-compatible object storage service built on a Ceph cluster following Red Hat production guidance. Unlike Storage VPS, which provides a full virtual machine with a block disk, Object Storage is accessed entirely via the S3 API or a web UI — there is no server to manage.
S3 credentials: Access Key and Secret Key are shown in the Control Panel; the Secret Key can be regenerated there.
Management credentials: the Contabo API and cntb CLI use the OAuth2 credentials (client ID, client secret, API user, API password) from the Control Panel, not the S3 keys.
Bucket and object operations, multipart upload, metadata
Supported
Bucket versioning
Supported
Bucket-wide (put-bucket-versioning); suspending stops new versions but keeps existing ones; current version marked IsLatest: true
Lifecycle configuration
Supported (expiration)
Expiration rules in days, optionally by Prefix
Object Lock
Supported
GOVERNANCE and COMPLIANCE modes; enabled with --object-lock-enabled-for-bucket at bucket creation; retention via put-object-lock-configuration
Bucket policies
Supported
IAM policy format 2012-10-17; principal ARN arn:aws:iam::<s3TenantId>:user/<customerId>:<userId>; s3TenantId via cntb get objectStorages -o=json, userId via cntb get users
Access control lists (ACL)
Supported
Per bucket and per object, via web UI or API; public or private links to individual objects
The S3 API covers most standard operations but does not guarantee full parity with AWS S3; server access logging is not supported.
Object Lock cannot be enabled on an existing bucket — create a new bucket with Object Lock enabled.
Lifecycle rules support expiration only; storage-class transitions are not documented, and expiration deletes objects irreversibly.
SFTP/SCP, FTP/FTPS, NFS/CIFS/SMB and RTSP are not supported — access is via the S3 API and web UI; use a FUSE client (s3fs-fuse, goofys) for filesystem access.
Plain HTTP is not supported (HTTPS only); a custom domain requires a TLS-terminating proxy.
FileZilla Pro forces virtual-hosted-style bucket names and is not compatible; use Cyberduck instead.
Objects changed from public to private may remain cached and accessible for up to one hour after the permission change.