Skip to main content

Discovering your cloud infrastructure

This step is optional, and only worth doing if your app is hosted in the cloud. It lives on the Infrastructure tab of Discovery, alongside reviewing what it finds.

If your app runs in the cloud, three actions appear in the page header, next to "Map code":

  • "Discover infra": starts a scan (a "census") of your connected cloud account for resources.
  • "Configure scope": opens the scope editor for the current provider so you can review or change what gets scanned.
  • "Investigate": cross-references your confirmed inventory against your mapped code to produce a written Infra Map.

If you click "Discover infra" or "Investigate" without a cloud account connected at all, you get an error banner: "Connect a cloud provider (AWS/GCP/Azure) before an infra census (Settings → Integrations)." Connecting the account itself happens on the Integrations page, not here.

Configure scope​

Clicking "Discover infra" for the first time (before any scan scope has been saved) automatically opens the scope panel instead of starting a scan, titled Configure infra discovery scope — <PROVIDER>. Clicking "Configure scope" directly opens the same panel pre-filled with your existing settings, titled Edit infra discovery scope — <PROVIDER>.

The panel has exactly two fields:

  • Regions (required): a comma-separated list of regions to scan, for example us-east-1, us-west-2 for AWS, us-central1, europe-west1 for GCP, or eastus, westeurope for Azure (the placeholder text adapts to your connected provider).
  • Scope patterns (optional): comma-separated resource-name prefixes to include, for example prod-, ace-, myapp-. The field explains: "Resource name prefixes to include — leave blank to scan everything in the regions above."

The save button reads "Save & start infra census" the first time, or "Save changes & re-run infra census" when editing. Either way, saving immediately kicks off a new infra scan. There is also a Cancel link and an "✕" to dismiss without saving.

Discover infra​

Once scope is configured, "Discover infra" runs a scan across your configured regions and writes back a list of resources as candidate or confirmed facts on the Infrastructure tab. See Reviewing discovered resources for how to work through them. While it runs, the usual run card shows its progress.

What does Investigate do?​

"Investigate" requires that an infra census has already completed successfully for the provider in question; if not, you will see an error telling you to run a census first. When it succeeds, it:

  • Produces the Infra Map: a written document plus a diagram of your infrastructure topology, shown at the top of the Infrastructure tab.
  • Can add new candidate resources it inferred and annotate existing ones, and can add new relationship edges (visible on the Architecture tab and in the Relationships panel on this tab).

What's in the Infra Map panel?​

Until Investigate has run at least once, this panel shows "No Infra Map generated yet" with the hint "Run 'Investigate' after mapping the codebase and completing an infrastructure census. The resulting Markdown and Mermaid map will appear here."

Once available, the panel shows a green "Available" tag, a Refresh button, a collapse and expand toggle, a "View run" link that jumps to that Investigate run's log, and a footer with the source path (discovery/infra-map.md) and the generation timestamp.

Who can do this?​

Requires discovery:manage (and a mutable project) to run any of these three actions or save scope; discovery:read is enough to view an existing Infra Map, inventory, or relationships.

On this page