Hybrid Cloud Architecture Designer | NetAIForge

Cloud Network Designer & AWS/Azure VPC Subnet Calculator | NetAI

Infrastructure Designer Inputs

Multi Cloud (AWS & Azure workload)

GatewaySubnet Validations Checked

Usable Azure Host Ranges Verified

├── Node-01 (Public IP: Active)

├── Node-02 (Public IP: Active)

├── Node-03 (Public IP: Active)

Infrastructure-as-Code Configuration

Total address space limits of parent range.

5 reserved addresses per allocated subnet.

Usable IP overhead remaining for pod growth.

Subnet Allocation Utilization Gauge

Invalid CIDR format (use e.g. 10.0.0.0/16)

Prefix length must be between 0 and 32

IP octets must be between 0 and 255

Base CIDR is not in RFC1918 private IP space. Ensure public routing is intended.

VNet allocation exhausted when creating Application Subnet

VNet allocation exhausted when creating Database Subnet

VNet allocation exhausted when creating AKS Subnet

VNet allocation exhausted when creating GatewaySubnet

VPC allocation insufficient for secondary Azure VNet workload

Kubernetes cluster pod utilization projection is critically high (>85%). Consider sizing up Pod CIDR block.

Kubernetes cluster pod utilization projection is high (>60%). Monitor scaling limits.

w-full animate-in fade-in duration-500

Design AWS VPCs, Azure VNets, Kubernetes CIDR pod networks, and dynamic Terraform configurations using an interactive cloud network designer.

cloud network designer, vpc calculator, azure vnet planner, kubernetes cidr, terraform network generator

Plan and design cloud networking architectures and generate clean Terraform manifests.

w-full space-y-6 relative z-10

M 360 125 L 360 160 L 120 160 L 120 190

M 360 125 L 360 160 L 600 160 L 600 190

Design AWS VPCs, Azure VNets, Kubernetes CIDR pod networks, and generate ready-to-use Terraform files.

AWS VPC, Microsoft Azure VNet, Kubernetes CNI (VPC CNI, Calico, Cilium), Terraform IaC, CloudFormation

VPC/VNet base IP CIDR (e.g. 10.0.0.0/16), subnet tiers (Public, Private, Database), AZ count, and worker node capacities.

Detailed IP subnet address maps, Kubernetes capacity analysis report, and downloadable Terraform modules.

Always replicate your private/public subnet tier layout across at least two or three Availability Zones (AZs) for high availability.

Separate databases into dedicated database tiers with isolated Security Groups and NACLs.

Deploy NAT Gateways in public subnets to allow private subnet nodes internet access safely.

Designing clean greenfield multi-tier cloud architectures for AWS and Azure.

Planning pod capacity networks for large Kubernetes clusters to avoid IP exhaustion.

Generating standard Terraform manifests to automate VPC network builds.

AWS reserves 5 IP addresses in each subnet, and Azure reserves 5 IP addresses as well.

Azure VNets allow adding multiple CIDR blocks later, while AWS VPC CIDRs are less flexible once created.

Cloud Networking Architecture & Design

The Cloud Network Designer is a visual-assisted calculator that helps cloud architects design Virtual Private Clouds (VPCs) in AWS or Virtual Networks (VNets) in Azure. It automates partitioning address space into Public, Private, and Database tiers, plans Kubernetes network pods, and exports copy-pasteable Terraform configuration files.

Use this designer during the initialization phase of a new cloud environment or container migration project. Sizing subnets incorrectly early on is extremely costly to remediate, often requiring rebuilding resources from scratch.

Kubernetes CNI Sizing Considerations

CNI engines like the AWS VPC CNI assign native VPC IP addresses to every pod. If worker nodes run up to 110 pods, each node consumes 110 IP addresses from the worker subnet. Subnets sized smaller than a /24 (251 usable IPs) will rapidly run out of address space, blocking container autoscaling. Dedicated Pod CIDRs (e.g., /16 or /18 ranges) should be allocated for large workloads.

Special Subnets in Azure VNets

Azure requires dedicated subnets for specific service nodes. For instance, Azure Virtual Network Gateways must reside in a subnet named exactly 'GatewaySubnet' (minimum recommended /27), and Azure Bastion hosts require 'AzureBastionSubnet' (minimum /26). These special tiers should be isolated from standard compute subnets.

Why does AWS reserve 5 IP addresses in each subnet?

What is the recommended size for Azure's GatewaySubnet?

Azure officially recommends sizing GatewaySubnet at /27 or /26 to ensure there are enough IP addresses for VPN and ExpressRoute active-active configurations, co-existence setups, and future expansion.

How does the VPC CNI handle IP allocation differently from overlay networks?

The AWS VPC CNI assigns native VPC IP addresses to each Pod, providing lower latency and direct routing, but consuming many VPC subnet IPs. Overlay CNIs (like Calico) route Pod traffic through virtual private IP interfaces, saving public/private VPC IP address space at the expense of a slight encapsulation performance overhead.

What is RFC 1918 private address space?

RFC 1918 defines the specific IP blocks reserved for private networks: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These ranges are not routable on the public internet, ensuring security and avoiding duplication.

Why should database subnets be kept in a separate tier?

To ensure maximum security. Isolating RDS or database instances in database-only subnets allows you to deny all public incoming requests at the Network ACL layer and restrict DB port access solely to your application subnets.