Eternet Portal Documentation

Cloud Storage

Resource types

The storage workspace is backed by the Cloud API data layer, which can retrieve block-storage and object-storage resources. The Storage route selects the object-storage group for its current workspace.

Availability

Data is fetched server-side with the authenticated session. When the Cloud API is not configured, the user is not signed in, or an upstream request fails, the loader may return no resource rows. A blank list should be checked against API/service availability before assuming that no resources exist.

Current scope

Describe only the operations exposed in the loaded workspace; do not infer create, delete, billing, or provisioning capabilities from resource visibility alone.

Storage resource visibility

The Cloud Storage route selects the object-storage group from the shared cloud loader. That loader also knows how to request block-storage records, so the portal’s Cloud layer recognizes more than one storage category even though this route’s current workspace is focused on object storage. The page is intended to present resources returned for the authenticated account. It does not infer that a resource is healthy or usable solely because a record exists; status, capacity, region, and other properties must come from the actual response fields.

For customers, object storage is commonly used for durable objects such as exports, media, backups, or application files, while block storage provides attachable volumes for compute workloads. The portal should only describe the specific type returned by the connected API and should not imply that these resources share the same performance, durability, or billing model. Those service characteristics are defined by the Cloud product and its API, not by the portal presentation. If a customer needs a new bucket, volume, resize, deletion, or access-policy change, confirm that the current page and API provide that operation before promising it.

Reading the page accurately

The server-side data loader obtains a Cloud service base and the current session, then sends an authenticated request. It normalizes common response wrappers such as data, results, or items into a list. If there is no session or service base, if the request returns an error, or if parsing fails, the loader may return an empty array. Therefore, an empty resource table is ambiguous: it could mean there are no resources, or it could mean the service could not be reached. A production support workflow should expose an explicit connection/error state so these cases are distinguishable.

When reviewing an individual storage record, confirm its stable identifier, type, status, location, and relationship to a workload using the actual response. Capacity values should be interpreted with units and timestamps. A static frontend label or sample value must not be presented as live account usage. Changes to storage can affect workload availability and can be difficult to reverse, so operational controls should make scope and consequences explicit.

Customer value and demonstration

A unified storage view can help customers relate cloud capacity to the devices, analytics, and video workloads managed elsewhere in the portal. It can reduce the need to switch between separate consoles for basic inventory review. For a trustworthy demonstration, use an authenticated account with known object-storage resources, compare the displayed identifiers to the Cloud API response, and explain which actions are actually available. If demonstrating only read access, say so directly. The portal is a presentation and control surface; the Cloud API remains responsible for authorization, persistence, provisioning, and authoritative resource state.