Networking

Cloud networking here is the hub path, private connectivity, DNS and egress design that determines both reachability and the invoice lines those paths create.

Who this topic is for

Network and platform engineers who own VPC or VNet topology and need to decide hub layout, private endpoints and how internet egress is metered.

Problems these pages cover

  • Every spoke NATs to the internet independently.
  • Cross-region replication was designed without an egress estimate.
  • Private endpoints and hub routing disagree, so traffic hairpins.

Recommended reading order

  1. Cloud networking fundamentals
  2. Hub-and-spoke networking
  3. Egress cost planning

Guides in this topic

Ankit Mehta

Egress cost planning

Use the egress cost estimator for a formula pass. It is not an invoice. The operational path for a sudden jump is cross-region traffic cost. Treat each hop as a meter:

Ankit Mehta

Hub-and-spoke cloud networking

Background terms sit in cloud networking fundamentals. Egress money sits in egress cost planning. The hub is the place you put things you do not want copied in every application network:

Related runbooks

Related tools

Consulting

Scoped review for this topic: Cloud architecture consulting.