Educational — Cloud egress & data-transfer cost guides. FinOps-lite estimators. Not a quote, broker, or savings guarantee. Launching soon where incomplete.
PipeTollCloud egress education
path-templates · Educational

Cloud egress: AWS egress cost path checklist

An AWS egress bill mixes Internet data-transfer-out, cross-AZ, NAT Gateway processing, and CloudFront or origin-fill meters. Name each path with this checklist, then open the matching PipeToll spoke and calculator mode. Educational FinOps-lite — not a quote or savings guarantee.

Updated

A single AWS bill mixes Internet, cross-AZ, NAT, and CloudFront meters — use this checklist to name each path before arithmetic.

Checklist matrix: AWS egress path → PipeToll spoke → calculator mode (educational)
AWS path / meterWhat to measurePipeToll spokeCalculator mode
Internet data-transfer-outGB leaving to public clientsThis checklist + free-tier cliffMode A · gb
Cross-AZ / cross-zoneHA chatter, LB→instance, replicasCross-AZ vs cross-regionMode A · path=cross-az
NAT Gateway stackHours + processing GB + Internet DTNAT vs Internet GatewayMode B · nat
S3 direct downloadsGET bytes from bucket to InternetS3 direct vs CloudFront originMode A · path=s3-direct
CloudFront + origin fillEdge GB + miss-driven origin GBS3 vs CF origin + CDN origin fillMode C · origin

Provider source footnotes

  1. AWS EC2 on-demand data transfer — as-of Unknown until verified
  2. AWS VPC pricing (NAT) — as-of Unknown until verified
  3. AWS CloudFront pricing — as-of Unknown until verified
  4. AWS S3 pricing — as-of Unknown until verified

Dated starting points only — Unknown until verified means no invented $/GB. PipeToll does not scrape private consoles or guarantee figures.

Path-class vocabulary: path template, Unknown until verified. Use this page as a journey map across PipeToll’s AWS-focused spokes. Name the path, then open the matching calculator mode. Educational only — not American pipe-tolling, not a broker.

Path templates to walk

Common traps

Spreadsheets with one “AWS egress” column. Ignoring NAT hours because “we already count Internet GB.” Treating CloudFront as pure savings without CHR. Skipping free-tier cliffs on quiet accounts. No scorecrowns across paths from Incomplete cells.

FinOps checklist

  1. Label every major talker: Internet, cross-AZ, NAT, S3, CloudFront/origin.
  2. Attach a PipeToll spoke URL to each label in your runbook.
  3. Deep-link Mode A, Mode B, or Mode C per meter.
  4. Keep Unknown until verified until rates are dated via methodology.
  5. Revisit after architecture changes — literacy is continuous, not a one-time quote.

FinOps-lite Unknown until verified

Worked estimate walkthrough: 3,000 GB Internet DT-out (Unknown $/GB)

Measured shape: 3,000 GB Internet DT-out this month. Estimate = GB × $/GB where $/GB stays Unknown until a human cites a dated provider page (e.g. AWS EC2 on-demand data transfer, as-of 2026-09-09). Stack separate Mode A/B/C runs for cross-AZ, NAT, and origin fill — five lines, not one blended cell. Synthetic educational arithmetic — not a quote or savings guarantee.

Open calculator

FAQ on this path

Why not one AWS egress number?

Internet, cross-AZ, NAT processing, and CloudFront/origin fills are different SKUs. Blending them hides the HA and NAT taxes.

Where do I start if the bill is opaque?

Export bytes by path class for 30–90 days, then walk this checklist top-down. Deep-link each spoke’s calculator mode.

Does this checklist guarantee lower spend?

No. PipeToll never guarantees savings. The checklist improves metering literacy only.