S3 storage overview
Coolify connects to S3-compatible storage for backup files. You create the bucket with a storage provider, then add its connection details to Coolify as an S3 storage.
Coolify can also store backups on an SFTP, FTPS, or WebDAV server. See SFTP, FTPS, and WebDAV storage.
Before you add S3 storage
Create the bucket with your provider and collect these connection details:
- Endpoint
- Bucket name
- Region
- Access key
- Secret key
Coolify uses MinIO's mc client to transfer backup files. When you validate the storage, Coolify sends a ListObjectsV2 request to the configured bucket.
The bucket must already exist before you add and validate the storage in Coolify.
Choose a storage provider
These guides cover the complete provider setup and the values to enter in Coolify:
| Provider | Provider setup | Guide |
|---|---|---|
| Amazon S3 | S3 bucket, IAM policy, IAM user, and access key | Configure Amazon S3 |
| Cloudflare R2 | R2 bucket and Object Read & Write API token | Configure Cloudflare R2 |
| Neon Object Storage | Branch bucket, S3 endpoint, and access key pair | Configure Neon Object Storage |
| Supabase Storage | Storage bucket, S3 endpoint, and access key pair | Configure Supabase Storage |
Other supported providers
Coolify also supports these S3-compatible storage providers:
- DigitalOcean Spaces
- MinIO
- Backblaze B2
- Scaleway Object Storage
- Hetzner S3 Storage
- Wasabi Hot Cloud Storage
- Vultr
- CloudPe Object Storage
- IDrive e2
Other providers may also work. If you successfully connect another provider, let the Coolify team know.
Add the storage to Coolify
After you prepare the bucket and credentials:
- Open Storage in the Coolify sidebar.
- Select New storage.
- Keep Type set to S3.
- Enter Name, optional Description, Bucket, Region, Access Key, and Secret Key. Split the endpoint into Protocol, Host, optional Port, and optional Path. Keep the bucket name separate from the endpoint.
- Turn on Skip TLS certificate verification only if the endpoint uses a self-signed or private CA certificate. See Self-signed certificates.
- Select Validate Connection & Continue.
After validation succeeds, Coolify opens the storage details page. The S3 storage is then ready to select when you configure a backup. Database and volume backup schedules can select multiple destinations; Coolify uploads each backup to every selected destination and tracks each copy separately.
Self-signed certificates
Turn on Skip TLS certificate verification for an endpoint with a self-signed or private CA certificate. Coolify then accepts any certificate for the connection test, backups, restores, and the deletion of old backups.
With this setting on, Coolify does not check the certificate of the endpoint. Turn it on only when the endpoint cannot use a trusted certificate.
The setting does not apply to your browser. Backup downloads open a link to the storage, so the browser must still trust the certificate. Through the API, set skip_tls_verification on the S3 storage.
Recovering an unusable storage
Coolify tests S3 storages marked unusable again every hour. Once the connection works, the storage becomes usable automatically. You can also validate it after correcting credentials or connectivity.
