Docs

Object Storage

What this screen is for

Object Storage browses the S3 and GCS buckets registered on your platform: navigate folders, upload and download objects, move and delete them, and track the syncs that copy data between locations.

It is a root-level sidebar item rather than living under Deploy, because storage outlives any one deployment.

Before you start

To do this You need
Open the area the Object Storage read permission

A connection must be registered in Settings › Infrastructure › Object Storage. With none, there is nothing to browse.

Opening it

  1. Object Storage in the sidebar.

Direct URL: /object-storage

The interface

📸 Screenshot Placeholder: The object browser inside a connection. Mark: (1) the connection cards, (2) the Browse and Syncs tabs, (3) the breadcrumb path, (4) Upload, (5) New folder, (6) an object’s detail drawer.

# Control What it does When you’d use it
1 Connection cards The registered buckets Choosing which to open
2 Browse / Syncs tabs Objects, or the sync jobs against this connection Browsing vs. transferring
3 Breadcrumb Where you are in the prefix hierarchy Navigating back up
4 Upload Adds an object at the current prefix Putting something in
5 New folder Creates a prefix Organising
6 Detail drawer One object’s metadata Checking size, type, timestamps

Object storage has no real folders — a “folder” is a prefix. Creating one and leaving it empty may not persist, which is not a bug so much as how the underlying storage works.

Walkthroughs

Browse a bucket

  1. Object Storage, choose the connection.
  2. Stay on Browse and navigate using the breadcrumb and folder entries.
  3. Select an object to open its detail drawer.

Upload an object

  1. Navigate to the prefix you want it under — upload targets the current location, and there is no “move to correct place” prompt afterwards.
  2. Upload, choose the file.

Move or delete

Use the move and delete actions. Delete asks for confirmation. Deleting from object storage is not recoverable through Fenwave — whether it is recoverable at all depends on versioning configured on the bucket itself, outside this platform.

Track a sync

Switch to the Syncs tab to see sync jobs against this connection and how they ended.

Scenario

A sync has not produced the files someone expects.

  1. Object Storage, open the connection, go to the Syncs tab.
  2. Find the run. If it failed, the failure names the cause and you are done.
  3. If it reports success but the files are absent, check you are looking at the right prefix on the Browse tab. A sync writing to a different prefix than the one someone is checking is the most common version of this report.
  4. If the connection itself is failing, go to Settings › Infrastructure › Object Storage and test it. Credentials rotated on the cloud side do not update a stored connection.
  5. Check the bucket permissions on the cloud side. A credential valid for the connection may still lack write access to that specific prefix, which presents as a success with nothing written.

When it doesn’t work

Symptom Cause How to check Fix
Object Storage is not in the sidebar Missing the Object Storage read permission Access Explorer Ask for a role granting it
No connections shown None registered Settings › Infrastructure › Object Storage Register one
A connection fails to open Credentials rotated or expired Test it in Settings Update the credentials
An empty folder disappeared Folders are prefixes, not real objects — Expected behaviour of object storage
Uploaded to the wrong place Upload targets the current prefix The breadcrumb Move it; navigate first next time
Deleted something needed Deletion is not recoverable through Fenwave Bucket versioning on the cloud side Recover there if versioning is enabled
Sync reports success, no files Wrong prefix, or the credential lacks write access to it The Browse tab, then cloud-side permissions Check the prefix; grant bucket access

Next