Overview
S4 sits between your applications (boto3, aws-sdk, Spark, Trino, DuckDB, or anything that speaks S3) and your real S3 bucket, and transparently compresses each object with a codec chosen per payload: CPU zstd for text and logs, GPU (NVIDIA nvCOMP Bitcomp or zstd) for integer and columnar data, and passthrough for already-compressed inputs.
No application changes are required. S4 keeps the same S3 wire protocol, the same SigV4 authentication, and the same SDK calls. You only change the endpoint URL. Range GET requests stay fast through a sidecar frame index that is compatible with Parquet and ORC readers.
The on-backend format is open, so there is no lock-in. If you stop the gateway, the objects remain readable with the Apache-2.0 s4-codec command-line tool, the s4-codec Python package, or the s4fs fsspec adapter (pandas, pyarrow, and DuckDB can read the data without the gateway).
Operate S4 with built-in day-2 tooling. The s4 estimate command projects savings on your existing bucket before you deploy. The s4 migrate command retro-compresses objects already in the bucket. The s4 recompact command re-compresses cold data at higher levels. The s4 maintain command runs policy-driven maintenance. The savings ledger and the s4 savings command report the storage bytes and dollars actually saved in production. Prometheus metrics and a Grafana dashboard are included.
This listing is billed per pod per hour. The same software is also available free under the Apache-2.0 license as a public container image; the Marketplace build adds metered billing through your AWS bill and is the supported procurement path for enterprises.
Highlights
- 50-80 percent fewer S3 storage bytes for compressible data such as logs, JSON, and columnar files. The reduction is measured, with per-bucket savings reporting built in.
- Zero application changes. S4 exposes an S3 wire-compatible endpoint (SigV4, multipart, Range GET, server-side encryption). Point your SDK at S4 and keep working.
- Open format, no lock-in. Objects stay readable without the gateway through Apache-2.0 command-line, Python, and fsspec tooling.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Description | Cost/unit/hour |
|---|---|---|
Hours | Container Hours | $0.10 |
Vendor refund policy
S4 is billed per pod per hour on metered usage; stop the pods anytime to stop software charges, and a free trial is available. Usage already incurred is generally non-refundable. If you were billed in error or a product defect prevented normal use, email aws-support@abyo.net (abyo software LLC) within 30 days with your AWS account ID, product name (S4 - Squished S3), and billing period. Valid refunds are processed through AWS Marketplace.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
S4 gateway via Helm chart
- Amazon EKS
Helm chart
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
S4 v1.4.0. Client-transparent S3-compatibility campaign: by default the gateway is invisible to S3 clients (compression is server-side, the ETag your client sees is MD5 of the original payload, multipart uploads return the composite ETag S3 returns, and the reserved s4-* user-metadata used internally is stripped from client views). All v1.2.x metering behavior is preserved: S4 confirms entitlement at startup (fail-closed) and reports one metered pod-hour every hour via the AWS Marketplace MeterUsage API. Same drop-in S3-compatible transparent compression gateway (CPU zstd or GPU nvCOMP compression, pre-deployment savings estimation, retro-compression, policy-driven maintenance, and measured-savings reporting).
Additional details
Usage instructions
S4 deploys on Amazon EKS via the provided Helm chart.
-
Subscribe, then follow the AWS Marketplace launch steps for this product to install the Helm chart on your EKS cluster.
-
Metered billing is automatic. The chart carries the Marketplace product code and runs under the service account AWS Marketplace provisions with the aws-marketplace:MeterUsage permission. S4 confirms entitlement at startup (the container exits if the pod is not entitled) and then reports one metered pod-hour every hour to the AWS Marketplace Metering Service.
-
Set your S3 backend endpoint at install time. Override backend.endpointUrl, for example https://s3.us-east-1.amazonaws.com - use the regional S3 endpoint for the bucket you put behind S4.
-
Point your S3 clients (boto3, aws-sdk, Spark, Trino, DuckDB, or anything S3) at the S4 service endpoint. No application code changes are required: same SigV4 auth, multipart, Range GET, and server-side encryption.
-
Billing is per pod per hour through your AWS bill. EKS infrastructure costs are separate and billed by AWS as usual.
Documentation: https://github.com/abyo-software/s4#readme Operations runbook: https://github.com/abyo-software/s4/blob/main/docs/ops/runbook.md
Resources
Vendor resources
Support
Vendor support
Community support is available through GitHub issues at https://github.com/abyo-software/s4/issues . Marketplace subscribers can email aws-support@abyo.net for best-effort response within 2 business days. Documentation, an operations runbook, and a threat model are included in the repository.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
