storage & assets

Connect your own storage

Add an S3-compatible bucket, validate least-privilege credentials, and make it the default write destination.

15 minutes

Intermediate

Workspace owners

Remote execution

What You Will Finish With

New Postward assets write to your validated bucket while existing assets keep their original storage identity.

1
Create a dedicated key
Grant only ListBucket, GetObject, PutObject, DeleteObject, and AbortMultipartUpload for the selected bucket and prefix.
2
Open Workspace → Storage
Choose the matching provider or Generic S3, then enter endpoint, region, bucket, optional prefix, and credentials.
3
Validate before saving
Postward performs a temporary write/read/delete probe. Fix endpoint, path-style, or policy errors before continuing.
4
Set the default write storage
Make the new ACTIVE storage the default. This affects future uploads only; Postward does not silently move existing bytes.
5
Verify safely
Confirm the sanitized configuration. The secret key is encrypted and is never returned by Postward.

Where to go next

Part of Build with Postward and Scale content production. Finish the journey in order for the full picture.

Ask my agent

Copy a ready prompt for this tutorial and paste it into any agent connected to Postward.

Preview the prompt

Follow the Postward tutorial "Connect your own storage".

Outcome: New Postward assets write to your validated bucket while existing assets keep their original storage identity.
Prerequisites to verify first: OWNER or ADMIN role; An S3-compatible bucket; A dedicated least-privilege access key.

Steps:
1. Create a dedicated key: Grant only ListBucket, GetObject, PutObject, DeleteObject, and AbortMultipartUpload for the selected bucket and prefix.
2. Open Workspace → Storage: Choose the matching provider or Generic S3, then enter endpoint, region, bucket, optional prefix, and credentials.
3. Validate before saving: Postward performs a temporary write/read/delete probe. Fix endpoint, path-style, or policy errors before continuing.
4. Set the default write storage: Make the new ACTIVE storage the default. This affects future uploads only; Postward does not silently move existing bytes.
5. Verify safely: Confirm the sanitized configuration. The secret key is encrypted and is never returned by Postward.

First inspect my environment and existing configuration, and verify each prerequisite before acting.
Follow the current Postward documentation rather than assuming tool names.
Do not replace unrelated configuration.
Verify the result and report exactly what changed.

Prerequisites

OWNER or ADMIN role
An S3-compatible bucket
A dedicated least-privilege access key

Works With

Wasabi
Amazon S3
Cloudflare R2
MinIO
Backblaze B2 S3