Object Storage
What this screen is for
The Object Storage tab registers the buckets Fenwave uses — AWS S3 or GCS. Once a connection is registered here, it becomes available in the platform’s Object Storage area.
Before you start
| To do this | You need |
|---|---|
| See the tab | platform-settings.storage.read |
| Add a connection | platform-settings.storage.create |
| Edit one | platform-settings.storage.update |
| Delete one | platform-settings.storage.delete |
Register the matching cloud credential first where the connection authenticates through it.
Opening it
- Settings › Infrastructure
- Select the Object Storage tab.
The interface
📸 Screenshot Placeholder: The Object Storage tab with one S3 connection. Mark: (1) Add button, (2) the provider column showing AWS S3, (3) the status, (4) the test action, (5) the delete action.
| # | Control | What it does | When you’d use it |
|---|---|---|---|
| 1 | Add | Opens the connection dialog | Registering a bucket |
| 2 | Provider | AWS S3 or GCS | Identifying the connection |
| 3 | Status | Whether the connection is currently working | Triage |
| 4 | Test | Checks the connection now | After credentials change |
| 5 | Delete | Removes the connection | Decommissioning |
Deleting a connection removes Fenwave’s record of it. It does not delete the bucket or anything in it.
Walkthroughs
Register an S3 bucket
Requires platform-settings.storage.create.
- Settings › Infrastructure › Object Storage, click Add.
- Choose AWS S3.
- Supply the bucket and its credentials.
- Save, then test the connection.
- Confirm the status reflects a working connection before relying on it.
Register a GCS bucket
Same flow, choosing GCS.
Remove a connection
Requires platform-settings.storage.delete.
Check what uses it first. Removing the connection does not warn you about anything depending on it.
Scenario
Storage syncs started failing after a credential rotation.
- Settings › Infrastructure › Object Storage — read the status of the connection.
- If it reports a failure, test it to get the current error.
- The usual cause is that the underlying cloud credential was rotated and this connection still carries the old secret. Check the Cloud tab as well.
- Update the credentials on the connection, save, and test again.
- Re-run the sync.
Rotating a cloud credential does not automatically update a storage connection that carries its own copy. Check both places after any rotation — this is the same lesson as clusters, and it catches people the same way.
When it doesn’t work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| Connection fails, nothing was changed | Credentials rotated or expired | Test the connection | Update the credentials and test |
| Bucket not offered in the Object Storage area | Not registered, or the connection is failing | This tab | Register it; fix the status |
| Test fails with a permission error | The credential lacks access to that bucket | The error from the test | Grant bucket access on the cloud side |
| Connection deleted by mistake | The record is removed; the bucket is untouched | — | Register it again |
| Cannot add a connection | Missing platform-settings.storage.create |
Access Explorer | Ask for a role granting it |