Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.2.1.6. Cost-Effective Network Topologies (Transit Gateway, PrivateLink, VPC Peering Pricing)

3.2.1.6. Cost-Effective Network Topologies (Transit Gateway, PrivateLink, VPC Peering Pricing)

💡 First Principle: A network design has three meters: hourly fees for every attachment or endpoint, per-GB processing for every managed hop, and per-GB transfer whenever traffic crosses an Availability Zone or Region boundary. The cheapest topology removes managed hops from the heavy flows and keeps a hub for the many light ones.

Scenario: A company connects 45 VPCs through a "Transit Gateway". Two of them, an analytics VPC and a data lake VPC in the same Region, exchange about 400 TB a month, and the transit gateway's data processing line now exceeds the cost of the analytics compute.

How the connectivity options are billed:
OptionHourly chargePer-GB charge (on top of normal AZ/Region transfer)Choose it when
"VPC peering"NoneNone; same-AZ traffic over peering is free, cross-AZ is billed in each direction, inter-Region is billed as inter-Region transferA few VPC pairs, or one very high-volume pair; non-transitive and no overlapping CIDRs
"Transit Gateway"Per attachment-hourData processing per GB sent into the transit gateway from a VPC, VPN, Direct Connect or Network Firewall attachment (traffic arriving over a TGW peering attachment is not charged processing)Many VPCs, transitive routing, a hybrid hub, centralized inspection
"PrivateLink" interface endpointPer endpoint per AZ-hourData processing per GB, tiered down with monthly volumeExposing one service to many consumers (one direction, overlapping CIDRs allowed), private access to AWS services
Gateway endpoint ("S3", "DynamoDB")NoneNoneSame-Region "S3"/"DynamoDB" traffic from private subnets
Design rules:
  • Hub for the many, peering for the heavy: Keep the transit gateway for general connectivity and add a VPC peering connection for the one or two high-volume pairs, with routes for the peer's CIDR in both VPCs. A route to the peer's specific CIDR is more specific than a summarized transit gateway route, so the heavy flow leaves the hub and stops paying the per-GB processing charge, while every other path is unchanged.
  • Centralize endpoints only for light traffic: Interface endpoints bill per AZ-hour in every VPC that has them, so 50 VPCs times 10 endpoints times 3 AZs adds up even with no traffic. Placing shared interface endpoints in a shared-services VPC, reached over the existing transit gateway with "Route 53" private hosted zones shared to the spokes, removes most endpoint-hours but adds transit gateway processing to each GB. It wins for many VPCs with modest volume; a VPC that pushes heavy volume to one service keeps its own endpoint.
  • Centralized egress has the same trade-off: Sending internet traffic through a central egress VPC removes per-VPC "NAT Gateway" hours but adds transit gateway processing on top of NAT processing for every GB.
  • "PrivateLink" vs. a shared hub for a service: For a SaaS or platform API consumed by hundreds of VPCs, "PrivateLink" puts the endpoint hours and per-GB processing on each consumer, works across overlapping CIDRs, and exposes one service rather than whole networks.
  • Inter-Region: Over a transit gateway peering attachment, the sending side pays processing plus inter-Region transfer; the receiving transit gateway pays no processing for that traffic.

⚠️ Exam Trap: Treating "Transit Gateway" as the cheapest answer because it simplifies the network. It adds a per-GB processing charge to every byte it carries, so for one heavy VPC pair the cost-optimized answer is usually a peering connection alongside the hub. Equally, "VPC peering is free" is only true for same-AZ traffic; cross-AZ and inter-Region transfer still bill.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned