Skip to content
Skills Library
DevOps & cloud · Planning

cloud-networking

/cloud-networking

Lay out VPCs, subnets, private connectivity, and DNS so services reach each other privately and the internet only on purpose. Use when designing cloud network topology or debugging cross-service connectivity.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Lay out VPCs, subnets, private connectivity, and DNS so services reach each other privately and the internet only on purpose. Use when designing cloud network topology or debugging cross-service connectivity.

Original author description

Lay out VPCs, subnets, private connectivity, and DNS so services reach each other privately and the internet only on purpose. Use when designing cloud network topology or debugging cross-service connectivity.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 52 lines, 368 words
SKILL.md preview
---
name: cloud-networking
description: Lay out VPCs, subnets, private connectivity, and DNS so services reach each other privately and the internet only on purpose. Use when designing cloud network topology or debugging cross-service connectivity.
---

# Cloud networking

Default-deny is the design stance: nothing reaches the internet, another
VPC, or your data stores unless a rule you wrote says so. Everything
else is plumbing to make that stance livable.

## Method

1. **Plan address space before the first VPC.** Non-overlapping CIDRs
   across VPCs, regions, and the office/VPN ranges, sized with 4x
   growth headroom, recorded in one registry. Overlaps discovered at
   peering time cost re-IP projects; ten minutes of spreadsheet now
   prevents them.
2. **Tier subnets by exposure.** Public subnets hold only entry points
   (load balancers, NAT); private subnets hold compute; isolated
   subnets hold data stores with no internet path at all. Workloads
   never get public IPs; inbound flows through the LB, outbound through
   NAT (watch its processing cost; see cloud-cost-optimization).
3. **Prefer identity rules over IP rules.** Security groups referencing
   other security groups ("db-sg allows app-sg on 5432") survive
   autoscaling and re-IPs; CIDR-based rules rot. Keep NACLs at coarse
   subnet guardrails; per-flow logic lives in security groups where
   state is handled for you.
4. **Reach managed services privately.** Private endpoints/Private Link
   for object storage, queues, and third-party SaaS keep traffic off
   the public internet and let isolated subnets function; they also
   carry per-GB cost, so hubs share endpoints where volume justifies.
5. **Scale inter-VPC with a hub, not a mesh.** Two or three VPCs:
   peering is fine. Beyond that, a transit hub (transit gateway
   pattern) centralizes routing, on-prem VPN/Direct Connect attachment,
   and egress inspection; peering meshes grow O(n^2) route tables that
   nobody can audit.
6. **Treat DNS as the service map.** Private zones per environment
   (`svc.internal`), records managed by IaC alongside the services;
   split-horizon so internal names never leak to public resolvers.
   Connectivity debugging order: DNS resolution, then security group,
   then route table, then endpoint policy; flow logs answer the "is it
   even arriving" question.

## Boundaries

- This is L3/L4 topology; service-to-service authn/z and mTLS live a
  layer up (see service-mesh-tradeoffs, zero-trust-basics), and network
  segmentation does not replace them.
- Kubernetes overlays its own networking (CNI, services, ingress) on
  top of this; pod-level policy is a separate control plane (see
  kubernetes-workloads).
- Multi-region topology (failover, data locality) is driven by
  multi-region-design; do not build global network plumbing ahead of a
  decided architecture.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
chrishuffman5/domain-expert100MIT
arjunprabhulal/devops-skills85MIT

Database snapshot: 13.11.2026 · package version 77df4384ea8d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100forge-network
    Design and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".
  • 100render-networking
    Connects Render services over the private network—internal DNS, service discovery, and cross-service communication. Use when the user needs to wire services together, resolve internal hostnames, troubleshoot connectivity between services, configure environment isolation, or…
  • 87huawei-cloud-vpc-network-diagnosis-management
    Use when managing Huawei Cloud VPC (Virtual Private Cloud) networks — VPC/subnet CRUD operations, network connectivity diagnosis, port connectivity diagnosis, and subnet CIDR conflict analysis. Covers listing VPCs/subnets/route tables, querying VPC/subnet details,…
  • 100gcp-networking
    Configure VPCs, firewall rules, and Cloud NAT. Implement shared VPC and private service connect. Use when designing GCP network infrastructure.
  • 100gcp-networking
    Configure VPCs, firewall rules, and Cloud NAT. Implement shared VPC and private service connect. Use when designing GCP network infrastructure.
  • 100gcp-networking
    Configure VPCs, firewall rules, and Cloud NAT. Implement shared VPC and private service connect. Use when designing GCP network infrastructure.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.