How sources are chosen
During opscanvas setup, OpsCanvas asks where your repositories are located and which cloud identities you want to use. You confirm every source before anything from it enters your map. You can run setup again at any time to change your choices.
Credentials
OpsCanvas uses the cloud identities you select, in place, on your computer. It reads through the access those identities already have and does not collect, store, or transmit your credentials. In the current release it is read only: it makes no changes to your cloud.
Sources
- AWS: accounts reachable through the AWS identities you select.
- Azure: subscriptions reachable through the Azure identity you select.
- Google Cloud: projects reachable through the Google Cloud identity you select.
- Kubernetes: clusters and contexts from your local Kubernetes configuration.
- Terraform and OpenTofu: state that maps resources to environments and services.
- Repositories: infrastructure as code and CI/CD definitions in the repository locations you give setup.
Application and network context
The graph connects each service to the network it runs in and maps how those networks connect across accounts, regions, and hybrid sites on AWS, Azure, and Google Cloud: VPCs and VNets, Transit Gateway, Direct Connect, ExpressRoute, VPN, peering, and endpoints. Network facts come from Terraform state and from read-only describe calls, so networks built in a console are included. Data transfer spend is broken down by type (internet egress, inter-region, cross-AZ, NAT, and Direct Connect) and attributed to the environment that owns it.
OpsCanvas does not do network performance monitoring, flow analytics, or discovery of on-premises routers, switches, or SD-WAN.