AWS S3 vs Cloudflare R2 Egress Cost Calculator
Compare monthly storage fees, API request charges, and data transfer egress costs between AWS S3 Standard, Cloudflare R2, Backblaze B2, and Wasabi to eliminate cloud bandwidth lock-in.
The Anatomy of Cloud Egress Pricing (The “AWS Egress Tax”)
In hyperscale public clouds like Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure, data ingress is universally free, but outbound data transfer across the public internet is priced at an exorbitant premium. While tier-1 transit providers (such as Cogent, Lumen, and Telia) sell wholesale IP transit for under $0.0005 per gigabyte, AWS bills customers between $0.09 and $0.05 per gigabyte—a gross margin markup exceeding 1,800%.
This economic asymmetry creates the infamous cloud “hotel lock-in”: it is practically free to upload petabytes of machine learning datasets, video assets, or customer backups to AWS S3, but retrieving them incurs budget-breaking bandwidth bills.
Architectural Comparison: AWS S3 vs Cloudflare R2
| Technical Dimension | Amazon S3 (Standard Tier) | Cloudflare R2 Object Storage | Backblaze B2 |
|---|---|---|---|
| Storage Price per GB/mo | $0.023 | $0.015 (35% Cheaper) | $0.006 |
| Public Internet Egress Fee | $0.09 / GB (First 10TB) | $0.00 / GB (100% Free Forever) | $0.01 / GB (After 3x free storage) |
| S3 API Protocol Compatibility | Native Reference Implementation | S3-Compatible (SigV4, Multipart) | S3-Compatible |
| Class A Operations (PUT/LIST) | $0.005 per 1,000 | $4.50 per 1,000,000 | $0.005 per 1,000 |
| Class B Operations (GET/HEAD) | $0.0004 per 1,000 | $0.36 per 1,000,000 | $0.0004 per 1,000 |
| Global Edge Replication | Cross-Region Replication (Paid) | Automatic Global Edge Caching | Regional Data Centers |
Zero-Downtime Migration Runbook: Migrating 50TB from S3 to R2
Migrating multi-terabyte production buckets from AWS S3 to Cloudflare R2 can be executed with zero application downtime using R2’s native Super Slurper or Cloudflare Sippy (Incremental Migration):
1. Dual-Read Incremental Migration via Cloudflare Sippy
Instead of executing a massive batch copy that spikes AWS egress fees all at once, enable Cloudflare Sippy directly on your R2 bucket. When a client requests an object from R2:
- R2 checks if the object already exists in its local bucket.
- If not found (cache miss), R2 transparently fetches the object from your upstream AWS S3 bucket, copies it permanently into R2, and serves it to the client.
- Subsequent requests for that object are served directly from R2 at $0 egress.
AWS S3 to Cloudflare R2 Migration Script (Node.js AWS-SDK v3)
import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";
// Configure client pointing to Cloudflare R2 S3-compatible endpoint
const r2 = new S3Client({
region: "auto",
endpoint: `https://${process.env.CF_ACCOUNT_ID}.r2.cloudflarestorage.com`,
credentials: {
accessKeyId: process.env.R2_ACCESS_KEY_ID,
secretAccessKey: process.env.R2_SECRET_ACCESS_KEY,
},
});
async function uploadAsset(bucketName, key, body, contentType) {
const command = new PutObjectCommand({
Bucket: bucketName,
Key: key,
Body: body,
ContentType: contentType,
});
return await r2.send(command);
}
3-Year Enterprise TCO Modeling across Data Volume Scales
The table below summarizes cumulative 3-year infrastructure spending for companies streaming media or hosting public downloadable datasets with a 2:1 egress-to-storage ratio:
| Scale Profile | Storage / Egress Volume | 3-Year AWS S3 Total Cost | 3-Year Cloudflare R2 Total Cost | 3-Year Net Cash Retained |
|---|---|---|---|---|
| Startup / B2B SaaS | 10 TB Storage / 20 TB Egress | $72,684 | $6,480 | $66,204 (91% Saved) |
| Growth Streaming / Media | 50 TB Storage / 100 TB Egress | $354,600 | $32,400 | $322,200 (91% Saved) |
| AI Training / Large Files | 250 TB Storage / 500 TB Egress | $1,746,000 | $162,000 | $1,584,000 (Saves $1.58M!) |
Frequently Asked Questions (S3 vs R2 FAQ)
Does Cloudflare R2 charge for egress bandwidth under any circumstances?
No. Cloudflare R2 has zero data transfer egress fees across public internet downloads, worker bindings, and third-party cloud routing. You only pay for storage capacity ($0.015/GB-month) and Class A / Class B API requests exceeding the free monthly tier.
Can I use standard AWS CLI and S3 SDKs with Cloudflare R2?
Yes. Cloudflare R2 implements the standard AWS S3 REST API specification, including AWS Signature Version 4 (SigV4). You can configure the AWS CLI, Boto3 (Python), AWS SDK for JS, or Cyberduck simply by overriding the endpoint URL to point to your Cloudflare Account ID.
When is AWS S3 still better than Cloudflare R2?
AWS S3 remains superior if your architecture heavily relies on AWS-native ecosystem features such as S3 Object Lambda, S3 Glacier Deep Archive ($0.00099/GB for cold compliance storage), AWS Athena federated SQL querying, or direct EBS mount points within the same AWS availability zone.
Production Failure Modes in Cloud Object Storage & Dual-Cloud Routing
While migrating from AWS S3 to Cloudflare R2 delivers massive egress cost reductions, cloud architects must engineer around specific consistency, caching, and partition bottlenecks.
1. Hot Partition Throttling on High-Throughput Write Pipelines
In high-volume object storage workloads (such as real-time dashcam uploads, security camera footage, or high-frequency telemetry), uploading thousands of objects per second with sequential timestamps (e.g., /uploads/2026-11-13/08-00-01.jpg) concentrates write load onto a single internal storage partition. This triggers 503 Slow Down throttling errors on AWS S3 and rate-limiting on R2.
Disaster Recovery Runbook:
- Prefix Randomization: Prefix all storage keys with a 4-to-8 character MD5 or SHA-256 hash slice of the object ID (e.g.,
9a2f-uploads/2026-11-13/...). This automatically distributes storage partitions across the distributed storage ring, unlocking over 3,500 PUT and 5,500 GET requests per second per partition. - Enforce Multipart Upload Thresholds: For files exceeding 100MB, always initiate S3/R2 Multipart Uploads with 10MB to 50MB chunk sizes. If a network blip occurs during a 10GB file transfer, only the failed 20MB part needs to be retransmitted, preventing total upload retries.
Terraform / OpenTofu Infrastructure as Code: Dual-Bucket Zero-Egress Architecture
To eliminate cloud vendor lock-in, forward-thinking engineering teams deploy a dual-bucket strategy: AWS S3 serves as the durable canonical backend for cold compliance storage, while Cloudflare R2 serves as the high-throughput, zero-egress public content delivery origin.
Production OpenTofu Configuration for Cloudflare R2 + Custom Domain
terraform {
required_providers {
cloudflare = {
source = "cloudflare/cloudflare"
version = "~> 4.0"
}
}
}
resource "cloudflare_r2_bucket" "production_media" {
account_id = var.cloudflare_account_id
name = "zelobiz-production-assets"
location = "WNAM"
}
resource "cloudflare_r2_custom_domain" "cdn_endpoint" {
account_id = var.cloudflare_account_id
bucket_name = cloudflare_r2_bucket.production_media.name
domain = "assets.zelobiz.com"
zone_id = var.cloudflare_zone_id
}
Real-World FinOps Case Study: Slashing $14,200/mo in AWS Egress by 87%
An enterprise SaaS platform specializing in AI-generated video renders previously stored and distributed all MP4 video downloads directly from AWS S3 standard buckets. As monthly active users scaled, the platform’s infrastructure bill revealed:
- AWS S3 Storage (45 TB): $1,035 / month
- AWS S3 API Operations (PUT/GET): $410 / month
- AWS Public Bandwidth Egress (142 TB): $12,755 / month (89.8% of their entire cloud storage bill!)
- Total AWS S3 Expense: $14,200 / month
The Cloudflare R2 Resolution: The team pointed their frontend video player to Cloudflare R2 via custom CNAME edge domains and enabled Cloudflare Sippy incremental migration. Over 30 days:
- Cloudflare R2 Storage (45 TB): $675 / month
- Cloudflare R2 Egress (142 TB): $0.00 (Zero bandwidth charge!)
- Cloudflare R2 API Class A/B Requests: $1,175 / month
- New Total Monthly Storage Spend: $1,850 / month
- Net Bottom-Line Cash Savings: $12,350 / month ($148,200 saved per year!)
Disaster Recovery & Object Lifecycle Management in Dual-Cloud Architectures
When running a hybrid S3 and R2 multi-cloud architecture, automated lifecycle rules prevent accidental data loss and eliminate redundant storage charges from incomplete multipart uploads:
- Aborting Incomplete Multipart Uploads: In both AWS S3 and Cloudflare R2, if a multipart upload fails or is abandoned mid-stream, the uploaded chunk segments remain in storage indefinitely, quietly accumulating storage fees. Configure an automated lifecycle rule to abort incomplete multipart uploads after 7 days.
- Non-Current Version Expiration: When object versioning is enabled for disaster recovery against ransomware or accidental deletion, retain non-current object versions for 30 to 90 days before permanent purging. This safeguards compliance audit trails without permanently inflating cold storage costs.
AWS S3 Lifecycle Rule Configuration (JSON Policy)
{
"Rules": [
{
"ID": "PruneIncompleteUploadsAndVersions",
"Status": "Enabled",
"Filter": {},
"AbortIncompleteMultipartUpload": {
"DaysAfterInitiation": 7
},
"NoncurrentVersionExpiration": {
"NoncurrentDays": 60
}
}
]
}
AWS S3 Intelligent-Tiering vs Cloudflare R2: Break-Even Economics
AWS often recommends S3 Intelligent-Tiering to automatically transition objects between Frequent Access ($0.023/GB), Infrequent Access ($0.0125/GB), and Archive Instant Access ($0.004/GB). However, Intelligent-Tiering carries critical architectural catches:
- Monitoring and Automation Surcharge: AWS assesses a $0.0025 per 1,000 objects monthly monitoring fee. If you store millions of small 50KB files, monitoring fees completely dwarf storage savings.
- Minimum 128KB Object Size: Objects under 128KB are billed at the full Frequent Access rate and do not transition to cheaper tiers.
- Egress Remains Full Price: Regardless of which tier an object resides in, downloading it over the public internet still incurs the full $0.09/GB egress fee—which Cloudflare R2 completely eliminates at $0.00/GB.