Networking Documentation

Central documentation for network architecture, IP allocation, and VPC layouts across Watsco's e-commerce infrastructure. This site serves as the authoritative reference for how private IP space is allocated, how environments are structured, and how services interconnect.

Table of Contents

Section	Description
Segmentation Policy	Top-level /16 allocation across platforms (Magento, Shopware, DR)
SupplySync	SupplySync network — VPC layouts, subnets, host IPs (us-east-2)
Shopware	Shopware platform network architecture — per-BU allocation, EKS, shared services

Scope

This documentation covers:

• IP segmentation policy — how 10.33.0.0/14 is divided across platforms and business units
• VPC architecture — subnet layouts, AZ distribution, tier isolation
• Per-environment detail — production and staging subnet maps with host assignments
• EKS networking — pod CIDR planning, shared vs. per-BU cluster options
• Connectivity — Transit Gateway, VPC peering, and cross-account routing
• DR strategy — primary/DR region separation and CIDR non-overlap guarantees

Platforms

Magento (Legacy) — 10.33.0.0/16

The existing e-commerce platform. Per-BU environments with /23 VPCs. Documented for reference during the migration to Shopware. These allocations will be reclaimed as BUs migrate.

Shopware (Active) — 10.34.0.0/16

The greenfield Shopware platform. Each BU receives a /20 with /21 per environment. Three-tier architecture (Next.js, Domain API, Shopware Backend) with dedicated subnet groups and EKS-ready sizing.

DR — 10.35.0.0/16

Mirror of the Shopware primary allocation, deployed in the DR region. Identical BU offsets and subnet structure, no CIDR overlap with primary.

Conventions

• One AWS account per BU per environment — each VPC is the sole network in its account
• 3-AZ deployment — all subnets span us-east-2a, 2b, 2c
• Tier isolation — ingress, compute, data, and API tiers occupy separate subnet groups
• Contiguous reserved space — uncertain workloads (Next.js, EKS) placed at the top of the address range so unused blocks merge cleanly

Contributing

This site is built with VitePress and uses D2 for network diagrams.

make dev        # Install deps, render diagrams, start dev server
make diagrams   # Re-render all D2 diagrams to SVG
make build      # Full production build
make deploy     # Build + upload to S3

Source: Bitbucket