Lucidscale can be used to import cloud infrastructure data from Google Cloud. For a comprehensive list of the supported resources and lines from Google Cloud that are available in Lucidscale read this article.
For instructions on importing cloud infrastructure data from Google Cloud and using it to generate diagrams in Lucidscale, refer to our Import and manage Google Cloud infrastructure data in Lucidscale article.
Supported resources
Lucid provides automated diagramming for the following Google Cloud resources. These resources are referred to as “mapped resources” within Lucid editors.
Analytics
- BigQuery Datasets
Compute
- Autoscalers
- Cloud Functions
- Compute Instances
- GKE Clusters (Google Kubernetes Engine)
- Instance Groups
- Node Pools
Database
-
Bigtable Instances
- clusters, backups, tables, app profiles imported as associated metadata
- SQL Instances
Networking
- Cloud Routers
- Firewall Rules
-
Interconnects
- Dedicated Interconnect, Partner Interconnect
-
Managed Zones
- Cloud DNS
- NAT Gateways
-
Networks
- VPC networks, VPC peering connections, Shared VPC host/service project relationships
- Routes
- Subnetworks
-
VPN Gateways
- VPN gateways, tunnels, interfaces
Organization
- Projects
Storage
-
Buckets
- Cloud Storage buckets
- Persistent Disks
Additional imported resource metadata, also known as unmapped resources, are available in your Cloud Inventory for manual placement.
Supported lines
We can draw lines between resources that explicitly reference another in the metadata:
- Instance → Subnetwork
- Network → Network (VPC Network Peerings)
- Host Project → Service Project (Shared VPC)
Note: Lines are only shown for individual resources that are visible on the canvas. Hiding, filtering, or summarizing resources will hide their lines until both connected resources are fully visible again.