Pterodactyl with Enderchest
Pterodactyl's panel has a built-in S3 backup driver. Point it at Enderchest and every server backup, including a 40 GB modded Minecraft world, lands in a bucket at $3 per TB with free restores.
Endpoint https://s3.enderchest.store · region eu-ams-1 · path-style addressing · an access key from the console. 50 GB free on every account, then $3 per TB per month; downloads and API requests are free.
Panel settings
Create a bucket in the console (for example server-backups) and a read-write access key. Then add these lines to the panel's .env:
APP_BACKUP_DRIVER=s3 AWS_DEFAULT_REGION=eu-ams-1 AWS_ACCESS_KEY_ID=YOUR_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY=YOUR_SECRET_ACCESS_KEY AWS_BACKUPS_BUCKET=server-backups AWS_ENDPOINT=https://s3.enderchest.store AWS_USE_PATH_STYLE_ENDPOINT=true
Then clear the configuration cache and restart the queue so the panel picks the values up:
cd /var/www/pterodactyl php artisan config:clear php artisan queue:restart
What happens on the node
The panel hands each Wings node a presigned upload link, and Wings sends the backup straight to Enderchest, so the node needs outbound HTTPS to s3.enderchest.store. Large backups go up in parts; the default part size of 5 GB is fine. Restores and downloads come back the same way at no charge.
Existing local backups
Backups made before the switch stay on the node under the local driver and still restore. If you ever move back to local backups, keep the S3 lines in .env so the panel can still reach the ones stored here.
Sizing
A vanilla Minecraft world is a few hundred megabytes; a modded one with a long history can be 20 to 50 GB. The first 50 GB on an account is free, and above that storage is $3 per TB per month counted by the day, so a host with twenty servers averaging 10 GB each pays about $0.60 a month.
Other clients
- rclone
- restic
- AWS CLI
- s3cmd and MinIO client
- boto3 (Python)
- Kopia
- Duplicati
- Synology Hyper Backup
- TrueNAS
- Proxmox Backup Server
- WordPress (UpdraftPlus)
Every supported operation is listed in the documentation. Questions: [email protected].