By default your organization's media is kept in Natiq's platform storage. A storage profile points Natiq at a bucket you own, so new uploads land there instead. One profile is in use at a time.
Before you start
You need admin:write to add, change or delete profiles; with admin:read you can see the Storage tab. Have ready the bucket name, its region and either an access key pair or the name of a key that's configured on the server side.
The Storage tab
Open Settings → Storage. At the top, a card for the platform storage shows an In use tag when it's what your organization uses. If it isn't configured for the environment, the card says "Platform storage is not configured, so uploads need a profile of your own."
Below it is the table of your own profiles. Each row shows the profile Name, its type, bucket and region, whether Keys are Stored, come from the Server (with a reference) or are None, and the Largest upload. Tags show In use and Disabled.
Add a profile
- 1Test connection
Select New profile. If you have none yet, the empty state says "Add one to keep this organization's media in your own bucket."
Name the profile where it says Name this profile….
Under Bucket, choose the type — S3, R2 or MINIO — then enter the Bucket name and Region.
Under Access keys, enter the Access key ID and Secret access key. Enter both, or leave both empty — if you leave them empty, you must give a server-side key reference (step 6).
Under Limits, optionally set Largest upload in MB. Leave it empty to use the platform limit. By default it can't exceed 16 MB.
Select Add endpoint, CDN, or server-side keys for the rest, if you need them:
- Endpoint URL — only for S3-compatible providers. It must be
https;httpis allowed for MinIO. - Public base URL — a CDN or custom domain that serves the objects. Leave it empty to use the bucket URL.
- Server-side key reference — names an environment variable pair on the server instead of storing keys here.
- Endpoint URL — only for S3-compatible providers. It must be
Leave Profile is enabled ticked. To check the credentials first, select Test connection in the drawer footer. Then select Create profile.
The profile is verified against the provider as it's saved: Natiq writes and removes a test file, and a bucket that doesn't work isn't saved. The failure appears on the form. If your bucket can't be reached from where Natiq runs but you know it's right, the form offers Save without testing. If it's your first profile and it's enabled, it becomes the one in use.
Keys are shown once
Keys are stored encrypted and are never shown again after saving. When you edit a profile, leave both key fields empty to keep the stored pair, or enter a new pair to replace it.
Test, switch and remove
| Action | What it does |
|---|---|
| Test connection | Writes and removes a test file. On success: "Connected. Wrote and removed a test file in" your bucket. |
| Use this one | Makes an enabled profile the one in use. Only one is in use at a time. |
| Use platform storage | On the platform card, while one of your profiles is in use: puts new uploads back on platform storage. |
| Edit | Opens the drawer to change a profile. |
| The bin icon | Deletes it, after a confirmation. |
You can't disable the profile that's in use. Switch to another profile first. Deleting a profile leaves files already uploaded to it where they are. Deleting the one in use moves new uploads to platform storage — the confirmation says so.