multi-cloud · Educational

Cloud egress: AWS vs GCP multi-cloud path templates

Q: Is replication the same as user egress?

Usually no. Replication/multi-region bucket meters should stay on separate lines.

AWS and GCP meter Internet, cross-AZ / inter-zone, inter-region, interconnect (DX / Interconnect), and object-replication paths with different vocabulary. Map the same workload onto matching path templates first — then decode opaque AWS lines via the Cost Explorer decoder and keep S3 CRR / multi-region replication on its own line. Unknown until verified; never one blended $/GB.

Updated 2026-09-16

Map the same workload across AWS and GCP path templates so FinOps reviews compare apples to apples.

Path matrix: AWS vs GCP multi-cloud egress path templates (educational)
Path class	AWS lens	GCP lens	Notes
Internet egress	EC2/S3/ELB SKUs; tiered	Compute/Cloud Storage; tiered	SKU names differ — map by path
Same-zone / same-AZ	Often free in AZ	Same-zone often free	Confirm product exceptions
Cross-AZ / cross-zone	Cross-AZ charges common	Inter-zone pricing on many products	HA designs multiply bytes
Cross-region	Inter-region DT	Inter-region / multi-region bucket	Replication ≠ user egress
Premium vs standard network	Internet vs backbone nuances	Premium Tier vs Standard Tier	Latency vs $/GB tradeoff

Provider source footnotes

AWS EC2 on-demand pricing (data transfer) — as-of 2026-09-09 Unknown until verified
GCP network pricing — as-of 2026-09-09 Unknown until verified
GCP Cloud Storage pricing — as-of 2026-09-09 Unknown until verified

Dated starting points only — Unknown until verified means no invented $/GB. PipeToll does not scrape private consoles or guarantee figures.

Generic pricing pages collapse distinct meters. PipeToll uses multi-cloud path templates so FinOps reviews compare the same traffic shapes — including Internet egress, cross-AZ / inter-zone, and cross-region edges. Keep unverified rates Unknown until verified.

Path templates to model

API responses to mobile clients — Internet egress from regional compute or LB.
Multi-AZ / multi-zone database replicas — cross-AZ chatter can exceed user-facing egress.
Object replication — separate meter from end-user downloads.
Analytics export to partner bucket — cross-cloud: source egress + destination ops.
Premium vs standard Internet path — tier choice is part of the template.

Common traps

One Internet $/GB across clouds — Comparing only Internet egress $/GB ignores NAT gateways, LB bytes, premium network tiers, and hybrid interconnect ports. Align path templates first on this matrix.
Inter-zone = cross-AZ without product checks — Assuming GCP inter-zone equals AWS cross-AZ without product checks misprices HA. Sibling depth: cross-AZ vs cross-region.
Replication blended with user Internet — Treating multi-region bucket / S3 CRR bytes as user Internet egress double-counts durability traffic. Keep replication on its own Mode A line.
Opaque CE labels pasted into GCP cells — Opaque AWS Cost Explorer labels need the CE decoder before cloud-to-cloud arithmetic. Decode Internet, InterZone, ELB, NAT, DX, CRR first.
ELB cross-zone pasted into GCP inter-zone — Pasting ALB/NLB cross-zone GB into a GCP inter-zone cell invents a false peer — use the ELB spoke and ?path=elb-xz.
Dual-running months ignored — Migrations that ignore dual-running egress understate cutover months. Free-tier cliffs on each cloud stay separate via AWS cliff and multi-cloud cliffs.
Scorecrowns from Incomplete — No scorecrowns from Incomplete cells — badge Unknown until verified. No guaranteed savings from switching clouds.

FinOps checklist

Draw one diagram; label Internet, inter-zone/cross-AZ, inter-region, interconnect, and replication edges.
Pull 90-day bytes per edge from both clouds (or estimates).
On the AWS side, map Cost Explorer / CUR talkers with the CE decoder (Internet, InterZone, ELB, NAT, PrivateLink, DX, S3 CRR, CloudFront) before pasting rates.
Price each edge with dated sources; badge Unknown otherwise. Keep S3 CRR / multi-region replication off the Internet line.
Include NAT/LB SKUs and hybrid DX / Interconnect vs Internet when paths use them; sibling VPC endpoints vs NAT.
Reference cross-AZ spoke, multi-cloud free-tier cliffs, calculator (?mode=gb&path=aws-gcp), methodology.

FinOps-lite Unknown until verified

Worked example (educational): same 4 TB Internet + 1 TB inter-zone

Hold workload shape fixed: 4,000 GB Internet responses + 1,000 GB inter-zone/cross-AZ chatter — two Mode A runs, AWS lens then GCP lens.
On AWS, confirm which Cost Explorer lines carry the bytes via the CE decoder before pricing; do not paste one Internet tier into InterZone or ELB cells.
Premium / Standard network tiers can change Internet $/GB — treat tier as part of the path template.
If multi-region object durability is in scope, add a separate replication line (AWS S3 CRR ≠ GCP multi-region bucket meters) — never blend into Internet.
Optional AWS-only: ALB/NLB cross-zone GB is a different meter from instance InterZone — see ELB cross-zone.
Educational only; not a migration savings guarantee. Rates stay Unknown until verified.

Numbered AWS vs GCP fixed-shape stack — Unknown rate cells
#	Path class	Volume	AWS lens	GCP lens
1	Internet responses	4,000 GB	Unknown DT-out $/GB	Unknown egress $/GB (tier matters)
2	Inter-zone / cross-AZ chatter	1,000 GB	Unknown InterZone	Unknown inter-zone
3	ELB cross-zone (AWS-only, if any)	as measured	Unknown — ?path=elb-xz	n/a (no ELB SKU)
4	Replication / multi-region durability	as measured	S3 CRR separate	dual/multi-region separate
5	Hybrid interconnect sibling	500 GB example	DX private transfer	Interconnect private transfer

Second educational stack: 500 GB hybrid interconnect (AWS Direct Connect / GCP Interconnect private transfer) vs 500 GB Internet DT-out for the same payload — port hours and private-transfer SKUs are different meters; see DX / Interconnect vs Internet. Open Mode A with ?path=aws-gcp&gb=5000 for the combined Internet+InterZone shape, and ?path=cross-az&gb=1000 when isolating cross-AZ. Knit ELB labels in the CE decoder before blending. No savings guarantee.

Worked-estimate sensitivity (educational)

Hold the 4 TB Internet + 1 TB inter-zone/cross-AZ baseline and walk three multi-cloud path-class runs. Internet $/GB, inter-zone $/GB, and hybrid private-transfer fees stay Unknown until dated provider cites — literacy arithmetic, not a migration quote or ROI.

Run A — Fixed-shape split: 4,000 GB Internet on Mode A (?path=aws-gcp) plus 1,000 GB inter-zone/cross-AZ on a second Mode A line (?path=cross-az). Never blend into one cell; decode AWS CE talkers first via the CE decoder.
Run B — Inter-zone-only twin: same month with zero Internet responses but 1,000 GB (or larger) HA chatter still bills. Re-run cross-AZ Mode A alone; sibling depth on cross-AZ vs cross-region. Do not paste ELB cross-zone GB into a GCP inter-zone cell.
Run C — Hybrid interconnect sibling: 500 GB AWS Direct Connect / GCP Interconnect private transfer vs 500 GB Internet DT-out for the same payload — port hours and private-transfer SKUs displace some Internet $/GB, not replication. Sibling DX / Interconnect vs Internet; free-tier cliffs for Internet leave sit beside Run A via AWS cliff and multi-cloud cliffs.

Sensitivity runs — Unknown rates (educational)
Run	What changes	Meters to keep visible	Unit rates
A	4 TB Internet + 1 TB inter-zone split	Internet · inter-zone/cross-AZ (separate Mode A)	Unknown
B	Inter-zone-only twin (0 Internet)	HA chatter / InterZone only	Unknown
C	500 GB hybrid interconnect sibling	DX/Interconnect private · residual Internet · cliffs beside A	Unknown

Cross-read S3 vs GCS, S3 CRR, ELB cross-zone, DX / Interconnect, and methodology. Badge every unverified rate Unknown until verified. No savings guarantee from switching cloud logos.

Open calculator Mode A (aws-gcp · 5 TB) Mode A · 1 TB cross-AZ Mode A · ELB cross-zone ELB cross-zone spoke Cost Explorer decoder S3 CRR spoke Mode A · 4 TB Internet Mode A · 1 TB inter-zone twin DX / Interconnect

FAQ on this path

Can I compare AWS and GCP using one $/GB?

No. Map identical path templates first (Internet, inter-zone, inter-region, interconnect, replication), then apply each cloud’s dated rates.

Do premium network tiers matter?

Yes. Latency and $/GB tradeoffs differ. Treat tier choice as part of the path template.

Is replication the same as user egress?

Usually no. Replication / multi-region bucket meters should stay on separate lines — see S3 CRR for the AWS durability twin.

How do opaque AWS Cost Explorer lines fit a multi-cloud compare?

Decode AWS talkers first with the CE decoder (Internet, InterZone, ELB, NAT, PrivateLink, DX, S3 CRR, CloudFront), then map each decoded path to the matching GCP template before Mode A arithmetic.

Where does Direct Connect / Interconnect sit?

Hybrid interconnect port hours and private transfer are different meters from Internet DT-out. Sibling spoke: DX / Interconnect vs Internet.

Is ALB/NLB cross-zone the same as GCP inter-zone?

No. ELB cross-zone is an AWS load-balancer meter; GCP inter-zone is a compute/network path class. Keep ELB GB on the ELB cross-zone spoke and deep-link ?path=elb-xz — never paste it into a GCP inter-zone cell.

Which calculator path alias?

Use ?path=aws-gcp for the multi-cloud Internet / inter-region template; isolate cross-AZ with ?path=cross-az.

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.