Cloud egress: AWS egress cost path checklist
A single AWS bill mixes Internet, cross-AZ, NAT, and CloudFront meters — use this checklist to name each path before arithmetic.
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, VPC endpoints, object storage, and CDN origin fill. Start with the AWS checklist, then open the matching calculator mode. 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. Journey order: checklist → free-tier cliffs → egress vs ingress → NAT/endpoints → S3 paths → CDN.
Path matrices
Cloud egress: AWS Internet egress free-tier cliff
Complimentary Internet data-transfer allotments end — model the cliff explicitly or averages lie.
Cloud egress: Azure & GCP free-tier cliffs matrix
Complimentary bandwidth and egress allotments end — model Azure free-grant and GCP free-tier cliffs beside the AWS cliff spoke.
Cloud egress: Egress vs ingress path classes
Egress leaving a cloud boundary and ingress entering are different meters — name direction before any $/GB arithmetic.
Cloud egress: AWS NAT Gateway vs Internet Gateway triple-charge
Private-subnet Internet access via NAT can stack hourly + processing + egress — the triple-charge pattern FinOps teams miss.
Cloud egress: VPC endpoints vs NAT Gateway path matrix
Gateway and interface VPC endpoints can shift AWS-bound traffic off NAT — compare endpoint fees to the NAT triple-charge stack.
Cloud egress: Cross-AZ vs Cross-Region Data Transfer
High availability often burns more on cross-AZ chatter than on customer downloads — separate the meters.
Cloud egress: AWS S3 vs Cloudflare R2 path matrix
Compare how object-storage egress is billed on AWS S3 versus Cloudflare R2 using path templates — not vendor marketing slides.
Cloud egress: Cloudflare R2 vs Backblaze B2 compare
Both market egress-friendly storage — differences show up in download caps, CDN pairing, and API ops.
Cloud egress: Azure Blob vs AWS S3 bandwidth matrix
Bandwidth on Azure and egress on AWS are not labeled the same — this matrix aligns path classes before rates.
Cloud egress: AWS S3 vs Google Cloud Storage path matrix
Align S3 and GCS path classes — Internet GETs, private compute pulls, replication, and CDN origin fill — before comparing any $/GB cell.
Cloud egress: AWS vs GCP multi-cloud path templates
Map the same workload across AWS and GCP path templates so FinOps reviews compare apples to apples.
Cloud egress: S3 direct vs CloudFront origin path
Public S3 downloads and CloudFront-origin fills are different meters — map who pays before comparing $/GB.
Cloud egress: S3 Transfer Acceleration vs Internet DT-out
Transfer Acceleration is a distinct path class from standard Internet downloads — model acceleration fees separately from DT-out.
Cloud egress: Vercel Blob vs Cloudflare R2 for app assets
Platform-bundled blob storage vs standalone object storage — model delivery path, not logo preference.
Cloud egress: Estimating CDN Origin Fill Egress
Origin fill is egress you pay when the CDN misses — estimate it from hit ratio and object size, not vibes.
Cloud egress: Multi-CDN origin fill path matrix
Two CDN logos in front of one origin still share miss-driven fill — map edge vs origin meters per provider before blending.
Cloud egress: CloudFront vs Cloudflare CDN origin path
CDN logos are not interchangeable meters — map edge transfer versus origin fill before comparing CloudFront and Cloudflare paths.
Read methodology before treating any cell as a quote. Start the AWS meter map with the AWS egress cost path checklist.