S4 Container
S3 compression container for Amazon EKS
When does this pay back?
Example: $10,000/month in compressible S3 storage
At $10,000/month in compressible S3 storage spend, a 50–80% reduction is roughly $5,000–$8,000/mo — gross avoided usage charge before the S4 software fee, runtime compute, and workload differences.
Estimate your savings
Enter your relevant monthly spend or usage for a rough estimate — no bill upload needed.
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.
Why it's cheaper
Assumes deploying S4 as a Pod on an existing EKS cluster (with a GPU node group) to compress 100 TB → S3 at ~3× ratio.
- S3 storage (100 TB)
- $2,300 / mo
- Monthly total
- $2,300 / mo
- S3 storage (34 TB compressed)
- $800 / mo
- GPU node (g6.xlarge) + software fee
- $590 / mo
- Monthly total
- $1,390 / mo
Sizing the S4 Container node by write load
| Write load | Recommended node | Node cost | Total at 100 TB stored |
|---|---|---|---|
| ~1 TB / day | g4dn.xlarge | $385 / mo | $1,185 / mo (−49%) |
| ~10 TB / day | g6.xlarge | $590 / mo | $1,390 / mo (−40%) |
| High-concurrency / 100 TB / day | g6.4xlarge | $965 / mo | $1,765 / mo (−23%) |
Illustrative example. S4 Container shares the same compression ratio and economics as the AMI version of S4; the only difference is the deployment shape (EKS Pod instead of an EC2 AMI). The EKS control plane fee ($73/mo) is omitted on the assumption you reuse an existing cluster. Node prices are g4dn / g6 on-demand.
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