An AWS egress bill mixes Internet data-transfer-out, cross-AZ, ELB cross-zone, NAT Gateway processing, PrivateLink, peering/TGW, Direct Connect, S3 CRR, 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, ELB, NAT, PrivateLink, peering/TGW, Direct Connect, S3 CRR, and CloudFront meters — use this checklist to name each path before arithmetic.
Dated starting points only — Unknown until verified means no invented $/GB. Verified here means the cited public URL responded as-of the date; it does not mean PipeToll pasted a region-qualified list price. Inferred means educational mapping pending your export. PipeToll does not scrape private consoles or guarantee figures. Distinct from ProofWindow.
Spreadsheets with one “AWS egress” column. Ignoring NAT hours because “we already count Internet GB.” Treating CloudFront as pure savings without CHR / origin fill. Skipping free-tier cliffs on quiet accounts. Blending ELB cross-zone into instance cross-AZ. Pasting S3 CRR into a CDN miss cell. Collapsing PrivateLink / VPC endpoint processing into the NAT stack. Treating Direct Connect port hours as interchangeable with Internet DT-out. No scorecrowns across paths from Incomplete cells.
One-column “AWS egress” — Internet DT-out, cross-AZ, ELB cross-zone, NAT triple-charge, PrivateLink, peering/TGW, DX, S3 CRR, and CloudFront/origin fill are different path templates. One blended cell hides the HA and NAT taxes.
NAT hours erased — counting only Internet GB through NAT misses hourly + processing meters of the triple-charge pattern.
CloudFront = automatic savings — without CHR and origin-fill literacy, miss-heavy edges can recreate origin DT-out under a new label.
Quiet-account cliff blindness — free-tier cliffs apply to Internet DT-out independently of NAT or CF lines; model the cliff remainder separately.
ELB ↔ instance cross-AZ blend — ALB/NLB cross-zone bytes are not the same SKU as instance cross-AZ chatter; keep path=elb-cross-zone and path=cross-az apart in Mode A.
CRR pasted into CDN miss — bucket→bucket replication is not end-user egress and not origin fill; use path=s3-crr alone.
Incomplete → crown — Incomplete / Unknown cells stay Incomplete. PipeToll never invents $/GB to finish a matrix. Stay FinOps-lite.
FinOps checklist
Label every major talker: Internet, cross-AZ, ELB cross-zone, NAT, PrivateLink, peering/TGW, Direct Connect, S3 GET/CRR, CloudFront/origin.
Attach a PipeToll spoke URL to each label in your runbook.
Revisit after architecture changes — literacy is continuous, not a one-time quote.
FinOps-liteUnknown until verified
Worked estimate walkthrough: multi-meter month (Unknown $/GB)
Measured shape (educational stack, not a quote): 3,000 GB Internet DT-out + 8,000 GB cross-AZ chatter + 1,500 GB NAT processing + 730 NAT hours + 4,000 GB client CDN download at CHR 0.80 (so ~800 GB origin fill). Keep every meter on its own line. $/GB and $/hour stay Unknown until a human cites dated provider pages (EC2 DT, VPC NAT, CloudFront/S3 — as-of footnotes above). Synthetic educational arithmetic — not a quote or savings guarantee.
Second educational twin (S3-heavy): 6,000 GB S3 direct GET + 2,000 GB CRR + residual NAT for private-subnet control-plane. Split Mode A runs — ?path=s3-direct&gb=6000 and ?path=s3-crr&gb=2000 — then Mode B for any NAT. Decode confusing CE labels on the Cost Explorer decoder. Synthetic only.
Bill-style path attribution (educational Cost Explorer shape)
FinOps readers often see separate Cost Explorer / CUR-ish lines and still paste one “AWS egress” rate. Walk this bill-style month first — volumes are a synthetic educational shape, not a customer invoice. Every unit rate stays Unknown until you cite a dated, region-qualified provider page per methodology. Decode opaque labels on the Cost Explorer decoder. Distinct from ProofWindow.
Synthetic bill-style month — path attribution before arithmetic (not a quote)
Attribute before multiply. Name each CE/CUR-ish label with this checklist; do not invent a blended “AWS egress” cell.
Cliff only on Internet DT-out. Complimentary allotments do not cancel NAT hours, InterZone, CRR, or origin fill — see the AWS free-tier cliff spoke.
CHR honesty. Client edge GB ≠ origin GB. Mode C needs a measured or explicitly Inferred cache-hit ratio; badge the miss volume accordingly.
Unknown rates are success. Leaving $/GB blank until a human dates an official page is the PipeToll posture — not a missing feature. No savings guarantee.
Synthetic educational arithmetic only. Volumes above are illustrative. Status badges: Verified = cited public URL checked as-of date; Inferred = educational mapping or assumed CHR pending your export; Unknown = no region-qualified $/GB pasted. Distinct from ProofWindow.
Calculator methodology pointers
PipeToll calculators are client-side FinOps-lite estimators. They do not call a live AWS Pricing API and do not quote your account. Use this page to choose the mode, then paste only rates you verified:
Mode A (GB × $/GB) — Internet DT-out, cross-AZ, ELB cross-zone, peering/TGW processing, DX transfer, S3 GET, S3 CRR. Deep-link examples above. Methodology: pricing snapshot & as-of · worked Unknown.
Mode C (origin fill) — client GB × (1 − CHR) → origin GB, then origin $/GB. Pair with CDN origin fill and CloudFront docs cited in Sources.
Provenance checklist before any public matrix shows a number instead of Unknown — region, SKU path class, official URL, as-of date, staleness plan — is on methodology § provenance checklist. Sitemap lastmod bumps only when this URL’s public content changes; this depth pass is one such change.
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.
How do I attribute a Cost Explorer line to a PipeToll path?
Match the CE/CUR-ish label to the bill-style table on this page (or the CE decoder), then open Mode A/B/C. Keep $/GB Unknown until you cite a dated official pricing page for your region — see methodology.
Are the bill-style volumes a real invoice?
No. They are a synthetic educational shape so you can practice path attribution. Distinct from ProofWindow. No savings guarantee.
Does this checklist guarantee lower spend?
No. PipeToll never guarantees savings. The checklist improves metering literacy only.
Trademarks: Amazon Web Services, AWS, Microsoft Azure, Google Cloud Platform, GCP, and Cloudflare are trademarks of their respective owners. PipeToll (Ameti One LLC) is not affiliated with, endorsed by, or sponsored by those companies. Educational comparisons may be outdated — verify current rates with each provider.
