Eternet Portal Documentation

Cloud Network

Resource view

The Network route loads the virtual-network group from the authenticated Cloud API and presents it in the cloud management dashboard.

Operational boundary

The current evidence confirms resource listing and presentation. Network changes should only be described as supported when the corresponding workspace action and Cloud API operation have been verified. API failures can result in an empty resource group.

Network resource workflow

The Cloud Network route requests the virtual-network group from the shared Cloud API loader and passes it to a management dashboard. The purpose of this view is to give operators a place to review network resources and understand their relationship to other cloud workloads. The API endpoint currently used for the group is the Eternet Cloud VPC list operation. Depending on what the service returns, records may include identifiers, names, state, region, address ranges, or links to dependent resources. The portal should display only fields that are actually present and should retain the service’s identifiers so a network can be traced to its authoritative record.

Virtual networks are foundational infrastructure. A network can define address space and connectivity boundaries for virtual machines, storage, and cluster workloads, but the exact behavior depends on the Cloud provider’s implementation. A portal row does not prove that routing, firewall rules, DNS, peering, or public access are configured. Those details require separate authoritative records and should only be described if the relevant API or linked resource is available. Similarly, a read-only list should not be presented as a complete network administration console.

Connectivity and safety considerations

The cloud loader calls the fixed Cloud API using the authenticated user’s server-side bearer token. Missing session state, unavailable configuration, upstream errors, or unexpected response shapes can result in empty data. Before assuming that no VPCs exist, confirm the session, service base, endpoint response, and permissions for the account. A robust operational review also checks pagination and whether the API applies user-level or organization-level filtering. Network changes can interrupt services or expose resources, so mutation operations should include clear scope, validation, and confirmation.

When a customer reports that a workload cannot communicate, use the Network view as an inventory starting point, then verify the actual network membership and policy in the Cloud service. Trace the resource identifier across the relevant APIs, check address and route conflicts, and confirm any security controls. The portal cannot diagnose a path that its API does not expose.

Customer value and honest scope

Network inventory alongside compute and storage can help customers connect infrastructure components in a single workspace. This is useful for discovery, support handoffs, and understanding which virtual networks are represented in the account. In a presentation, show a known VPC and identify the fields sourced from the Cloud API. Be clear whether the current interface offers viewing or actual management. The backend Cloud API and provider are authoritative for state and changes; the portal is the authenticated user experience layered over those systems.