Chapter 87: AWS DataTransfer Online
AWS Data Transfer — and specifically “Data Transfer Online” (i.e. data transfer that happens over the internet or between AWS services while everything is running live, as opposed to offline physical shipping).
Many people think “data transfer” is just one simple line item on the bill, but in reality it is a whole family of different charges, each with its own rules, free tiers, workarounds, and gotchas — and misunderstanding them is one of the top 3 reasons Indian startups get surprise bills in their first 6–18 months.
Let me explain it like we’re sitting together with a whiteboard — slow, clear, step-by-step, full of everyday Hyderabad analogies, actual 2026 pricing numbers (ap-south-1 & ap-south-2), real startup examples, and the exact tricks smart teams use to keep data transfer costs near zero even at scale.
1. First — What do we even mean by “AWS Data Transfer Online”?
AWS Data Transfer = any time data leaves or enters one AWS resource and goes to another place.
But there are many different directions, and AWS prices them very differently:
| Direction / Type | Charged? | Free tier / exceptions (2026) | Typical Hyderabad trap (2026) |
|---|---|---|---|
| Inbound to AWS (someone → your S3/EC2/API) | No | Always free | None — everyone forgets this is free |
| Same-region AWS → AWS (EC2 → S3 same region) | No | Always free | None — very cheap internally |
| Inter-region AWS → AWS (ap-south-2 → us-east-1) | Yes | No free tier — ~₹1.8–2.5/GB | Accidentally using us-east-1 resources |
| Outbound to internet (your S3 → user browser) | Yes | First 100 GB/month free → then tiered (~₹6–8/GB in ap-south-2) | Direct S3 public URLs instead of CloudFront |
| CloudFront → internet | No | Almost all egress free (because data leaves from Edge) | — (this is the big money-saver) |
Golden rule everyone must memorize (2026):
Inbound is always free. Same-region internal traffic is always free. Outbound to the internet is expensive — unless you route it through CloudFront.
2. The Main Types of Data Transfer Charges (With 2026 ap-south-2 Prices)
| Type | Price per GB (ap-south-2, 2026 approx.) | Free amount per month | Typical Hyderabad startup scenario | Monthly damage if you do it wrong |
|---|---|---|---|---|
| Data out to internet (first 100 GB) | Free | 100 GB | Website on S3 → users download photos | — |
| Data out to internet (next 9.999 TB) | ~₹6–8 | — | S3 public bucket, 500 GB egress | ₹3,000–4,000 |
| Data out to internet (next 40 TB) | ~₹5–6 | — | Video platform, 50 TB egress | ₹2–2.5 lakh |
| Inter-region transfer (out from ap-south-2) | ~₹1.8–2.5 | None | Analytics in us-east-1 | ₹9,000–25,000 (for 5–10 TB) |
| Same-region AWS → AWS | Free | Unlimited | EC2 → S3 same region | — |
| CloudFront → internet | Free (most cases) | Almost unlimited | S3 + CloudFront for images/videos | — (this is the big saver) |
3. The #1 Way to Eliminate Almost All Egress Costs (CloudFront)
CloudFront = AWS’s global Content Delivery Network (CDN).
When you put CloudFront in front of S3 (or API Gateway, ALB, etc.):
- Data leaves AWS from Edge Locations (Hyderabad has several) → most outbound data transfer is free
- First byte latency drops dramatically (especially for users in India, Middle East, SEA)
- You get automatic HTTPS + caching + geo-restriction + WAF protection
Hyderabad example – food delivery app
- Before: S3 bucket with menu photos & restaurant images → direct public URLs → 400 GB egress/month → ~₹2,400–3,200 bill just for data transfer
- After: S3 bucket → CloudFront distribution → Same 400 GB now leaves from Edge Locations → egress cost ≈ ₹0 → Images load 2–5× faster → better user experience → Extra: added WAF rules → blocked bots scraping prices
4. Real Hyderabad Startup Pricing Journey (2026)
Your startup “TeluguBites” — restaurant discovery + food ordering
Month 1–6 (learning phase):
- Mostly On-Demand, some us-east-1 experiments
- Bill ~₹35,000–70,000
- Data transfer out ~₹4,000–12,000 (direct S3 + some cross-region traffic)
Month 7 (wake-up call):
- Bill hits ₹1.35 lakh → panic
- Found 60 % of egress was direct S3 → moved everything to CloudFront → egress dropped to ~₹500
- Moved analytics queries from us-east-1 → ap-south-2 → saved ~₹8,000/month inter-region
- Bought Compute Savings Plan → 65 % discount on ECS Fargate & Lambda
- Bill stabilized at ~₹65,000–85,000 for same usage
Lesson learned:
- CloudFront saved ~₹8,000–15,000/month
- Same-region everything saved ~₹5,000–10,000/month
- Savings Plans saved ~₹25,000–40,000/month
Summary Table — AWS Data Transfer Cheat Sheet (2026 – India Focus)
| Type | Charged? | Free amount | Best way to avoid/minimize cost | Typical monthly damage if wrong |
|---|---|---|---|---|
| Inbound to AWS | No | Unlimited | — | — |
| Same-region AWS → AWS | No | Unlimited | — | — |
| Inter-region AWS → AWS | Yes | None | Keep everything in ap-south-2 | ₹5,000–30,000 |
| Out to internet (direct) | Yes | 100 GB | Use CloudFront instead | ₹2,000–50,000+ |
| Out via CloudFront | No | Almost all | Route S3, API Gateway, ALB through CloudFront | — (biggest saver) |
Teacher’s final note (real talk – Hyderabad 2026):
Data transfer is the silent killer of AWS bills in India.
The teams that keep egress near zero are not lucky — they are disciplined:
- Everything goes through CloudFront (images, videos, API responses)
- No cross-region traffic unless absolutely necessary
- VPC endpoints for S3, DynamoDB, Secrets Manager → no NAT Gateway charges
- AWS Budgets alert at 80 % — catches egress spikes early
Do these four things religiously and your data transfer line item will be ₹0–2,000/month even at scale — instead of ₹20,000–1 lakh.
Got it? This is the “how to stop paying AWS to send your own data to your own users” lesson.
Next?
- Step-by-step: Set up CloudFront in front of S3 bucket (with zero egress cost)?
- Deep dive: All the different data transfer rates (intra-region, inter-region, internet, CloudFront) 2026 prices?
- Or how to use VPC endpoints to eliminate NAT Gateway charges?
Tell me — next whiteboard ready! 🚀🌐💸
