Data Egress vs Replication

Replication is egress.

Overview

Cross-region replication is a form of egress with real per-byte cost, and the cost compounds with replication volume. Enabling cross-region replication is the easy decision; deciding what to replicate (and what to skip) is the discipline that determines whether the DR posture lands at sane cost or at six-figure surprise. Most teams over-replicate by default; the discipline is selective replication matched to actual recovery requirements.

• Replication is egress. Per-replication AWS bills cross-region transfer; the cost is real and compounds with volume.
• Cross-region replication. Per-region pair the data-transfer rate; cross-continent rates are higher than intra-continent.
• Per-resource replication policy. Per-resource the replication scope decided by recovery requirement, not by default-on toggle.
• Selective replication plus quarterly cost review. Per-critical-resource explicit replication; per-quarter cost review catches replication that lost its justification.

The approach

The practical approach is to enumerate per-resource recovery requirements explicitly (RTO and RPO per workload), replicate only what those requirements demand, prefer compression in transit where supported, run quarterly cost reviews against actual replication volume, and document the per-resource replication rationale so the cost is reviewable rather than mysterious.

• Selective replication. Per-critical-resource explicit replication; the rest stays single-region with documented acceptance.
• Per-resource policy. Per-resource replication scope tied to documented RTO/RPO requirements.
• Per-quarter review. Quarterly replication cost review; surfaces resources whose replication outlived their justification.
• Compression in transit plus documented policy. Per-replication compression where supported (S3 replication, RDS replication); per-resource rationale committed to the infrastructure repo.

Why this compounds

Egress-vs-replication discipline compounds across years. Each correctly-scoped replication produces ongoing savings without sacrificing DR posture; each quarterly review catches drift before it becomes a CFO question; the team builds a vocabulary for matching replication to actual recovery requirements rather than to defaults.

• Cost efficiency. Right replication matches DR need; the bill tracks the actual recovery requirement rather than the default-on cost.
• DR posture. Right resources replicated; recovery time matches documented requirements rather than wishful thinking.
• Operational fit. Right policy matches workload; replication scope aligns with the criticality of the data.
• Institutional knowledge. Each policy iteration teaches DR patterns; the team learns the cost-benefit of each replication decision.

Egress-vs-replication discipline is an operational discipline that pays off across years. Nova AI Ops integrates with replication telemetry, surfaces cost patterns, and supports the team’s DR cost discipline.