S3-compatible storage is object storage that supports the Amazon S3 API, the de facto standard interface for storing and retrieving objects over HTTP. Applications, backup software and tools built for Amazon S3 can use S3-compatible storage from another provider, or on-premises, with little or no code change.
How S3-compatible storage works
Data is stored as objects inside buckets. Each object has a unique key, the data itself and metadata. Applications use standard S3 operations such as PUT, GET, LIST and DELETE, authenticated with access keys. Because the API is the same, the application only needs a different endpoint URL and credentials to point at a different provider. See object storage for background.
Common S3 features to check
“S3-compatible” can mean different levels of support. Check for:
- Core operations: PUT, GET, LIST, DELETE and multipart upload for large files.
- Versioning: keeps previous versions of objects.
- Object lock: immutable, WORM retention for backups and compliance.
- Lifecycle policies: automatic expiry or movement of objects.
- Access control: bucket policies and per-user keys.
- Encryption: at rest and in transit.
- Audit logging: records of who accessed what.
Why use S3-compatible storage instead of Amazon S3?
| S3-compatible storage (private / regional) | Amazon S3 | |
|---|---|---|
| Location | Your data center, a colocation site or a local provider | AWS regions only |
| Egress fees | Often low or none | Charged per GB transferred out |
| Cost predictability | Usually flat per-TB pricing | Storage, requests and transfer billed separately |
| Data residency | Choose the exact country and facility | Limited to AWS region locations |
| Ecosystem | Works with S3 tools and SDKs | Native |
Common use cases
- Backup target for Veeam, Commvault, HYCU and others (see Backup as a Service)
- Data lakes and AI training data sets
- Media and content archives
- Application data for cloud-native apps and Kubernetes
- Long-term archives (see backup and archival storage)
S3-compatible storage with Zadara
Zadara Object Storage supports the S3 and Swift APIs and runs on Zadara zStorage alongside block and file storage. It includes object lock for immutability and object storage audit logs, and it can be deployed on-premises, in colocation or in Zadara’s edge cloud locations. Because Zadara does not charge data egress fees on its own network, reading your data back does not come with surprise transfer bills. Learn more on the Zadara Object Storage page.
Frequently asked questions
What does S3-compatible mean?
It means the storage accepts the same API calls as Amazon S3, so software written for S3 can use it by changing the endpoint and credentials.
Is S3-compatible storage as reliable as Amazon S3?
Reliability depends on the provider’s architecture, redundancy (for example erasure coding or replication) and SLA, not on the API. Compare durability and availability commitments directly.
Can I use S3-compatible storage for backups?
Yes. It is one of the most common backup targets, especially when it supports object lock for immutable backups.
