Create buckets, attach policy defaults, and issue scoped credentials cleanly.
One release workflow, several operator-ready installation paths.
Multi-arch release archives and Debian packages for the normal deployment targets.
Deploy Seamlessly
The high-confidence routes stay closest to hand: a direct installer, a signed APT repository, a direct Debian package, and a pinned GHCR runtime path.
Download the right release archive for the current platform, verify checksums when published, and install `s3ctl` into the target directory.
curl -fsSL ./install.sh | bash
The installer supports --version, --install-dir, and --binary-name; macOS uses a user-owned home bin dir.
Use a release package directly when you want a Debian install without wiring an APT source.
Release package metadata will appear here after publication.
The release hub will prefer the amd64 package when one is published.
When repository signing is configured, the landing page publishes a Debian repository beside the release hub.
APT repository metadata will appear here after publication.
Pull the published multi-arch image when you want the release path to stay container-native.
docker run --rm ghcr.io/soakes/s3ctl:latest --help
Use the published image when you want the install path to stay container-native.
Release Payload
Use the release hub for installation, then drive bucket provisioning from flags, environment variables, JSON config, or CSV batch input.
Open Documentation