Connect and scan cloud accounts

Before you start

Prepare read-only credentials for the provider you want to connect. Each connection also needs a friendly name and a workspace scope.

AWS

Access key or assume role

GCP

Service account key

Azure

App registration

Vörr also accepts Prometheus and Nagios during the cloud connection flow where applicable.

Add the connection

Choose AWS, Azure or Google Cloud, enter the required read-only credentials and give the account a recognizable name.

Scope the connection to selected workspaces, or leave it available to all workspaces. Credentials are encrypted at rest and secrets are never shown again once saved.

Validate access

Vörr validates the credentials against the provider. Returned credentials are masked in the interface.

Start the scan

Connecting an account does not scan it automatically. Start the scan when you are ready for Vörr to discover and map its supported resources.

The scan reports what it is doing — discovering resources, connecting them up, saving the map, auto-mapping — with a running resource count per region. You can leave the page while it works.

Review scan coverage

Before treating an empty result as proof that no resource exists, check the scan status. Vörr separates:

• A supported resource type that was scanned and found empty
• A resource type that Vörr does not index
• A scan that was incomplete because of access, failure or throttling

Only the first is a trustworthy zero.

Confirm the result

Check that:

• The connection shows Connected.
• The scan completed for the services you expect.
• Access failures or partial coverage are visible.
• Resources appear under the correct account and workspace context.