website logo
Create accountLogin
Home
DCS
Node
Resources
Help center
Navigate through spaces
Home
DCS
Node
Resources
Help center
⌘K
Storj DCS
Get Started
AWS CLI and Hosted Gateway MT
AWS SDK and Hosted Gateway MT
Uplink CLI
Satellite Admin Console
Object Browser
Downloads
Download Uplink CLI
Download Self-hosted S3 Compatible Gateway
Download Storj Client Libraries
SDKs & Reference
Tutorial
How-to Guides
Concepts
Support
Support Overview
FAQ
Community Forum
Status Page
Help Desk
Billing, Payment & Accounts
Resources
Moved Documents
Docs powered by archbee 
6min

S3 Compatibility

The Storj DCS S3-compatible Gateway supports a RESTful API that is compatible with the basic data access model of the Amazon S3 API.

The Storj DCS S3 Gateway is well-suited for many application architectures, but the S3 standard was designed for centralized storage and there are a few areas where a decentralized architecture requires a different approach.

Storj DCS offers two options for S3 compatibility:

  1. Gateway-MT: Storj hosted S3 Compatible Service
  2. Gateway-ST: Self-hosted S3 Compatible Binary (run your own S3 endpoint)

The latest compatibility can be found in the compatibility table for GatewayST in our GitHub repo.

When to use GatewayMT

If you have an existing application that is using an S3-compatible object storage service and you want to switch to Storj DCS, the easiest way to switch is to use the hosted S3-compatible service. The main design decision you need to be aware of is that Gateway-MT uses server-side encryption. You can learn about the supported commands and endpoints for S3 compatibility under the SDK & Reference section for the Storj-hosted S3 Compatible Gateway.

When to use GatewayST

If you have an hybrid cloud architecture, are working with on-premise data, or have other needs to host your own S3-compatible object storage service you may want to use the self-hosted GatewayST. The two main design decisions you need to be aware of are that:

  1. GatewayST uses end-to-end encryption.
  2. When you host your own Gateway, that gateway is handling the erasure coding and direct peer-to-peer transfer of data to storage nodes. You will need to account for the upstream bandwidth associated with the expansion factor related to erasure coding the data and any associated overhead related to concurrent connections with storage nodes related to parallel transfers.

You can learn about the supported commands and endpoints for S3 compatibility under the SDK & Reference section for the Storj-hosted S3 Compatible Gateway.

Updated 12 Aug 2022
Did this page help you?
Yes
No
UP NEXT
File Repair
Docs powered by archbee 
TABLE OF CONTENTS
When to use GatewayMT
When to use GatewayST