Worked example: 2,000 GB × an example $0.09/GB placeholder ≈ $180 in Mode A — synthetic only; paste dated rates or keep Unknown. Mode B stacks NAT hourly + processing + Internet DT-out; Mode C estimates origin fill ≈ client_GB × (1−CHR) × origin $/GB. Free educational WebApplication — not a quote or savings guarantee.
Updated
Runs entirely in your browser. Three educational meters — no accounts, no checkout, no savings guarantees.
Synthetic / educational disclaimer: Estimators ignore many SKUs, taxes, and private discounts. They do not guarantee savings. Verify on provider pricing pages and invoices. Example rates are placeholders — treat as Unknown until verified per methodology.
?mode=) — name the path template first.These walkthroughs reuse PATH_LABELS already wired in calc.js and the Matching spokes list below — no new /compare/* URLs. They follow the compare hub Suggested path (checklist → NAT → free-tier cliffs → CDN origin → calculator) plus this batch’s PrivateLink / S3 CRR depth. Paste dated provider rates yourself; otherwise keep Unknown until verified. Synthetic educational arithmetic only — not a quote or savings guarantee. See methodology for pricing-snapshot / as-of discipline. OTP, role="status" live results, and mode-tab a11y stay unchanged.
Path context label: AWS egress path checklist (path=aws-checklist). Shape: 3,000 GB Internet DT-out this month. Mode A estimate = GB × $/GB where $/GB stays Unknown until a human cites a dated EC2/S3 pricing page. Do not blend cross-AZ, NAT, or origin fill into this cell — stack separate runs. Spoke: AWS egress cost path checklist.
Open Mode A · path=aws-checklist&gb=3000
Path context: S3 Transfer Acceleration vs Internet DT-out (path=s3-ta). Split measured bytes: e.g. 800 GB via Transfer Acceleration vs 3,200 GB standard Internet GET. Run Mode A twice — once for acceleration, once for standard DT-out — and keep free-tier cliff literacy on the standard half only. Acceleration is not CloudFront; if edge delivery is the real goal, re-model with Mode C on the S3 vs CloudFront spoke. Spoke: Transfer Acceleration vs Internet.
Open Mode A · path=s3-ta&gb=800 Upload-heavy twin · gb=2400
Path context: Cross-AZ data transfer (path=cross-az). Example shape: 12,000 GB of multi-AZ chatter (replicas, LB→instance east-west). Mode A with the cross-AZ-ish starter tier is educational only — still badge rates Unknown until dated. Do not paste Internet DT-out $/GB into this cell; do not blend ELB cross-zone into instance cross-AZ. Spoke: Cross-AZ vs cross-region.
Open Mode A · path=cross-az&gb=12000 Cross-region twin · path=cross-region&gb=4000
Path context: Egress vs ingress direction primer (path=egress-ingress). Many teams label every byte “egress.” Mode A here is for outbound DT-out literacy only — ingress is usually a different (often $0) class and must stay off this line. Spoke: Egress vs ingress.
Open Mode A · path=egress-ingress&gb=5000
Path context: Internet egress free-tier cliff (path=free-tier-cliff). Quiet accounts can look cheap until GB crosses the cliff. Model the post-cliff remainder as its own Mode A line; do not average cliff + paid tiers into one blended $/GB. Spokes: AWS free-tier cliff · multi-cloud cliffs (path=multi-cloud).
Open Mode A · path=free-tier-cliff&gb=1200 Multi-cloud twin · path=multi-cloud
Path context: Object store Internet egress (S3 / R2 style) (path=s3-r2). Compare path classes across providers with separate Mode A runs — never one “object egress” cell. Matching deep-links already on this page: path=s3-gcs, path=azure-s3, path=aws-gcp, path=r2-b2. Spokes: S3 vs R2 · S3 vs GCS · Azure vs S3 · AWS vs GCP · R2 vs B2.
Open Mode A · path=s3-r2&gb=7500 GCS twin R2/B2 twin
Path context: NAT Gateway educational stack (path=nat). Completes the compare hub Suggested path step after the checklist: stack NAT hourly + processing + Internet DT-out for 2,000 GB private-subnet chatter (730 Gateway hours). Open Mode B — do not collapse the triple-charge into one Mode A cell. Sibling PrivateLink / endpoint runs stay on separate meters. Spoke: NAT vs IGW · VPC endpoints vs NAT.
Open Mode B · path=nat Endpoint twin · path=vpc-endpoints
Path context: CDN origin fill (path=cdn / path=origin). Completes the Suggested path CDN origin step: origin fill ≈ client_GB × (1−CHR) × origin $/GB. Example shape: 10,000 GB client download at CHR 0.85 → ≈ 1,500 GB origin. Badge origin $/GB Unknown until dated. Do not blend edge delivery $/GB into the origin cell. Spoke: CDN origin fill · Multi-CDN (path=multi-cdn).
Open Mode C · path=cdn Multi-CDN twin S3 vs CloudFront twin · path=s3-cf
Path context: PrivateLink interface endpoint vs NAT egress (path=privatelink-vs-nat). Shape: 1,500 GB/month AWS-bound API chatter — compare NAT hairpin (Mode B) vs interface endpoints (Mode A private-path GB + endpoint hours). Keep residual Internet DT-out for non-AWS destinations on its own line; cross-AZ is a fourth meter when clients and endpoints differ by AZ. Spoke: PrivateLink vs NAT egress.
Open Mode A · path=privatelink-vs-nat&gb=1500 NAT hairpin twin · Mode B path=privatelink twin
Path context: S3 cross-region replication egress (path=s3-crr / path=crr). Shape: 1,200 GB CRR inter-region beside same-region Internet GET — never one blended $/GB. Run Mode A for CRR bytes only; stack GET / Transfer Acceleration as sibling runs (path=s3-ta). SRR ≠ CRR. Spoke: S3 CRR egress.
Open Mode A · path=s3-crr&gb=1200 CRR twin · path=crr&gb=450 TA sibling · path=s3-ta
Walkthrough discipline: each deep-link sets Path context via existing PATH_LABELS and may suggest a starter tier — rates remain educational placeholders. Keep FinOps-lite honesty: Incomplete cells beat invented $/GB. OTP, role="status" live results, and mode tabs stay unchanged.
Mode A: GB × $/GB. Mode B: NAT educational stack (hourly×hours + processing×GB + egress×GB). Mode C: origin fill ≈ client_GB × (1−CHR) × origin $/GB. All synthetic.
No. Results are educational arithmetic only. Free-tier cliffs, taxes, and private discounts are out of scope.
No. PipeToll never guarantees savings. Verify on provider consoles and invoices.
Use ?mode=nat, ?mode=origin, or ?mode=gb. Optional path= sets a Path context label and suggested tier; gb= presets Mode A volume. Spoke worked examples deep-link here.
Educational Mode A/B/C scenarios that reuse existing PATH_LABELS and follow the compare hub Suggested path (checklist → NAT → free-tier cliffs → CDN origin) plus PrivateLink and S3 CRR depth. Deep-links: aws-checklist, s3-ta, cross-az, egress-ingress, free-tier-cliff, s3-r2, path=nat (Mode B), path=cdn (Mode C), privatelink-vs-nat, s3-crr/crr, and twins. No new /compare/* URLs. Rates stay Unknown until verified.