S4 Container
S3 compression container for Amazon EKS
Container build of the S4 transparent compression gateway. Deploy the drop-in S3-compatible gateway on any CPU node in Amazon EKS via the included Helm chart, point your S3 clients at it, and cut S3 storage bytes 50–80% for compressible data. Metered per pod-hour, fails closed without a Marketplace entitlement. Same binary as the free `ghcr.io` image.
S4 Container is the container distribution of the transparent S3-compatible compression gateway. It is the same binary as the AMI build (nvCOMP / GPU for integer and columnar data; CPU zstd for text and log data) and deploys to small CPU nodes on Amazon EKS via the included Helm chart. Zero application changes, no lock-in — objects stay readable without the gateway via Apache-2.0 CLI / Python / fsspec tooling. The paid container verifies entitlement via AWS Marketplace `RegisterUsage` at startup and fails closed when not entitled. Metered per pod-hour.
Highlights
Drop in on Amazon EKS: bundled Helm chart, runs on any CPU node. S3 clients work unchanged against the S3 wire-compatible endpoint.
Cut S3 storage bytes 50–80% for compressible data. Same binary as the AMI, with measured per-bucket savings reporting (s4 savings) built in.
Per pod-hour metering with Marketplace fail-closed entitlement: the container calls `RegisterUsage` at startup and refuses to serve when not entitled. Same code as the free `ghcr.io` image.
Pricing model
Hourly per-pod software fee billed by AWS + the EC2 nodes in your own EKS cluster. No license keys; entitlement verified via Marketplace `RegisterUsage`.
Other S4 products
S4 — Squished S3
Transparent GPU S3-compression gateway
S4 Logs
Archive CloudWatch Logs to zstd S3
S4 Metrics
Govern CloudWatch metric cardinality