mirror of
https://github.com/mulgadc/spinifex.git
synced 2026-10-15 09:01:31 +00:00
Julian Sommer
bf622f3745
The roadmap carries IPv4 pools, local zones as an installation option, and an S3 gap closure naming inventory and intelligent tiering. All three were published as operations this platform will never serve. Twenty-nine EC2 operations — local gateways, CoIP pools, BYOIP and the zone group opt-in — and nine S3 operations are no longer declared. Carrier gateways stay, as a route into a telco's 5G network in a Wavelength Zone.
title, seoTitle, description, category, sections, tags
| title | seoTitle | description | category | sections | tags | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| S3 API Coverage | Amazon S3 API Coverage on Spinifex — Spinifex Docs | The Amazon S3 API operations Predastore serves on the platform's S3 endpoint, alongside the AWS-hosted features it does not offer and why each is absent. | Coverage |
|
|
S3 API Coverage
Overview
Predastore implements 19 operations in the S3 2006-03-01 API model.
Predastore serves this endpoint
S3 is the one surface the AWS gateway does not answer itself. Object storage runs on Predastore, which serves the S3 REST API directly over its own endpoint.
Routed is not the same as conforming
This page says an operation is routed to a handler. It does not say the handler's behaviour matches S3 in every case.
That behaviour is measured separately, against the ceph/s3-tests suite Ceph RGW, MinIO and Garage are all validated with, and the results are published in Predastore's S3 compatibility report.
Operations
| Operation | Status |
|---|---|
AbortMultipartUpload |
✅ Implemented |
CompleteMultipartUpload |
✅ Implemented |
CopyObject |
✅ Implemented |
CreateBucket |
✅ Implemented |
CreateMultipartUpload |
✅ Implemented |
CreateSession |
⛔ Not applicable 2 |
DeleteBucket |
✅ Implemented |
DeleteObject |
✅ Implemented |
DeleteObjects |
✅ Implemented |
GetBucketAccelerateConfiguration |
⛔ Not applicable 1 |
GetBucketRequestPayment |
⛔ Not applicable 4 |
GetObject |
✅ Implemented |
HeadBucket |
✅ Implemented |
HeadObject |
✅ Implemented |
ListBuckets |
✅ Implemented |
ListMultipartUploads |
✅ Implemented |
ListObjects |
✅ Implemented |
ListObjectsV2 |
✅ Implemented |
ListParts |
✅ Implemented |
PutBucketAccelerateConfiguration |
⛔ Not applicable 1 |
PutBucketRequestPayment |
⛔ Not applicable 4 |
PutObject |
✅ Implemented |
UploadPart |
✅ Implemented |
UploadPartCopy |
✅ Implemented |
WriteGetObjectResponse |
⛔ Not applicable 3 |
Notes
- Transfer acceleration routes uploads over AWS edge locations, which an on-premise deployment has none of.
- Sessions authenticate S3 Express One Zone directory buckets, a storage class this platform does not offer.
- S3 Object Lambda rewrites a response from a Lambda function, and Lambda is not offered.
- Requester Pays shifts transfer charges to the caller, which needs AWS billing behind it.