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

Cloud egress compare hub: path matrices

PipeToll compare spokes are path-template matrices for cloud egress and data-transfer meters — Internet DT-out, NAT, Direct Connect / hybrid interconnect, VPC peering/TGW, ELB cross-zone, object storage, and CDN origin fill. Start with a journey card, then open a labeled cluster. Educational FinOps-lite — Unknown until verified, never a savings guarantee.

Updated

Every spoke is a matrix or template — not a scraped clone of vendor pricing HTML. Follow the Suggested path (checklist → NAT → free-tier cliffs → CDN origin → calculator) or pick a start-here journey card; labeled clusters sit below. Batch-34 second-pass thickens Suggested-path walk guidance and cluster-family cues without adding spokes — still path templates first, Unknown until verified.

Start here

Suggested path: AWS path checklist → NAT vs IGW → AWS free-tier cliff → Multi-cloud cliffs → CDN origin fill → Calculator

One linear walk across existing spokes only — name the meter on the AWS egress cost path checklist, stack the NAT triple-charge on NAT vs IGW, watch free-tier cliffs on the AWS cliff then the Azure & GCP cliffs matrix, estimate origin fill via CDN origin fill, then open Mode A/B/C on the calculator with Unknown rates. Decode opaque CE labels anytime with the Cost Explorer decoder (ELB cross-zone sits beside InterZone and Internet). No new /compare/* URLs — depth-not-width. Journey cards below remain alternate entry points (bill shock · private-subnet · object/CDN). FinOps-lite education only; never a savings guarantee.

How to walk the Suggested path (depth, not new spokes)

Treat the chain as a meter-naming drill, not a shopping cart. On the checklist, mark which path actually fired (Internet DT-out · InterZone · ELB cross-zone · NAT stack · PrivateLink · DX · S3 CRR · CloudFront) before you open any $/GB cell. When the bill line smells like private-subnet Internet, open NAT vs IGW and keep hourly + processing + egress as three lines — the triple-charge pattern — then decide whether a VPC endpoint or PrivateLink removes AWS-bound chatter without inventing a fourth Internet path.

Cliff steps are remainder math: the AWS free-tier cliff teaches the complimentary Internet allotment ending; the multi-cloud cliffs matrix keeps Azure bandwidth grants and GCP free-tier siblings from blending into one “free egress” story. Only after cliffs are named should you estimate CDN origin fill from CHR — client edge GB is not origin GB — and park rates as Unknown on the calculator.

Optional detours that stay on the existing Suggested path URLs only: if CE labels are opaque, jump to the Cost Explorer decoder mid-walk; if HA chatter dominates, keep cross-AZ vs cross-region and ELB cross-zone beside InterZone instead of inventing a new spoke. Hybrid interconnect bills belong on Direct Connect vs Internet with residual NAT called out — still no new /compare/*.

When to leave the linear walk early: if the bill is already decoded as ELB cross-zone or InterZone, jump the NAT / VPC cluster cards for ELB cross-zone and cross-AZ vs cross-region without discarding the checklist. If object storage egress dominates, prefer the multi-cloud cluster (S3 vs R2, R2 vs B2, S3 vs GCS) and return to the calculator only after path classes align. Journey cards remain parallel entry points — they do not add spokes.

Path matrices by cluster

Clusters below surface thickened NAT triple-charge / VPC endpoint, CDN origin-fill CHR, S3 CRR, and ALB cross-zone spokes — path templates first, Unknown until verified. Prefer the Suggested path when you want one ordered walk; use clusters when you already know the meter family (NAT/VPC · CDN origin · multi-cloud · Cost Explorer).

Cluster guidance (batch-34 second-pass): open NAT / VPC when private-subnet or hybrid meters dominate — NAT triple-charge, endpoints, PrivateLink, peering/TGW, DX, ELB cross-zone, and cross-AZ sit together so InterZone never blends with Internet DT-out. Open CDN origin-fill when CHR and miss-driven origin GB are the question — estimating origin fill, multi-CDN lanes, CloudFront vs Cloudflare, S3-direct vs CloudFront, and Transfer Acceleration stay lane-aware. Open Multi-cloud & object storage for S3/R2/B2/GCS/Azure path classes, aws-vs-gcp templates, CRR, free-tier cliffs, and egress-vs-ingress direction. Open Cost Explorer & bill decoding when CUR labels are opaque — checklist first, then the CE decoder — before any Mode A/B/C arithmetic. Every card links an existing spoke only; depth-not-width, no new /compare/* URLs.

NAT / VPC path meters

CDN origin-fill

cdn-origin

Cloud egress: Multi-CDN origin fill path matrix

Two CDN logos on one origin still share miss-driven fill — thickened with a lane CHR sensitivity twin (80% vs 50%), Mode C per-lane deep-links, and CE/CRR knit so edge meters never blend with replication.

Multi-cloud & object storage

multi-cloud

Cloud egress: AWS vs GCP multi-cloud path templates

Map the same workload across AWS and GCP path templates — thickened with an Internet vs InterZone twin, ELB cross-zone knit (AWS-only), and DX/Interconnect sibling so FinOps compares apples to apples.

object-storage

Cloud egress: S3 cross-region replication egress

S3 CRR vs same-region GET vs Transfer Acceleration — SRR ≠ CRR. Keep inter-region replication off the Internet line; pair with free-tier cliffs and the TA spoke when bills blur downloads with replication.

Cost Explorer & bill decoding

path-templates

Cloud egress: AWS egress cost path checklist

A single AWS bill mixes Internet, cross-AZ, ELB, NAT, PrivateLink, peering/TGW, Direct Connect, S3 CRR, and CloudFront meters — use this checklist to name each path before arithmetic.

Read methodology before treating any cell as a quote. Start the AWS meter map with the AWS egress cost path checklist.