Hippius S3 is a drop-in replacement for Amazon S3 with a focused feature set. If you already have code that works with AWS S3, you only need to change three things: endpoint URL, region, and credentials. Everything else stays the same.
This page lists every S3 API operation and whether Hippius supports it.
Connection Parameters
| Parameter | Value |
|---|
| Endpoint | https://s3.hippius.com |
| Region | decentralized |
| Signature | AWS Signature V4 |
| Addressing | Path-style (s3.hippius.com/bucket/key) |
Bucket Operations
| Operation | Status | Notes |
|---|
CreateBucket | ✅ Supported | |
DeleteBucket | ✅ Supported | Must be empty |
HeadBucket | ✅ Supported | |
ListBuckets | ✅ Supported | |
GetBucketLocation | ✅ Supported | Returns decentralized |
PutBucketAcl | ✅ Supported | private, public-read, public-read-write, authenticated-read |
GetBucketAcl | ✅ Supported | |
PutBucketPolicy | ✅ Supported | JSON IAM-style policies |
GetBucketPolicy | ✅ Supported | |
DeleteBucketPolicy | ✅ Supported | |
PutBucketTagging | ✅ Supported | |
GetBucketTagging | ✅ Supported | |
DeleteBucketTagging | ✅ Supported | |
PutBucketLifecycleConfiguration | ⚠️ Partial | Basic expiration rules only |
GetBucketLifecycleConfiguration | ⚠️ Partial | |
PutBucketVersioning | ❌ Not supported | |
GetBucketVersioning | ❌ Not supported | |
PutBucketCors | ❌ Not supported | CORS is handled at the gateway level |
PutBucketNotificationConfiguration | ❌ Not supported | |
PutBucketReplication | ❌ Not supported | Data is replicated by the network automatically |
PutBucketLogging | ❌ Not supported | |
Object Operations
| Operation | Status | Notes |
|---|
PutObject | ✅ Supported | Up to ~5 TiB via multipart |
GetObject | ✅ Supported | Range requests supported (video streaming) |
HeadObject | ✅ Supported | |
DeleteObject | ✅ Supported | |
DeleteObjects | ✅ Supported | Bulk delete |
CopyObject | ✅ Supported | |
ListObjectsV2 | ✅ Supported | Pagination, prefix, delimiter |
ListObjects | ✅ Supported | V1 — prefer ListObjectsV2 |
PutObjectAcl | ✅ Supported | Per-object ACLs |
GetObjectAcl | ✅ Supported | |
PutObjectTagging | ✅ Supported | |
GetObjectTagging | ✅ Supported | |
DeleteObjectTagging | ✅ Supported | |
SelectObjectContent | ❌ Not supported | S3 Select |
PutObjectLockConfiguration | ❌ Not supported | Object Lock / WORM |
PutObjectRetention | ❌ Not supported | |
Multipart Upload
| Operation | Status | Notes |
|---|
CreateMultipartUpload | ✅ Supported | |
UploadPart | ✅ Supported | |
CompleteMultipartUpload | ✅ Supported | |
AbortMultipartUpload | ✅ Supported | |
ListMultipartUploads | ✅ Supported | |
ListParts | ✅ Supported | |
Presigned URLs
| Operation | Status | Notes |
|---|
| Presigned GET | ✅ Supported | Max expiry: 7 days |
| Presigned PUT | ✅ Supported | Max expiry: 7 days |
| Presigned DELETE | ✅ Supported | |
What's Different from AWS S3
Hippius S3 is S3-compatible but not an AWS clone. Here's what to keep in mind:
- Path-style only. Virtual-hosted style (
bucket.s3.hippius.com) is not supported. Always use forcePathStyle: true or addressing_style: "path".
- Single region. There's no multi-region setup. The region is always
decentralized.
- No versioning. Objects are overwritten in place. If you need version history, manage it in your application.
- No S3 Select. You can't query inside objects. Download the object and process it locally.
- No event notifications. There's no equivalent of S3 Event Notifications or Lambda triggers.
- Replication is automatic. The Hippius network handles data replication across miners. You don't need to configure cross-region replication.
Tested Clients
These S3 clients are tested and confirmed to work with Hippius S3:
Further Reading