S3 Compatibility
The Tardigrade S3 Gateway supports a RESTful API that is compatible with the basic data access model of the Amazon S3 API.
The Tardigrade S3 Gateway is well-suited for many application architectures, but there are a few edge cases to be aware of:
API Features | Status (support/not supported) | Remarks |
List Buckets | Supported | Do not return a sorted list because of the encryption with object keys |
Delete Bucket | Supported | |
Create Bucket | Supported | |
Bucket Lifecycle | Not Supported | |
Policy (Buckets, Objects) | Not Supported | |
Bucket Website | Not Supported | Configuration needed --website — take a look at Uplink S3 Gateway how to use it |
Bucket ACLs (Get, Put) | Not Supported | Supported through restricted access grant only, configuration needed on the gateway |
Bucket Location | Not Supported | |
Bucket Notification | Not Supported | |
Bucket Object Versions | Not Supported | |
Get Bucket Info (HEAD) | Supported | |
Bucket Request Payment | Not Supported | |
Put Object | Supported | To be implemented in future |
Delete Object | Supported | |
Get Object | Supported | |
Object ACLs (Get, Put) | Not Supported | Supported through restricted access grant only, configuration needed on the gateway |
Get Object Info (HEAD) | Supported | |
POST Object | Supported | To be implemented in future |
Copy Object | Partially Supported | Not done on the server-side, this is done on the client-side and then re-uploaded |
Multipart Uploads | Partially Supported | Support upload of all parts in right sequence, committing objects right after. No support for resume uploading parts in parallel. |
Object Tagging | Not Supported | |
