Storage boxes
Storage Boxes
One storage box over S3, SFTP, FTPS, WebDAV and NFS, with an audit log.
What a storage box is
A storage box is a place for files that your apps, servers and people reach over the protocol they already use. A backup tool writes over S3, a person opens the same folder over SFTP or WebDAV, and a server mounts it over NFS.
You don't have to set up or maintain your own file server. We keep the server running and updated. You only work with your files.
Each storage box runs on a server of its own in your private network. Every file is kept on several servers at once.
Why ours
Same files over every protocol
A file uploaded over S3 can be opened over SFTP, FTPS, WebDAV or NFS right away. Each user can be limited to the protocols it needs.
Folders and logins
Give each app and server its own folder and login. A user sees only its folder and can also get read-only access.
Every operation in the log
The audit log shows who uploaded, downloaded or deleted each file, and from where.
An address of its own
Each storage box gets its own public address, so S3, SFTP, FTPS and WebDAV work on their standard ports.
It grows with you
When its space or its file count fills up, the storage box moves to the next package by itself.
Connect the way your software expects
S3 is for apps and backup tools like rclone, restic and the AWS CLI. SFTP takes a password or an SSH key, from servers and file managers. FTPS is for software and devices that only speak FTP, with TLS on top.
WebDAV mounts the box as a drive on macOS, Windows and Linux. NFS mounts a folder on your servers, and several servers can mount the same folder at once.
S3, SFTP, FTPS and WebDAV work from the internet and from your private network. NFS works only from your private networks on the router of the box.
Guarded logins
Addresses that keep guessing passwords are blocked for a while. You set how many failures in how many minutes block an address, and for how long. A blocked address is refused on every protocol until the block ends.
Your office and your servers can be listed, so failures from them are not counted. The panel lists the addresses blocked now, each of which you can unblock, and the blocks of the last 7 days.
How to start
- Create a storage box in the Cloud Panel and pick a package. It gets its own address and a main user.
- Copy the password or the S3 keys of the main user from the storage box page.
- Add users for your apps and servers, each with its own folder and protocols.
Example usage
# S3 with rclone
rclone config create box s3 provider=Other \
endpoint=https://files-3f9a1c.storage.serverscamp.com \
access_key_id=<access key> secret_access_key=<secret key>
rclone copy ./backups box:storage/backups
# SFTP
sftp [email protected]
# NFS, from a server in the same network
sudo mount -t nfs4 <private IP>:/servers/web1 /mnt/boxAlso in every storage box
SSH keys
Add SSH keys to a user to log in over SFTP without a password.
New secrets at any time
Give a user a new password or new S3 keys from the panel. The current ones stop working.
Metrics
Traffic, requests and space, in the panel.
Questions
Can several servers use the same folder?
Yes. Several servers can mount the same folder at once over NFS in your private network.
Does it work with my backup tool?
rclone, restic and the AWS CLI work with it without any setup.
What happens when the storage box is full?
It moves to the next package by itself when its space or its file count fills up. It does not move back down.
Can I mount it over NFS from the internet?
No. NFS works only from the private networks on the router of the storage box.
Can a user only read?
Yes. A user can get read-only access, and each user sees only its own folder.
Do I need a network first?
Yes. A storage box lives in a private network behind a router, the same way your servers do.