s3sync-awscliv2

This application backs up every folder mounted at `/data/` to a given AWS S3 path using the `aws s3 sync` command.

  • Backup
  • Cloud
This application backs up every folder mounted at `/data/` to a given AWS S3 path using the `aws s3 sync` command. It requires a pair of (IAM) Access and Secret Keys. You can supply the usual s3 sync parameters such as `--delete` and everything else. The cron schedule defines how often the sync command is executed, and it uses a lockfile to avoid parallel executions. This app has been based on the already available s3sync, however that was outdated, this version contains AWS CLI V2 and doesn't rely on extra python packages.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
72last commit 25 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 27 days ago

GitHub stars
1
Open issues
0
Last commit
2026-10-27
Latest release
v0.1.0
License
MIT
Activity
rising

Checked 9 days ago - source: GitHub (jterpstra1/docker-s3sync)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Configuration Set ACCESS_KEY, SECRET_KEY, REGION, and S3PATH environment variables; optionally S3SYNCPARAMS for custom aws s3 sync flags (e.g. --delete). Mount source folders under /data/ before starting the container. source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which local folders does s3sync back up?

Mount the folders you want to back up under the /data directory in the container.

Which environment variables should I set for basic use?

Set ACCESS_KEY, SECRET_KEY, REGION, and S3PATH. You can also set S3SYNCPARAMS for extra aws s3 sync options.

Can I pass --delete or other AWS sync flags?

Yes, put extra aws s3 sync parameters in S3SYNCPARAMS. If you use --delete, it removes files not present in the synced folders inside the specified S3 prefix.

How often does the sync run?

It runs every hour by default with CRON_SCHEDULE set to 0 * * * *. You can change it using standard CRON notation, but a more frequent schedule is not advised.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads