Datasets:
image imagewidth (px) 4.29k 18.3k | id stringlengths 7 34 | provider stringclasses 3
values | title stringlengths 34 70 | prompt stringlengths 270 516 | graph stringlengths 1.45k 4.29k | annotations stringlengths 2.55k 6.99k | node_count int64 25 56 | render_command stringlengths 90 144 |
|---|---|---|---|---|---|---|---|---|
aws-batch-hpc | aws | AWS Batch HPC architecture diagram | Draw an AWS Batch HPC genomics pipeline: an S3 upload triggering an EventBridge rule and a Step Functions workflow that submits array jobs to AWS Batch compute environments running EC2 Spot instances in private subnets across two availability zones, FSx for Lustre linked to the upload bucket, ECR and CloudWatch Logs in... | {"tv_aws_users.researchers":["aws_s3_bucket.sequencer_uploads"],"aws_s3_bucket.sequencer_uploads":["aws_cloudwatch_event_rule.new_run"],"aws_cloudwatch_event_rule.new_run":["aws_sfn_state_machine.genomics_pipeline"],"aws_sfn_state_machine.genomics_pipeline":["aws_batch_compute_environment.spot~1","aws_batch_compute_env... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-batch-hpc.tvg.json --annotate aws-batch-hpc.annotations.yml
format: '0.3'
title: AWS Batch genomics pipeline on EC2 Spot with FSx for Lustre
update:
aws_vpc.hpc:
cidr_block: 10.60.0.0/16
aws_su... | 29 | terravision draw --source aws-batch-hpc.tvg.json --annotate aws-batch-hpc.annotations.yml --format png | |
aws-data-lake | aws | AWS data lake architecture diagram | Draw an AWS data lake with processing in a VPC across two availability zones: DMS from Aurora MySQL, Glue jobs, EMR Serverless, MWAA and Redshift Serverless in private subnets, an S3 gateway endpoint, and Glue and Secrets Manager interface endpoints in each zone. Kinesis, Firehose and Transfer Family land data in a raw... | {"tv_aws_mobile_client.apps":["aws_kinesis_stream.clickstream"],"tv_aws_users.partner_systems":["aws_transfer_server.partner_sftp"],"tv_aws_users.analysts":["aws_quicksight_data_source.dashboards"],"aws_group.ingestion":["aws_kinesis_stream.clickstream","aws_kinesis_firehose_delivery_stream.clickstream","aws_transfer_s... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-data-lake.tvg.json --annotate aws-data-lake.annotations.yml
format: '0.3'
title: AWS data lake and analytics platform in a VPC
update:
aws_vpc.analytics:
cidr_block: 10.30.0.0/16
aws_subnet.pro... | 44 | terravision draw --source aws-data-lake.tvg.json --annotate aws-data-lake.annotations.yml --format png | |
aws-ecs-fargate-api | aws | Amazon ECS on Fargate API architecture diagram | Draw an Amazon ECS on Fargate API across two availability zones: Route 53 and an Application Load Balancer with AWS WAF in public subnets, API and worker tasks in private subnets, Aurora PostgreSQL and ElastiCache in data subnets, interface endpoints for ECR, SQS and Secrets Manager, an S3 gateway endpoint, an SQS job ... | {"tv_aws_users.api_clients":["aws_route53_zone.api"],"aws_route53_zone.api":["aws_alb.api~1","aws_alb.api~2"],"aws_wafv2_web_acl.api":["aws_alb.api~1","aws_alb.api~2"],"aws_vpc.api":["tv_aws_az.us_east_1a","tv_aws_az.us_east_1b","aws_internet_gateway.igw","aws_vpc_endpoint.s3_gateway"],"tv_aws_az.us_east_1a":["aws_subn... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-ecs-fargate-api.tvg.json --annotate aws-ecs-fargate-api.annotations.yml
format: '0.3'
title: Amazon ECS on Fargate API with Aurora, ElastiCache and an SQS worker
update:
aws_vpc.api:
cidr_block: ... | 44 | terravision draw --source aws-ecs-fargate-api.tvg.json --annotate aws-ecs-fargate-api.annotations.yml --format png | |
aws-eks-karpenter | aws | Amazon EKS with Karpenter architecture diagram | Draw an EKS cluster that uses Karpenter for node autoscaling, across three availability zones: an ALB and NAT gateway in each public subnet; the Karpenter controller, a NodePool of On-Demand and Spot nodes and interface VPC endpoints for ECR, EC2 and SQS in each private subnet; Aurora PostgreSQL in data subnets; an S3 ... | {"tv_aws_users.users":["aws_route53_zone.dns"],"aws_route53_zone.dns":["aws_alb.ingress~1","aws_alb.ingress~2","aws_alb.ingress~3"],"aws_account.eks_control_plane":["aws_eks_service.cluster"],"aws_eks_service.cluster":["tv_karpenter.karpenter~1","tv_karpenter.karpenter~2","tv_karpenter.karpenter~3"],"aws_vpc.main":["tv... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-eks-karpenter.tvg.json --annotate aws-eks-karpenter.annotations.yml
format: '0.3'
title: Amazon EKS with Karpenter autoscaling and private endpoints
update:
aws_vpc.main:
cidr_block: 10.10.0.0/16... | 52 | terravision draw --source aws-eks-karpenter.tvg.json --annotate aws-eks-karpenter.annotations.yml --format png | |
aws-event-driven | aws | AWS event-driven order processing architecture diagram | Draw an AWS event-driven order system with Lambdas in a VPC across two availability zones: mobile clients call an API Gateway REST API with WAF and a Cognito authorizer, a create-order Lambda saves to DynamoDB through a gateway endpoint and queues on SQS, a fulfilment Lambda notifies through SNS, SQS and SNS are reache... | {"tv_aws_mobile_client.mobile_app":["aws_api_gateway_rest_api.orders_api"],"aws_wafv2_web_acl.api_protection":["aws_api_gateway_rest_api.orders_api"],"aws_api_gateway_rest_api.orders_api":["aws_cognito_user_pool.customers","aws_lambda_function.create_order~1","aws_lambda_function.create_order~2"],"aws_vpc.orders":["tv_... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-event-driven.tvg.json --annotate aws-event-driven.annotations.yml
format: '0.3'
title: AWS event-driven order processing with Lambda in a VPC
update:
aws_vpc.orders:
cidr_block: 10.30.0.0/16
aw... | 36 | terravision draw --source aws-event-driven.tvg.json --annotate aws-event-driven.annotations.yml --format png | |
aws-hybrid-direct-connect | aws | AWS Direct Connect hybrid architecture diagram | Draw an AWS hybrid network for a head office: staff, DNS servers, a File Gateway and a router connected by Direct Connect, a transit VIF and a Direct Connect gateway to a Transit Gateway, with a site-to-site VPN as backup, and a VPC across two availability zones with an internal ALB, EC2 app servers, Multi-AZ RDS for O... | {"tv_aws_onprem.head_office":["tv_aws_client.staff","tv_aws_server.dns_servers","aws_storagegateway_gateway.file_gateway","aws_customer_gateway.office_router"],"tv_aws_client.staff":["aws_customer_gateway.office_router"],"aws_storagegateway_gateway.file_gateway":["aws_customer_gateway.office_router"],"aws_customer_gate... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-hybrid-direct-connect.tvg.json --annotate aws-hybrid-direct-connect.annotations.yml
format: '0.3'
title: AWS hybrid workloads over Direct Connect with Route 53 Resolver and Storage Gateway
update:
aw... | 47 | terravision draw --source aws-hybrid-direct-connect.tvg.json --annotate aws-hybrid-direct-connect.annotations.yml --format png | |
aws-iot-telemetry | aws | AWS IoT telemetry architecture diagram | Draw an AWS IoT telemetry platform for a wind farm: turbine sensors and an IoT Greengrass gateway on site publishing to IoT Core, IoT rules routing readings to Kinesis Data Streams, alarms to an IoT Events detector model with SNS alerts, and everything to Firehose and an S3 archive, with Lambda functions in a VPC acros... | {"tv_aws_onprem.wind_farm":["tv_aws_iot_sensor.turbine_sensors","aws_greengrass_group.site_gateway"],"tv_aws_iot_sensor.turbine_sensors":["aws_greengrass_group.site_gateway"],"aws_greengrass_group.site_gateway":["aws_iot_topic_rule.telemetry","aws_iot_topic_rule.archive","aws_iot_topic_rule.alarms"],"aws_group.device_r... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-iot-telemetry.tvg.json --annotate aws-iot-telemetry.annotations.yml
format: '0.3'
title: AWS IoT telemetry with Greengrass, IoT Core rules, Timestream and Grafana
update:
aws_vpc.telemetry:
cidr_... | 32 | terravision draw --source aws-iot-telemetry.tvg.json --annotate aws-iot-telemetry.annotations.yml --format png | |
aws-media-processing | aws | AWS video processing architecture diagram | Draw an AWS video-on-demand platform: creators uploading through presigned URLs from an API Gateway HTTP API with Cognito, an S3 upload bucket archiving masters to Glacier, an EventBridge rule starting a Step Functions workflow with a Lambda probe, MediaConvert, Rekognition moderation, a DynamoDB catalogue and SNS noti... | {"tv_aws_users.creators":["aws_apigatewayv2_api.media","aws_s3_bucket.uploads"],"tv_aws_users.viewers":["aws_route53_zone.video","aws_apigatewayv2_api.media"],"aws_apigatewayv2_api.media":["aws_cognito_user_pool.members","aws_lambda_function.upload_url","aws_lambda_function.catalogue_api"],"aws_lambda_function.upload_u... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-media-processing.tvg.json --annotate aws-media-processing.annotations.yml
format: '0.3'
title: AWS video processing with MediaConvert, Rekognition and CloudFront signed URLs
connect:
tv_aws_users.cre... | 25 | terravision draw --source aws-media-processing.tvg.json --annotate aws-media-processing.annotations.yml --format png | |
aws-multi-account-network | aws | AWS multi-account network with Direct Connect architecture diagram | Draw an AWS multi-account network: a corporate data centre with office staff, an ERP server and a router connected by Direct Connect and a Direct Connect gateway to a Transit Gateway in a network account, with a site-to-site VPN as backup; an inspection VPC with Network Firewall in two availability zones; a central egr... | {"tv_aws_onprem.corporate_datacentre":["tv_aws_client.office_staff","tv_aws_server.erp_system","aws_customer_gateway.datacentre_router"],"tv_aws_client.office_staff":["aws_customer_gateway.datacentre_router"],"aws_customer_gateway.datacentre_router":["aws_dx_connection.primary","aws_vpn_connection.ipsec_vpn","tv_aws_se... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-multi-account-network.tvg.json --annotate aws-multi-account-network.annotations.yml
format: '0.3'
title: AWS multi-account network with Direct Connect, Transit Gateway and central inspection
update:
... | 53 | terravision draw --source aws-multi-account-network.tvg.json --annotate aws-multi-account-network.annotations.yml --format png | |
aws-multi-region | aws | AWS multi-region failover architecture diagram | Draw an AWS active-passive multi-region architecture: Route 53 failover between a primary region and a standby region, each with a VPC across two availability zones, ALBs in public subnets, ECS Fargate services in app subnets, Aurora PostgreSQL in data subnets and a DynamoDB gateway endpoint. Show Aurora Global Databas... | {"tv_aws_users.users":["aws_route53_zone.failover"],"aws_route53_zone.failover":["aws_alb.primary_web~1","aws_alb.primary_web~2","aws_alb.standby_web~1","aws_alb.standby_web~2"],"tv_aws_az.us_east_1a":["aws_subnet.primary_public~1","aws_subnet.primary_app~1","aws_subnet.primary_data~1"],"aws_subnet.primary_public~1":["... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-multi-region.tvg.json --annotate aws-multi-region.annotations.yml
format: '0.3'
title: AWS multi-region active-passive failover
update:
aws_vpc.primary_us_east_1:
cidr_block: 10.40.0.0/16
aws_v... | 44 | terravision draw --source aws-multi-region.tvg.json --annotate aws-multi-region.annotations.yml --format png | |
aws-payments-processing | aws | AWS payments processing architecture diagram | Draw an AWS card payments platform across three availability zones: API Gateway with mutual TLS and AWS WAF, a VPC link to Network Load Balancers, ECS Fargate authorisation and settlement services, Aurora PostgreSQL Multi-AZ with a writer and readers, a DynamoDB idempotency table through a gateway endpoint, an SQS FIFO... | {"tv_aws_users.merchants":["aws_api_gateway_rest_api.payments"],"aws_wafv2_web_acl.payments":["aws_api_gateway_rest_api.payments"],"aws_api_gateway_rest_api.payments":["aws_nlb.payments~1","aws_nlb.payments~2","aws_nlb.payments~3"],"aws_vpc.payments":["tv_aws_az.us_east_1a","tv_aws_az.us_east_1b","tv_aws_az.us_east_1c"... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-payments-processing.tvg.json --annotate aws-payments-processing.annotations.yml
format: '0.3'
title: AWS card payments processing across three availability zones
update:
aws_vpc.payments:
cidr_bl... | 54 | terravision draw --source aws-payments-processing.tvg.json --annotate aws-payments-processing.annotations.yml --format png | |
aws-saas-multi-tenant | aws | AWS SaaS multi-tenant architecture diagram | Draw an AWS multi-tenant SaaS platform: API Gateway HTTP API with a Cognito JWT authorizer and a VPC link to internal ALBs across two availability zones, ECS Fargate services for a pooled tier, a premium silo tenant and tenant management, Aurora PostgreSQL with a schema per tenant plus a dedicated premium cluster, a Dy... | {"tv_aws_users.tenant_users":["aws_apigatewayv2_api.saas"],"tv_aws_users.saas_admins":["aws_apigatewayv2_api.saas"],"aws_apigatewayv2_api.saas":["aws_cognito_user_pool.tenants","aws_alb.internal~1","aws_alb.internal~2"],"aws_vpc.saas":["tv_aws_az.us_east_1a","tv_aws_az.us_east_1b","aws_vpc_endpoint.dynamodb_gateway","a... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-saas-multi-tenant.tvg.json --annotate aws-saas-multi-tenant.annotations.yml
format: '0.3'
title: AWS multi-tenant SaaS with pooled and silo tiers on ECS Fargate
update:
aws_vpc.saas:
cidr_block: ... | 42 | terravision draw --source aws-saas-multi-tenant.tvg.json --annotate aws-saas-multi-tenant.annotations.yml --format png | |
aws-sagemaker-mlops | aws | Amazon SageMaker MLOps architecture diagram | Draw an Amazon SageMaker MLOps platform in a VPC across two availability zones: SageMaker Studio in VPC-only mode reached through Client VPN, Feature Store, a Step Functions retraining workflow started weekly by EventBridge Scheduler that runs SageMaker Pipelines and registers models in the Model Registry, a real-time ... | {"tv_aws_users.data_scientists":["aws_ec2_client_vpn_endpoint.data_science"],"tv_aws_mobile_client.customer_app":["aws_api_gateway_rest_api.predictions"],"aws_api_gateway_rest_api.predictions":["aws_lambda_function.predict~1","aws_lambda_function.predict~2"],"aws_vpc.ml":["tv_aws_az.us_east_1a","tv_aws_az.us_east_1b","... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-sagemaker-mlops.tvg.json --annotate aws-sagemaker-mlops.annotations.yml
format: '0.3'
title: Amazon SageMaker MLOps with a private Studio, Pipelines and a real-time endpoint
update:
aws_vpc.ml:
c... | 36 | terravision draw --source aws-sagemaker-mlops.tvg.json --annotate aws-sagemaker-mlops.annotations.yml --format png | |
aws-security-logging | aws | AWS security logging architecture diagram | Draw AWS organisation security logging by account: an organisation CloudTrail trail in the management account; Config, GuardDuty and VPC flow logs in workload accounts; a log archive account with S3 buckets using Object Lock; and a security tooling account with the delegated GuardDuty administrator, Security Hub, Confi... | {"aws_account.management":["aws_cloudtrail.organization_trail"],"aws_account.workloads":["aws_config_configuration_recorder.workloads","aws_guardduty_member.workloads","aws_vpc_flow_log.workloads"],"aws_account.log_archive":["aws_s3_bucket.cloudtrail_logs","aws_s3_bucket.config_history","aws_s3_bucket.flow_logs"],"aws_... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-security-logging.tvg.json --annotate aws-security-logging.annotations.yml
format: '0.3'
title: AWS organisation security logging and threat detection
update:
aws_vpc.security_tooling:
cidr_block:... | 32 | terravision draw --source aws-security-logging.tvg.json --annotate aws-security-logging.annotations.yml --format png | |
aws-serverless-event-driven | aws | AWS serverless event-driven architecture diagram | Draw an AWS serverless event-driven order system with every Lambda in a VPC across two availability zones: API Gateway with Cognito invoking order Lambdas in private subnets, a DynamoDB gateway endpoint, interface endpoints for EventBridge, SNS and Secrets Manager in an endpoints subnet per zone, and NAT gateways only ... | {"tv_aws_users.customers":["aws_apigatewayv2_api.orders_api"],"aws_apigatewayv2_api.orders_api":["aws_cognito_user_pool.customers","aws_lambda_function.orders_api~1","aws_lambda_function.orders_api~2"],"aws_vpc.orders":["tv_aws_az.us_east_1a","tv_aws_az.us_east_1b","aws_vpc_endpoint.dynamodb_gateway","aws_internet_gate... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-serverless-event-driven.tvg.json --annotate aws-serverless-event-driven.annotations.yml
format: '0.3'
title: AWS serverless event-driven order platform in a VPC
update:
aws_vpc.orders:
cidr_block... | 47 | terravision draw --source aws-serverless-event-driven.tvg.json --annotate aws-serverless-event-driven.annotations.yml --format png | |
aws-static-site-cicd | aws | AWS static website with CI/CD architecture diagram | Draw an AWS static website with CI/CD: Route 53, AWS WAF and an ACM certificate on a CloudFront distribution reading a private S3 bucket through origin access control, with a cross-Region replica bucket as failover origin, Lambda@Edge security headers and an access-log bucket, and a release where a GitHub push through ... | {"tv_aws_users.visitors":["aws_route53_zone.site"],"aws_route53_zone.site":["aws_cloudfront_distribution.production"],"aws_wafv2_web_acl.site":["aws_cloudfront_distribution.production"],"aws_cloudfront_distribution.production":["aws_lambda_function.security_headers","aws_s3_bucket.site","aws_s3_bucket.site_replica","aw... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-static-site-cicd.tvg.json --annotate aws-static-site-cicd.annotations.yml
format: '0.3'
title: AWS static website on CloudFront and S3 with a CodePipeline release
update:
tv_aws_internet.github:
... | 27 | terravision draw --source aws-static-site-cicd.tvg.json --annotate aws-static-site-cicd.annotations.yml --format png | |
aws-streaming-analytics | aws | AWS real-time streaming analytics architecture diagram | Draw an AWS real-time streaming analytics platform: mobile apps writing to Kinesis Data Streams, a Managed Service for Apache Flink application in private subnets across two availability zones reading through a Kinesis interface endpoint and indexing into OpenSearch, Redshift Serverless with streaming ingestion queried... | {"tv_aws_mobile_client.mobile_apps":["aws_kinesis_stream.clickstream"],"aws_vpc.streaming":["tv_aws_az.us_east_1a","tv_aws_az.us_east_1b","aws_vpc_endpoint.s3_gateway"],"tv_aws_az.us_east_1a":["aws_subnet.processing~1","aws_subnet.analytics~1","aws_subnet.endpoints~1"],"aws_subnet.processing~1":["aws_kinesisanalyticsv2... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-streaming-analytics.tvg.json --annotate aws-streaming-analytics.annotations.yml
format: '0.3'
title: AWS real-time streaming analytics with Kinesis, Managed Flink and Redshift Serverless
update:
aws_... | 33 | terravision draw --source aws-streaming-analytics.tvg.json --annotate aws-streaming-analytics.annotations.yml --format png | |
aws-vm-lift-and-shift | aws | AWS VM lift-and-shift migration architecture diagram | Draw an AWS lift-and-shift of a Windows three-tier app: on-premises web, app, SQL Server and file servers replicating with Application Migration Service over a site-to-site VPN to a replication server in a staging subnet; then, across two availability zones, an internet-facing ALB, EC2 web and app Auto Scaling groups w... | {"tv_aws_onprem.datacentre":["tv_aws_server.web_servers","tv_aws_server.app_servers","tv_aws_database.sql_server","tv_aws_server.file_server","aws_customer_gateway.datacentre_router"],"tv_aws_server.web_servers":["aws_customer_gateway.datacentre_router"],"tv_aws_server.app_servers":["aws_customer_gateway.datacentre_rou... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-vm-lift-and-shift.tvg.json --annotate aws-vm-lift-and-shift.annotations.yml
format: '0.3'
title: AWS lift-and-shift of a Windows three-tier application with Application Migration Service
update:
aws_... | 56 | terravision draw --source aws-vm-lift-and-shift.tvg.json --annotate aws-vm-lift-and-shift.annotations.yml --format png | |
azure-aks | azure | Azure AKS microservices architecture diagram | Draw an AKS microservices platform on Azure: Front Door with WAF in front of an Application Gateway, an AKS cluster with autoscaling node pools across three zones, Cosmos DB, Service Bus and Redis reached through private endpoints in their own subnet, a NAT gateway for egress, and ACR, Key Vault, Log Analytics and Azur... | {"tv_azurerm_users.customers":["azurerm_cdn_frontdoor_profile.edge"],"azurerm_cdn_frontdoor_firewall_policy.waf":["azurerm_cdn_frontdoor_profile.edge"],"azurerm_cdn_frontdoor_profile.edge":["azurerm_public_ip.ingress"],"azurerm_public_ip.ingress":["azurerm_application_gateway.ingress"],"azurerm_resource_group.shop":["a... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-aks.tvg.json --annotate azure-aks.annotations.yml
format: '0.3'
title: Azure AKS microservices with Front Door and private endpoints
update:
azurerm_virtual_network.aks:
address_space:
- 10... | 31 | terravision draw --source azure-aks.tvg.json --annotate azure-aks.annotations.yml --format png | |
azure-batch-hpc | azure | Azure Batch HPC architecture diagram | Draw Azure Batch HPC with simulation engineers using an App Service job portal, a Batch account with dedicated and Spot HBv4 pools in a compute subnet, Azure NetApp Files scratch in a delegated subnet, Blob Storage inputs and results, private endpoints for Batch and Blob Storage, a VPN gateway to a FlexLM licence serve... | {"tv_azurerm_users.engineers":["azurerm_linux_web_app.job_portal"],"tv_azure_onprem.datacenter":["tv_azurerm_server.licence_server","azurerm_local_network_gateway.datacenter"],"azurerm_local_network_gateway.datacenter":["tv_azurerm_server.licence_server"],"azurerm_resource_group.hpc":["azurerm_virtual_network.hpc","azu... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-batch-hpc.tvg.json --annotate azure-batch-hpc.annotations.yml
format: '0.3'
title: Azure Batch HPC with dedicated and Spot pools, Azure NetApp Files and an on-premises licence server
update:
azurer... | 26 | terravision draw --source azure-batch-hpc.tvg.json --annotate azure-batch-hpc.annotations.yml --format png | |
azure-container-apps-microservices | azure | Azure Container Apps microservices architecture diagram | Draw Azure Container Apps microservices in an internal zone-redundant environment in a virtual network, with Azure DNS and Front Door with WAF over Private Link, storefront, orders, payments and KEDA-scaled fulfilment apps, a nightly Container Apps job, private endpoints for Cosmos DB, Azure SQL, Service Bus and Azure ... | {"tv_azurerm_users.customers":["azurerm_dns_zone.shop"],"azurerm_dns_zone.shop":["azurerm_cdn_frontdoor_profile.edge"],"azurerm_cdn_frontdoor_firewall_policy.waf":["azurerm_cdn_frontdoor_profile.edge"],"azurerm_cdn_frontdoor_profile.edge":["azurerm_container_app_environment.shop"],"azurerm_resource_group.shop":["azurer... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-container-apps-microservices.tvg.json --annotate azure-container-apps-microservices.annotations.yml
format: '0.3'
title: Azure Container Apps microservices with Front Door Private Link and KEDA scali... | 32 | terravision draw --source azure-container-apps-microservices.tvg.json --annotate azure-container-apps-microservices.annotations.yml --format png | |
azure-hub-spoke | azure | Azure hub-and-spoke network architecture diagram | Draw an Azure hub-and-spoke landing zone: a hub VNet with a VPN gateway to the head office, Azure Firewall with a firewall policy, Bastion and a Private DNS Resolver, peered to two spokes. One spoke runs a public web app (Application Gateway, a VM scale set across two zones with a CPU autoscale setting, Azure SQL via p... | {"tv_azurerm_users.office_users":["azurerm_local_network_gateway.head_office"],"azurerm_local_network_gateway.head_office":["azurerm_virtual_network_gateway.vpn"],"tv_azurerm_users.customers":["azurerm_public_ip.web_ingress"],"azurerm_public_ip.web_ingress":["azurerm_application_gateway.web"],"azurerm_resource_group.co... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-hub-spoke.tvg.json --annotate azure-hub-spoke.annotations.yml
format: '0.3'
title: Azure hub-and-spoke landing zone with Azure Firewall
update:
azurerm_virtual_network.hub:
address_space:
-... | 44 | terravision draw --source azure-hub-spoke.tvg.json --annotate azure-hub-spoke.annotations.yml --format png | |
azure-hybrid-expressroute | azure | Azure ExpressRoute hybrid network architecture diagram | Draw an Azure ExpressRoute hybrid network with workstations, DNS and app servers and BGP edge routers in a corporate data centre, an ExpressRoute circuit to an ExpressRoute gateway, a backup site-to-site VPN gateway, a hub with Azure Firewall and its policy, a DNS Private Resolver and Bastion, a peered spoke with an in... | {"tv_azure_onprem.datacenter":["tv_azurerm_client.workstations","tv_azurerm_server.dns","tv_azurerm_server.app_servers","azurerm_local_network_gateway.edge_routers"],"tv_azurerm_client.workstations":["azurerm_local_network_gateway.edge_routers"],"tv_azurerm_server.dns":["azurerm_local_network_gateway.edge_routers"],"tv... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-hybrid-expressroute.tvg.json --annotate azure-hybrid-expressroute.annotations.yml
format: '0.3'
title: Azure hybrid network with ExpressRoute, VPN backup, Azure Firewall and DNS Private Resolver
upda... | 35 | terravision draw --source azure-hybrid-expressroute.tvg.json --annotate azure-hybrid-expressroute.annotations.yml --format png | |
azure-iot-telemetry | azure | Azure IoT telemetry architecture diagram | Draw Azure IoT factory telemetry with an OPC UA server and an IoT Edge gateway on the factory site, the Device Provisioning Service, IoT Hub routing to Blob Storage and a data connection to Azure Data Explorer, Stream Analytics anomaly detection writing to an Event Hub, alerting and Digital Twins sync Function Apps in ... | {"tv_azure_onprem.factory":["tv_azurerm_server.opc_ua","tv_azurerm_iot_device.edge_gateway"],"tv_azurerm_server.opc_ua":["tv_azurerm_iot_device.edge_gateway"],"tv_azurerm_iot_device.edge_gateway":["azurerm_iothub_dps.provisioning","azurerm_iothub.telemetry"],"azurerm_resource_group.iot":["azurerm_virtual_network.iot","... | # Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-iot-telemetry.tvg.json --annotate azure-iot-telemetry.annotations.yml
format: '0.3'
title: Azure IoT factory telemetry with IoT Hub, Stream Analytics, Data Explorer and Digital Twins
update:
azurer... | 27 | terravision draw --source azure-iot-telemetry.tvg.json --annotate azure-iot-telemetry.annotations.yml --format png |
End of preview. Expand in Data Studio
TerraVision cloud architecture diagrams
Natural-language architecture descriptions, each paired with the TerraVision Graph Format JSON that draws it, the annotations that title it, label its networks with CIDR ranges and number its flows, and the rendered diagram with the official AWS, Azure and Google Cloud icons.
Every row is an example from the TerraVision gallery, designed the way a solutions architect on that cloud draws it for a design review: workloads in VPCs, subnets and zones, managed services reached through private endpoints, and numbered steps showing how requests and data move.
Intended use: teaching and evaluating language models to produce cloud architecture diagrams as structured JSON that a renderer turns into an architect-quality picture, instead of Mermaid box-and-arrow output.
Files
data/: the rows.metadata.jsonlhas one JSON object per example (fields below), and the PNG it names sits beside it.sources/: each example's source files, to download, edit and re-render:<id>.tvg.json(the graph) and<id>.annotations.yml(title, CIDR ranges, arrow labels, flows). Thegraphandannotationscolumns hold the same text.
Fields
| field | description |
|---|---|
file_name |
the rendered PNG (shown as the image column) |
id |
example name, <cloud>-<pattern> |
provider |
aws, azure or gcp |
title |
the gallery heading |
prompt |
the request a user would give an AI assistant, naming every major service in the diagram |
graph |
TVG JSON: {"<type>.<name>": ["<type>.<name>", ...]} |
annotations |
YAML: title, update (CIDR ranges), connect (arrow labels) and flows (numbered steps) |
node_count |
number of nodes in the graph |
render_command |
the command that drew the image |
Rendering
pipx install terravision # plus Graphviz
terravision draw --source sources/aws-data-lake.tvg.json \
--annotate sources/aws-data-lake.annotations.yml --format png
Schema: https://patrickchugh.github.io/terravision/schemas/terravision-graph-1.0.schema.json
Source: examples/graphs in the TerraVision repository, built with scripts/hf_dataset/build_dataset.py.
Licence
Graph JSON, annotations and prompts: CC-BY-4.0. Rendered images include provider icons that remain subject to the AWS, Microsoft Azure and Google Cloud architecture icon terms of use (free to use in architecture diagrams).
- Downloads last month
- 141