Skip to content

Network Segmentation Policy

Private IP Allocation — 10.33.0.0/14

All Watsco e-commerce infrastructure uses private IP space within 10.33.0.0/14 (10.33.0.0 – 10.36.255.255). Each /16 block is assigned a platform or purpose.

/16 Block Allocation

CIDRPurposeStatus
10.33.0.0/16Magento (legacy)Active — eventual deprecation
10.34.0.0/16Shopware — PrimaryActive
10.35.0.0/16Shopware — DR (mirror of 10.34)Reserved
10.36.0.0/16Reserved
10.37.0.0/16Reserved
10.38.0.0/16Reserved
10.39.0.0/16Reserved

10.33.0.0/16 — Magento (Legacy)

Per-BU allocation within 10.33. Each BU receives a 10-block of /24s with a consistent pattern: /23 for Production, /23 for Staging, /23 for DR Production, /23 for DR Staging.

/24 RangeBUNotes
10.33.0–9SupplySyncSee SupplySync docs
10.33.10–19Baker
10.33.20–29Gemaire
10.33.30–39CENAFull
10.33.40–49ECMDI
10.33.50–59Peirce Phelps
10.33.60–69CELATAM
10.33.70–71Homans
10.33.72–79Flow API
10.33.80–83GreeComfort
10.33.84–95Unused
10.33.96/19Human Element Workspace Manager
10.33.128/19Internal Services (Airflow)
10.33.160–255Unused

Per-BU Pattern (Magento)

OffsetCIDRPurpose
+0/23Production
+2/23Staging
+4/23DR Production
+6/23DR Staging
+8–9/24 × 2Overflow / special (OC Registry, etc.)

10.34.0.0/16 — Shopware (Primary)

Greenfield allocation for the Shopware platform. See Shopware Network Architecture for full details.

Key differences from 10.33:

  • /20 per BU (vs 10× /24 in Magento)
  • /21 per environment (vs /23 in Magento) — 4× the IPs
  • Dedicated subnets per component tier (Next.js, Domain API, Shopware Backend)
  • EKS-ready sizing for Domain API
  • Isolated data tier (RDS, ElastiCache, RabbitMQ)
CIDR BlockBU
10.34.0.0/20SupplySync
10.34.16.0/20Baker
10.34.32.0/20Gemaire
10.34.48.0/20CENA
10.34.64.0/20ECMDI
10.34.80.0/20Peirce Phelps
10.34.96.0/20CELATAM
10.34.112.0/20Homans
10.34.128.0/20GreeComfort
10.34.144.0/20Reserved (future BU)
10.34.160.0/20Reserved
10.34.176.0/20Reserved
10.34.192.0/20Shared Services
10.34.208.0/2010.34.240.0/20Reserved

10.35.0.0/16 — Shopware DR

Identical structure to 10.34, deployed in the DR region. Same BU offsets, same per-environment subnet layout. Enables clean Transit Gateway or VPC peering routes with no CIDR overlap between primary and DR.


Design Principles

  1. Account-per-BU-per-environment — each AWS account contains a single VPC for one BU's environment
  2. No CIDR overlap between regions — primary (10.34) and DR (10.35) never conflict
  3. Component isolation — network-level separation between frontend, backend, API, and data tiers
  4. EKS headroom — Domain API subnets sized for VPC CNI pod IP consumption
  5. Consistent patterns — same subnet layout across all BUs, only the base offset changes