Cloud accounts
The account and subscription register, the links that attach them, and why a cloud instance does not appear here.
A row in the register is an account, a subscription or a project — the provider's unit of billing and permission. A cloud instance does not appear here: it has an operating system and a name, it is patched on the OS vendor's cycle, so it is a server and it belongs in the server list.
The columns
| Column | What it says |
|---|---|
| Account name | The name the organization gives the account |
| Account id | The identifier the provider issues — an account number, a GUID, a project id |
| Provider | AWS, Azure, Google Cloud… |
| Deployment | Public · Private · Hybrid |
| Regions | The provider regions the account operates in, as separate chips |
| Environment | Production, test, development — as the organization marks it |
| Connectivity | Direct Connect · ExpressRoute · Cloud Interconnect · VPN · Disconnected |
| Status | The five status values shared across infrastructure |
| Owner | Who is responsible for the account |
| Servers | How many servers in the inventory belong to the account |
| Links | How many links attach it |
The Links column is not in the default set. It is added through the column picker, and it is always in the export.
The identifier the provider issues is part of the record's identity; the name is not. Renaming the account does not create a new record and does not break its history. The identifier itself has no quick filter — one distinct value per row is not a filter.
The first four connectivity values are AWS, Azure and Google product names, so they are written in the provider's own spelling and are identical in both languages. Only "Disconnected" is the product's own word — a statement that there is no circuit at all, which nobody sells — so only it is translated.
Provider, never Vendor: a cloud has a provider, a chassis has a vendor.
The link
A cloud is attached through a real circuit, and its physical end is a router or firewall already recorded in the equipment register. That is what makes the link a node on the map rather than a decoration: the Terminates on edge connects it to an existing record.
| Link field | What it says |
|---|---|
| Kind | Direct Connect · ExpressRoute · VPN · MPLS |
| Circuit id | The provider's identifier for the circuit. Part of the record's identity |
| Cloud account | The account the link attaches |
| Bandwidth | In Mbps |
| Terminates on | The router or firewall in the equipment register the link lands on |
| Site | Where the link lands |
| Status | The five status values shared across infrastructure |
A link has no screen of its own. It is recorded on the cloud account it attaches and renders inside the account card, exactly as a network interface renders inside a server card.
No inventory source discovers a cloud account, so every value in this register is recorded on the card. The product makes no outbound call to a cloud provider's interface at runtime.
Updated
This page is the file content/docs/en/v1/infra/cloud.mdx