Hybrid cloud network diagram template

A head office network joined to a cloud VPC by a site-to-site IPsec VPN. The office has a users segment and a server room; the VPC has a public subnet for Kubernetes and serverless functions and a private subnet for the managed database and object storage.

Use it to document how on-premises identity and servers reach cloud workloads, and which systems customers reach directly from the Internet.

Use this template freeIn the editor: File → New from template → Hybrid cloud
Head office10.0.0.0/16Users10.0.10.0/24 · VLAN 10Server room10.0.20.0/24 · VLAN 20Cloud VPC10.50.0.0/16Public subnet10.50.1.0/24Private subnet10.50.2.0/24InternetHQ firewall10.0.0.1Access switch10.0.10.2Staff devicesDirectory10.0.20.10Hypervisor10.0.20.20VPN gateway10.50.0.5Load balancerKubernetes10.50.1.10FunctionsManaged DB10.50.2.10Object storageSaaS apps
The template as it opens in Schema: 13 devices, 6 zones and segments, 13 connections.

How it's laid out

  • The office (10.0.0.0/16) and the VPC (10.50.0.0/16) use non-overlapping ranges, which a VPN between them needs. Schema flags overlapping subnets if you change them.
  • Customer traffic arrives at the cloud load balancer. Office traffic to cloud workloads goes through the VPN gateway.
  • SaaS applications (mail, chat, ticketing) use single sign-on from the office directory.

Networks and segments

NameKindSubnetVLANNotes
Head officeZone10.0.0.0/16-On-premises
UsersSegment10.0.10.0/2410-
Server roomSegment10.0.20.0/2420-
Cloud VPCZone10.50.0.0/16-Public cloud region
Public subnetSegment10.50.1.0/24--
Private subnetSegment10.50.2.0/24--

Device inventory

In Schema this table isn't a separate document. It's generated from the diagram, can be edited in place, and exports as CSV.

DeviceTypeHostnameIP addressRoleOwnerSegment
InternetInternet-----
HQ firewallFirewallfw-hq-0110.0.0.1-NetworkHead office
Access switchSwitch-10.0.10.2-NetworkUsers
Staff devicesLaptop--End User Device-Users
DirectoryDirectory / IdPdc-0110.0.20.10Domain ControllerITServer room
HypervisorHypervisorhv-0110.0.20.20HypervisorITServer room
VPN gatewayVPN-10.50.0.5-NetworkCloud VPC
Load balancerLoad Balancer--Load BalancerPlatformCloud VPC
KubernetesKubernetes-10.50.1.10-PlatformPublic subnet
FunctionsServerless---PlatformPublic subnet
Managed DBDatabase-10.50.2.10PrimaryData teamPrivate subnet
Object storageStorage---Data teamPrivate subnet
SaaS appsSaaS-----

Rules it checks

The template comes with these rule packs switched on. Schema checks them as you edit and marks anything that breaks a rule on the canvas. Every rule can be edited, turned off or deleted.

Perimeter & segmentation

Internet-facing systems sit behind a firewall, databases aren't exposed directly, and traffic between networks passes a firewall.

  • Internet-connected servers must sit behind a firewall
  • Databases must not connect directly to the Internet
  • Storage must not connect directly to the Internet
  • Servers reaching across a network boundary need a firewall in the path
  • Databases reaching across a network boundary need a firewall in the path
  • Workstations must not connect directly to databases

Documentation completeness

Every server, database and network device has the fields someone on call at 3am will need: an address, an owner, a role.

  • Servers must have an IP address
  • Servers must have an owner
  • Servers must have a role
  • Servers must record their OS
  • Databases must have an IP address
  • Databases must have an owner
  • Firewalls must have an IP address
  • Routers must have an IP address

Start from this template

Open it in Schema, replace the example addresses with yours, and you have a diagram, an inventory and a written report of your network. Free during early access.

Use this template free

Other templates