Cloud Resources

Most "on-prem" networks are not, entirely. The cloud module inventories what you run at cloud and interconnect providers next to what you run in your own racks.

What it covers

Add an account per provider and vConfig collects the resources that matter to a network team — instances, networks, load balancers, DNS records, storage, and the interconnect circuits that reach back to your own network — alongside the billing data for each.

Adding an account

Cloud Resources → accounts → add. Each provider needs its own read-only API credential. Grant read-only access: the module inventories and reports, it does not provision.

Billing

Billing is collected per account and reported in the currency the bill is actually issued in. vConfig reads the currency from the bill rather than assuming one per provider — a provider's overseas edition billed through a local reseller really can invoice in a different currency from its home market, and hard-coding that mapping produces confidently wrong totals.

For providers that export billing to a data warehouse, the export target (project and table) is configured per account rather than being assumed to live in the same project as the resources.

SDKs

Provider SDKs are declared as dependencies and installed on demand. If a provider's SDK is missing, the module reports which package is needed instead of failing silently.