Keep uploaded files in your own S3 compatible bucket, such as Amazon S3 or Cloudflare R2. Files there do not count against your plan's storage, and the largest file limit does not apply.

Overview

Once a bucket is connected, new uploads in Files go to it. The bucket stays private: TekStacks checks who is asking before it hands out any file.

What stays where:

• Files uploaded before you connect stay where they are.
• Documentation attachments and snippets stay in TekStacks storage.
• One bucket serves the whole account. With clients turned on, every client's files go to it.

Supported services: Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Hetzner Object Storage, OVHcloud Object Storage, and Another S3 compatible service such as MinIO.

Requirements

• Role: Admin (Company settings, custom domain and storage).
• A bucket in one of the services above, and an access key that can write, read and delete in it.

Steps

1. Under Administration, open Storage.
2. Under Choose your storage service, click your service.
3. Fill in the form. The fields follow the service, for example Bucket name and Region for Amazon S3, or Bucket name and Account ID for Cloudflare R2.
4. Optionally set Folder to keep TekStacks files in one folder of the bucket, such as tekstacks.
5. Enter the access key and secret, such as Access key ID and Secret access key.
6. Click Check and save.

TekStacks writes, reads and deletes a small test file in the bucket. If that works, the connection is saved and "Connected" appears. If not, nothing is saved and the message says what went wrong.

Need help setting up? below the form has step by step instructions for the chosen service and, where the service uses one, an access policy for the bucket.

Stop using the bucket for new uploads

Click Stop using for new uploads. New uploads go to TekStacks storage again, and files already in the bucket stay readable. Click Use for new uploads to switch back.

Move to another service

Click a different service under Move to another service and enter its details and keys, then Check and save.

Remove the connection

Remove appears once no file versions are stored in the bucket. It deletes the keys from TekStacks and touches nothing in the bucket.

Notes

Note: On the MSP plan, uploaded files must go to your own storage. Snippets and documentation attachments still use TekStacks storage.

Note: A custom endpoint must be an https address on the standard port.

Troubleshooting

"Not saved" with a message after Check and save. The test file could not be written, read or deleted. Check the bucket name, region and keys, and that the key's policy allows writing, reading and deleting in the bucket.

"Enter the keys for" a service. You switched to another service. Enter that service's keys; the old ones do not carry over.

There is no Remove button. Files are still stored in the bucket. The connection stays so they remain readable.

"The endpoint must be an https address on the standard port." For Another S3 compatible service, enter an https:// endpoint on the standard port (443).