Cloud accounts
Connect as many AWS accounts as you run — inventory, spend and alarms are read across all of them; GCP and Azure store one account each for the gateway readers
AWS
Regions, credentials (default chain, access keys, or an assumed role), the member-account role, and the thresholds that raise an anomaly.
One connection reaches every member account of one organization. A separate org, or a standalone account, is a second connection — add as many as you have.
The credential is only half of it:Finish setup & testshows the ARN your role must trust, the metric-stream endpoint and key, and probes what the credential can actually do.
Google Cloud
Project, service-account key or workload identity, and the regions to read. Apigee is also readable as an API gateway.
Microsoft Azure
Subscription, directory tenant, app registration credentials, and the resource groups to read. Azure API Management is also readable as an API gateway.
AWS connections
The credentials this organization has saved — one per AWS organization or standalone account. Each is probed for what it can actually read
No matching results
Linked accounts
Every AWS account the saved credentials reach, across all connections, plus any managed cloud gateway in use
No matching results
Streamed resources
Everything the CloudWatch metric stream has described — one row per resource, across every service you selected
No matching results
