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

Cloud egress: Azure Blob vs AWS S3 bandwidth matrix

Updated

Bandwidth on Azure and egress on AWS are not labeled the same — this matrix aligns path classes before rates.

Path matrix: Azure Blob bandwidth vs AWS S3 egress classes (educational)
Path classAzure BlobAWS S3Align on
Internet egress / bandwidthBandwidth meters by zoneInternet egress tiersRegion + free grant
Same-region compute pullVNet + Private EndpointVPC endpoint patternsPrivate path fees
Paired / secondary regionGRS/GZRS replication metersCRR / MRC patternsReplication vs reads
CDN originAzure CDN / Front Door originCloudFront originWho bills origin bytes
Egress from archive tiersRehydration + bandwidthRestore + egressTwo-step cost

Provider source footnotes

  1. Azure Bandwidth pricing — as-of Unknown until verified
  2. Azure Blob Storage pricing — as-of Unknown until verified
  3. 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. Azure often says bandwidth; AWS says data transfer out. Normalize vocabulary before arithmetic. PipeToll keeps Honest Unknown cells rather than inventing list prices.

Path templates to model

Common traps

Comparing only “Internet $/GB” ignores private endpoint fees and replication. Archive restores surprise teams that budgeted egress alone. Cross-cloud copy bills the source. No scorecrowns across Azure vs AWS from partial public pages.

FinOps checklist

  1. Translate Azure bandwidth labels to the same path classes used for S3.
  2. Split replication, private, Internet, and CDN-origin lines.
  3. Include restore/rehydration when cold tiers are in play.
  4. Verify rates with dated pricing URLs; else badge Unknown.
  5. Use calculator (?mode=gb&path=azure-s3), methodology, and glossary.

FinOps-lite Unknown until verified

Worked example (educational): 2 TB Internet downloads + archive restore

Restore 500 GB from archive/cool tier (rehydration/restore SKU — often outside pure egress) then download 2,000 GB to Internet. Model restore and bandwidth/egress as separate lines; GB×$/GB alone undercounts. Placeholder rates stay Unknown until dated. Not a savings guarantee.

Open calculator

FAQ on this path

Why does Azure say bandwidth and AWS say egress?

Vendor vocabulary differs. Align on path class (Internet, private, replication, CDN origin) before comparing numbers.

Do paired regions bill like user downloads?

Replication/read patterns can differ from Internet bandwidth. Keep replication meters separate.

What about archive tiers?

Rehydration/restore charges often fire before bandwidth/egress. Model two steps.