Amazon S3 compatible storage as a Windows Drive

The Amazon S3 API is widely used by cloud and object storage providers. TntDrive can connect to services that provide an Amazon S3 compatible API and mount their buckets as Network or Removable drives in Windows.

Examples include Wasabi, Backblaze B2, Cloudflare R2, and DigitalOcean Spaces. Each provider implements a different subset of the Amazon S3 API, so use the endpoint, signature version, and addressing model documented by your provider.

Information required to connect

• REST Endpoint - the API endpoint supplied by your storage provider. Enter the endpoint hostname, such as s3.us-east-1.wasabisys.com, without a bucket name or object path. The protocol prefix is optional; TntDrive uses the Use secure transfer (SSL/TLS) setting to select HTTPS or HTTP.
• Access Key ID - the access key or user ID issued by your storage provider.
• Secret Access Key - the corresponding secret key. This is not your account password.
• HTTPS support - keep Use secure transfer (SSL/TLS) enabled when your provider supports a secure endpoint.

Add an Amazon S3 compatible storage account

1. Start TntDrive Dashboard and choose Accounts > Add new account...

   

2. In the Add New Account dialog, enter a descriptive account name.

   

3. Select Amazon S3 Compatible Storage as the account type.

4. Enter the REST Endpoint supplied by your storage provider.

5. Enter your Access Key ID and Secret Access Key.

6. Keep Use secure transfer (SSL/TLS) enabled unless your provider explicitly requires HTTP.

7. Click Add new account.

The account is now available when you add or edit a mapped drive in TntDrive.

Advanced Amazon S3 compatible storage settings

Click advanced settings.. in the lower-left corner of the account dialog to configure provider-specific connection options.

• Signature Version - Signature V4 is the default and recommended signing method. Select V2 only when your storage provider explicitly requires the legacy signature version.
• Addressing Model - Path style places the bucket name in the request path and is the default. Virtual hosted style places the bucket name in the hostname and requires compatible DNS and TLS configuration from the provider.
• Region-specific Endpoint (optional) - an endpoint template containing the literal {region-code} placeholder, for example s3.{region-code}.wasabisys.com. TntDrive obtains the bucket region and substitutes it into the template. Leave this field empty when the provider uses a single endpoint or does not support the Amazon S3 GetBucketLocation operation.

Amazon S3 compatibility does not mean that every Amazon S3 operation or option is supported. If requests fail, verify the REST Endpoint, SSL/TLS setting, Signature Version, Addressing Model, region-specific endpoint, and access permissions against your provider's documentation.