cloud-networking-design

Designs VPC topologies, subnet tiers, routing, and security group policies for cloud networks.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill cloud-networking-design-snoodleboot-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloud-networking-design
Source: https://github.com/snoodleboot-io/discrecontinual_equations/tree/main/.claude/skills/cloud-networking-design
Command: npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill cloud-networking-design-snoodleboot-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cloud network misconfigurations — overlapping CIDRs, databases in public subnets, runaway NAT and inter-AZ costs — are expensive to fix after deployment. This Skill provides proven patterns and checklists for designing VPC architectures correctly the first time. ## Core Features & Use Cases - VPC and Subnet Topology: Three-tier subnet layouts (public, private, data) spread across availability zones with right-sized CIDR allocation. - Routing and Security: Route table design, NAT gateway egress, security group vs NACL guidance, and group-reference-based policies that track topology instead of IP addresses. - Connectivity and Cost Control: Decision guidance for VPC peering vs transit gateways vs PrivateLink, private endpoints for managed services, and mitigation of inter-AZ, NAT, and egress cost traps. - Use Case: When designing a new multi-account AWS environment, use this Skill to lay out non-overlapping CIDR blocks, place workloads in the correct subnet tiers, and choose the right connectivity pattern before writing any infrastructure code. ## Quick Start Ask the AI to design a VPC network architecture for a three-tier web application across three availability zones with private database subnets.

Frequently Asked Questions about cloud-networking-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a VPC subnet layout across availability zones?▼

Create three subnet tiers per AZ: public subnets with an internet gateway route for load balancers, private subnets with NAT egress for compute, and data subnets with no internet route for databases. Allocate CIDR blocks large enough to avoid renumbering later.

What is the difference between security groups and NACLs?▼

Security groups are stateful, instance-level, allow-only firewalls evaluated as a whole, while NACLs are stateless, subnet-level rules evaluated in numbered order with allow and deny. Use security groups for fine-grained policy and NACLs only for coarse subnet-wide guardrails.

When should I use a transit gateway instead of VPC peering?▼

VPC peering fits two or three VPCs with stable relationships but is non-transitive and grows quadratically in a mesh. Move to a hub-and-spoke transit gateway once you connect more than a handful of VPCs or accounts.

How do I reduce NAT gateway and inter-AZ data transfer costs?▼

Route managed-service traffic through VPC gateway or interface endpoints to bypass NAT, and keep high-volume chatter zone-local with topology-aware routing. Measure inter-AZ, NAT, and egress bytes since these three costs compound silently at scale.

Why can't peered VPCs with overlapping CIDR ranges connect?▼

Peering and VPN routing refuse to forward traffic between overlapping address ranges because routes would be ambiguous. The only fix is renumbering a live network, so allocate non-overlapping blocks from a central IPAM plan up front.