Cloud Account

On the [Settings > Cloud Account] page (/settings/cloud-account), you can connect cloud service provider accounts and manage their credentials, collection status, and access configurations.

Metric Cards

Four summary cards are displayed at the top of the page:

CardDescription
Registered AccountsRegistered out of contracted, as registered / contracted. Counted on a General-account basis — Root accounts are excluded and shown separately underneath
Not RegisteredContracted accounts not yet registered. Clicking the card opens the Not Registered Accounts dialog
Credential IssuesAccounts whose stored credentials no longer work, split into Invalid and Expired counts. Update the credentials to restore API access
Collection IssuesAccounts whose latest collection did not finish, split into Failure and Canceled counts

Viewing Cloud Accounts

Accounts are displayed in a paginated table. Use the tab bar above the table to filter by account scope:

TabDescription
All AccountsEvery registered cloud account
Root AccountParent accounts that manage permissions
General AccountsWorkload accounts (Direct or Delegated)

Each tab shows a badge with the current count.

Table Columns

ColumnDescription
NameAccount display name (alias)
Cloud Account IDProvider-specific identifier — AWS Account ID, Azure Subscription ID, or Google Cloud Project ID
ProviderCloud service provider (AWS, Azure, Google Cloud, NCP)
Access TypeRoot Account, Delegated, or Direct
Credential StatusCurrent credential validity — Valid, Invalid, Expired, or Unknown
Collection StatusLatest collection result — Pending, Running, Success, Failure, or Canceled
Last CollectedTimestamp of the most recent successful collection
ℹ️
Some columns are hidden depending on the active tab. The Root Account tab hides Access Type, Collection Status, and Last Collected; the All Accounts tab hides Collection Status and Last Collected.

Click any row to navigate to the account’s detail page.

Search and Filters

UI ElementDescription
SearchSearch by Name, Cloud Account ID... — matches on account name or Cloud Account ID
Filter (funnel icon)Opens the filter popover with Provider, Credential Status, and Collection Status tabs
More menu (⋮)Additional options: Set Display (page size, column visibility, order, and pinning), Refresh
ExportDownloads the accounts matching the current tab, search, and filters as an Excel or CSV file

Provider is no longer a standalone toolbar dropdown — it is now a tab inside the Filter popover. Any filter tab can be pinned (★) to the toolbar as a quick filter, so a pinned Provider, Credential Status, or Collection Status dropdown appears directly in the toolbar next to Search.

Column pinning

⋮ > Set Display also lets you pin up to 2 columns to the left so they stay visible while you scroll the table horizontally. Name is pinned by default. The layout is kept in your browser, and narrowing the list — a new search, filter, or tab — returns you to page 1.

Exporting the list

Click Export and choose Excel or CSV. The file is built from the list as you see it — the active tab, search, and filters are applied, and it contains the columns visible in Set Display in the same order, for every matching account rather than just the current page. The download starts automatically when the file is ready; if the server refuses the export (row limit, file too large, timeout), an error toast says why instead of leaving you waiting.

Filter Popover

Click [Filter] to open the filter popover. It has three tabs, and each tab has a ★ pin toggle that adds that filter to the toolbar as a quick filter:

TabDescription
ProviderFilter by cloud provider — AWS, Azure, Google Cloud, NCP. Supports multi-select
Credential StatusFilter by credential validity — All, Valid, Invalid, Expired, Unknown
Collection StatusFilter by collection result — All, Pending, Running, Success, Failure, Canceled

Provider is the tab the popover opens on, and it supports multi-select — the screenshot above shows it with AWS, GCP, Azure, and NCP listed.

ℹ️
The Collection Status tab shows the note “Root accounts have no collection status” — this filter applies to General accounts only.

Tab Filtering

Use the tab bar to filter accounts by scope. Each tab displays a count badge:

Account Detail

Clicking a row opens the detail page for that account. The header displays the account name, provider badge, access type badge, and creation date.

Two actions sit in the top-right corner:

ActionEffect
Collect ResourcesRuns a resource collection for this account immediately, instead of waiting for the next scheduled run
DisconnectRemoves the account from CloudOps
ℹ️
Collect Resources appears on General accounts only. Root accounts are not collection targets themselves — they delegate to the General accounts attached to them, so there is nothing to collect at the Root level.

How the collection runs

Pressing Collect Resources starts the resource stage of Flow Studio rather than a standalone job. The button reports only that the request was acceptedResource collection started. — because a stage run answers with a run handle, not a per-account result.

The outcome therefore shows up in two places instead of a toast:

WhereWhat it tells you
Collection Status on this pagePending → Running → Success / Failure / Canceled
The run in Flow StudioThe step-by-step detail of that execution

While the request is in flight the button stays disabled and says why:

StateMessage
Accepted, not yet startedCollection request accepted. Starting shortly.
QueuedCollection is queued for this account.
Already runningCollection is already in progress for this account.
Run definition unavailableCouldn't load the run definition. Click to try again. — the button is not locked in this state; pressing it reloads the definition
ℹ️
Collection request accepted. Starting shortly. is a distinct state from already running — the server has taken the request but has not recorded the start yet. Without it the button would look pressable again for a moment, and a second press would do nothing visible.

The in-progress state comes from what the server records for the account, so it clears on its own once the run ends — you never need to reload the page to get the button back. A request that arrives while a previous run is still wrapping up is answered with already in progress and is not an error.

Detail Metric Cards

Three metric cards summarize the account’s health:

CardDescription
Credential & IAM StatusCurrent validity of credentials and IAM permissions
Collection StatusLatest resource collection status across all resource types
Cost SummaryMonth-to-date cost with trend comparison against the previous month
ℹ️
On Root Account detail pages, the middle card is Attached General Accounts (“Delegated through this Root”) instead of Collection Status, because Root accounts are not collection targets. Non-Root accounts still show Collection Status.

Basic Info

The Basic Info card shows account properties. Account Name and Description support inline editing — click the edit icon, modify the value, and save.

FieldEditableDescription
Account NameYesDisplay name for the account
DescriptionYesFree-text description of the account’s purpose
Cloud Account IDNoProvider-specific account identifier
ProviderNoAWS, Azure, Google Cloud, or NCP
Access TypeNoRoot Account, Delegated, or Direct
ManagerNoAssigned account manager
TagsNoApplied tags displayed as badges
Created by / Updated byNoWho connected the account and who last changed it
ℹ️
Accounts created automatically — for example the General account CloudOps derives from a connected Root — carry an Auto badge in the list, so a machine-made entry is not mistaken for one somebody registered by hand.

Linked Root Account

General accounts display a Linked Root Account field showing how the account connects:

StateMeaning
DelegatedAccess is delegated through the linked Root Account
DirectThe account connects directly with its own credentials
Not linkedNo Root Account is linked

Click [Edit] to open the Edit Linked Root Account dialog, where you can change the delegated Root Account or switch to Direct. Switching to Direct re-issues the account’s credentials.

Credentials

The Credentials card displays the secret schema type and masked credential fields. Click [Update Credentials] to replace the stored credentials with new values.

ℹ️
Credential update is currently supported only for AWS accounts. For Azure and Google Cloud accounts, contact your administrator.

Attached General Accounts

For Root Account type accounts, an additional Attached General Accounts section appears below the Credentials card. It lists all general accounts linked to this root account in a searchable, filterable table.

ColumnDescription
NameGeneral account display name
Cloud Account IDProvider-specific identifier
ProviderCloud service provider
Access TypeDelegated or Direct
Credential StatusCredential validity of the attached account
Collection StatusLatest collection result of the attached account

Connecting an Account

Click [+ Connect Account ▾] and choose an account type

Click the [+ Connect Account ▾] dropdown at the top right of the list page and choose Connect Root Account (under the Root Account section) or Connect General Account (under the General Account section). The account type is chosen here, before the wizard — not inside it.

Select a Provider

Choose the cloud service provider. The stepper shows 4 steps: Provider → Account Info → Verify → Save.

Which providers appear here depends on the account type you picked in the previous step — see Supported account structures below.

Configure Account Info

Enter the Account ID, Account Name, and Description. For Root Accounts, configure credentials directly. For General Accounts, select a connection method (Delegated or Direct).

Verify and Save

Review the configuration, verify the connection, and save the account. It will appear in the account list once registration completes.

Supported account structures

Not every provider supports every account structure, and the wizard only offers the combinations that actually exist.

ProviderRoot AccountGeneral · DirectGeneral · Delegated
AWS
Azure
Google Cloud
NCP
ℹ️
This is why the provider list differs between the two entry points. Connect Root Account lists only providers that support a root account, so NCP does not appear there. Connect General Account lists all four, and once NCP is selected the Delegated connection method is hidden — NCP has no cross-account delegation equivalent.

Bulk Register

Bulk Register is a menu item inside the [+ Connect Account ▾] dropdown (under the General Account section) that opens /settings/cloud-account/bulk. Use it to register multiple Delegated General Accounts at once based on a selected Root Account. The wizard guides you through 5 steps.

Select Root Account

Choose the Root Account that serves as the delegation basis. The selected Root Account’s provider automatically determines the candidate list and credential fields.

The five steps sit on one page as a stack of sections rather than separate screens, and the Progress panel on the right tracks which of them are Done, In progress, or Not started. Get ready before you start beside it lists what to have on hand — a registered Root Account, a pre-created IAM Role name and External ID, and the list of contracted accounts — with a link to the setup guide.

Pick a CSP first to narrow the Root Account list to one provider; the default All shows every Root Account, as before. The filter only appears when your Root Accounts span more than one provider.

⚠️
Changing the CSP after you have chosen a Root Account clears that choice and the credentials you entered, because each provider has its own credential fields.

Click the dropdown to search and select a Root Account from the list.

ℹ️
If only one Root Account is registered, it is automatically selected.

Select Target Accounts

Browse and select the Delegated General Accounts to register. Accounts are listed with their availability status — only Selectable accounts can be checked.

Use the checkboxes to select individual accounts or use the header checkbox to select all on the current page. The status filter dropdown lets you narrow the list:

FilterDescription
All StatusesShow all candidate accounts
SelectableAccounts available for registration (default)
DuplicateAccounts already registered

ℹ️
You can select up to 100 accounts at a time. If the selectable count exceeds 100, narrow the results using search or filters.

Configure Credentials

Enter the credential details that will be applied identically to all selected accounts. For AWS, provide the Role Name and External ID.

FieldDescription
Role NameThe IAM Role name (the part after role/ in the Role ARN). CloudOps does not auto-create the role — you must pre-create it in AWS
External IDThe External ID configured in the IAM Role’s trust policy for assume-role

⚠️
CloudOps does not auto-create the AWS Role. You must pre-create the Role in each target account before proceeding. The Role Name and External ID are applied identically to all selected accounts.

Validation

CloudOps runs a connection test (STS AssumeRole) for each selected account. The result shows Passed or Failed with a reason for each account.

StatusDescription
PassedConnection test succeeded — the account will be registered
FailedConnection test failed — the account will not be registered. Check the Reason column for details
ℹ️
Provider, Root Account, credentials, and selection are locked while validation is in progress. Only accounts that pass validation will be registered in the next step.

Result

Review the registration results. A summary shows total selected, success, and failed counts. Use the Success and Failed tabs to inspect individual accounts.

Disconnecting an Account

Open the disconnect dialog

On the account detail page, click the [Disconnect] button in the top-right corner.

Confirm disconnection

Review the warning message, then check the confirmation checkbox: “I understand that this action is permanent and agree to disconnect the account.” Click [Disconnect] to proceed.

⚠️
Disconnecting a cloud account is permanent and cannot be recovered. Data retention for associated resources, costs, and collection history follows the system operation policy.
ℹ️
A Root Account with attached general accounts cannot be disconnected directly. Disconnect the attached general accounts first to proceed.
ℹ️
When no cloud accounts have been registered, the page shows an empty state titled “No Cloud Account Found” with the description “Create a new account to start connecting with a cloud provider.”
v1.7.0