Cloud Egress Fees in India 2026: Stop Paying to Move Your Own Data

A 12-person logistics firm in Gurugram got a bill last spring that made its founder call his CA before he called his cloud vendor. The compute line looked fine. Storage looked fine. The surprise was a ₹38,000 line item labelled "Data Transfer Out to Internet" for a single month, almost entirely from invoice PDFs and dispatch photos being downloaded by drivers and customers. Nobody had modelled it because nobody had been told it existed. That pattern, repeated across thousands of Indian SMBs, is why cloud egress fees India SMB owners need to understand this line before they sign the next contract.

Here is the uncomfortable fact: in many accounts we audit, data transfer charges quietly account for 10 to 25 percent of the total monthly cloud bill, and they are the line least likely to be reviewed. Providers are generally happy to take your data in for free and charge you to take it back out. For a business whose product is data, that asymmetry matters.

This article walks through what egress actually is, where the charges hide, how they compare across AWS, Google Cloud and Azure for Indian workloads, and the concrete steps that have cut real bills. You will get a worked example, a comparison table, a checklist you can hand to your vendor, and the mistakes we see most often. If you only read one section, read the Key Takeaways below.

Key Takeaways

• Inbound data is almost always free; outbound data to the internet, to other regions and sometimes to other availability zones is billed per GB.
• Egress is often 10 to 25 percent of an SMB cloud bill and is rarely budgeted for, so model it before you migrate.
• Keep compute and storage in the same region and, where possible, the same zone; cross-region replication is a common silent drain.
• Serve static assets and downloads through a CDN, which typically prices delivery lower than raw egress from the origin.
• Check whether your provider's Indian region is actually the cheapest place to host your data for your user base, not just the closest.
• Set budget alerts on the data-transfer SKU specifically, not just on total spend, so a runaway download job shows up in days, not at invoice time.

What exactly are cloud egress fees in India for an SMB?

Egress means data leaving a cloud provider's network. The charge depends on where the data is going. Traffic to the public internet is the most expensive category. Traffic between regions is billed separately, and in some setups traffic between availability zones inside the same region is billed too. Inbound traffic from the internet is generally free on all three major platforms, which is why the cost surprises tend to appear only after an application goes live and starts serving users.

For an Indian SMB the picture has a few local wrinkles. Most of your customers are in Mumbai, Delhi NCR, Bengaluru, Chennai, Hyderabad, Pune and tier-2 cities, so the traffic is domestic, but the provider still bills it as internet egress unless it is routed through a private path or a CDN edge. Pricing is quoted in US dollars, so your ₹ invoice moves with the exchange rate, and GST at 18 percent applies on top for most B2B cloud services billed to Indian entities. A bill that looks like ₹60,000 before tax can be materially different once the rupee moves two or three rupees against the dollar over a quarter.

Practical rule: if data leaves a boundary you have not explicitly priced, assume it is charged until you confirm otherwise.

Where do data transfer charges hide in an AWS, GCP or Azure bill?

The charge is rarely labelled "egress" in a way that jumps out. On AWS it appears under EC2-Other or under the data-transfer usage types in Cost Explorer. On Google Cloud it shows as Network Egress SKUs under Compute Engine or Cloud Storage. On Azure it sits under Bandwidth in the consumption breakdown. Finance teams miss it because it is spread across services.

The usual suspects in SMB environments are:

• Users downloading large files directly from object storage rather than through a CDN.
• Backup replication to a second region for disaster recovery, which doubles storage and adds transfer on every sync.
• Database read replicas placed in a different region from the primary, so every query result crosses a billed boundary.
• Analytics or reporting jobs that pull full datasets to an on-premise machine or a third-party BI tool.
• Logs and monitoring data shipped out to an external SaaS observability platform.
• Staff using a cloud-hosted VM as a file server and syncing large folders to laptops over the internet.

Worked example: how a logistics company cut its cloud bill by 60 percent

Consider a 15-person logistics company in Gurugram that ran its dispatch software, document store and customer tracking portal on a rack of ageing on-premise servers. The server room, power backup, AMC contracts, a leased internet line and occasional hardware replacements came to about ₹45,000 per month. The owner wanted to move to AWS without a surprise invoice.

The first design put the application in ap-south-1 (Mumbai) with the document store in S3 and a read replica of the database in ap-south-2 (Hyderabad) for disaster recovery. Our modelling showed compute and storage at roughly ₹22,000 per month, which looked attractive. The problem was that the document store served scanned proofs of delivery, roughly 40 GB of downloads a day across drivers and customers, all served directly from S3 to the internet. Add the cross-region replica sync and the monthly total came to about ₹41,000 once the transfer lines were included. The migration looked almost as expensive as the status quo.

The fix was three changes. First, the document store was fronted by a CDN, so repeat downloads of the same proof of delivery came from edge caches in Mumbai and Delhi rather than from the origin. Second, the disaster recovery replica was switched from continuous cross-region replication to a nightly incremental snapshot, which cut sync traffic sharply while still meeting the company's recovery target of 24 hours. Third, the tracking portal's logs were filtered to ship only error-level events to the external monitoring tool, instead of every request.

After the changes, the steady-state bill settled at about ₹18,000 per month including GST, against the ₹45,000 on-premise baseline. The owner also dropped the leased line and the AMC contracts, which were not in the cloud comparison at all. The lesson is not that cloud is always cheaper. It is that the transfer line decided whether the migration made sense, and it was invisible until someone modelled it.

How do AWS, GCP and Azure compare on egress for Indian startups?

Pricing changes, and you should verify current rates on each provider's pricing page before committing. The table below compares the criteria that matter for an Indian SMB rather than quoting specific per-GB figures that would go stale.

Criteria	AWS (Mumbai, Hyderabad)	Google Cloud (Mumbai, Delhi)	Microsoft Azure (Pune, Chennai)	Notes for SMBs
Inbound data	Free	Free	Free	All three are generous on ingress
Internet egress tiers	Tiered per GB, first 100 GB/month often free	Tiered per GB, free tier available	Tiered per GB, first 100 GB/month often free	Check the current free allowance; it changes
Cross-region transfer	Billed	Billed	Billed	Keep replicas in-region where recovery targets allow
CDN integration	CloudFront	Cloud CDN	Azure CDN / Front Door	CDN delivery is usually cheaper than origin egress
Local presence for Indian users	Strong, multiple Indian regions	Strong, Mumbai and Delhi regions	Strong, Pune and Chennai regions	Latency is similar; decide on pricing and services
Partner and reseller support in India	Broad partner network	Growing partner network	Broad, with strong enterprise channel	Managed-service partners matter more than list price

In practice, the provider choice matters less for egress than the architecture choice. A well-designed application on any of the three will beat a poorly designed one on the cheapest platform. If you are weighing a switch, read our analysis of whether Indian SMBs should move from AWS or Azure, and check the latest figures in our recheck of AWS and Azure pricing changes before you rely on any rate.

What steps should you take to audit and cut egress costs?

The following walkthrough is what we run in the first two weeks of an engagement. You can do most of it yourself or hand it to your vendor as a brief.

1. Pull 90 days of billing data, filtered to data transfer. On AWS, use Cost Explorer grouped by usage type and look for DataTransfer entries. On GCP, use the billing export to BigQuery and filter on Network SKUs. On Azure, use Cost Analysis filtered to Bandwidth. Export to a spreadsheet and sort by amount.
2. Map each transfer line to a source and a destination. Work out which resource is sending the data and where it is going: internet, another region, another zone, or a third-party service. Most of the money sits in two or three lines.
3. Classify each flow as necessary or accidental. A nightly backup to another region for a regulated dataset may be necessary. A read replica in a second region that nobody queries is accidental.
4. Put static and cacheable content behind a CDN. Documents, images, product catalogues, app bundles and downloadable reports should be served from the edge. Set cache headers sensibly so repeat requests do not return to origin.
5. Co-locate compute and storage. Make sure the application, the database and the object store that talk to each other are in the same region. Where availability zones are billed, place tightly coupled services in the same zone unless you need redundancy.
6. Revisit replication and backup frequency. Match replication to your actual recovery point objective. Many SMBs replicate continuously when a nightly snapshot would meet their stated recovery target at a fraction of the transfer cost.
7. Filter what you ship to third parties. Logs, metrics and traces sent to external tools should be sampled or filtered. Ask what the vendor actually needs.
8. Set alerts on the transfer SKU. Create a budget alert on data-transfer spend with a threshold you would notice in a week, not a month.
9. Re-run the audit quarterly. Transfer patterns drift as features ship. A bill that was healthy in January can be unhealthy by June.

Common Mistake: Treating the free tier as a planning number

Pro Tip / Common Mistake: Many teams model egress against the free allowance and assume they are safe. The free allowance is usually a per-month figure across the account, and it is consumed by background traffic you did not expect: health checks, monitoring agents, package updates on VMs and software licence checks. We have seen a team exhaust its allowance in the first week and then pay for a month of traffic that was entirely internal housekeeping. Model egress from measured traffic, not from the free tier.

How do you decide between a CDN, a dedicated link and simply paying the transfer fee?

Three options usually compete. A CDN is the default for public content and is usually the cheapest per GB for internet delivery. A dedicated private connection, such as AWS Direct Connect, Azure ExpressRoute or Google Cloud Interconnect, makes sense when you move large, steady volumes between your office or a colocation facility and the cloud, because the per-GB rate is lower and the path is predictable. Paying raw egress is fine when volumes are small and unpredictable.

For most Indian SMBs with under a few terabytes a month of outbound traffic, the CDN plus careful architecture is enough. Private links start to pay off when a company is shipping large datasets daily to on-premise systems, such as a manufacturer syncing design files or a hospital chain moving imaging data. Get a quote for both before deciding, because the fixed cost of a private link can outweigh savings at low volumes.

Why does data residency change the egress equation in India?

Data localisation and sector-specific rules shape where you can place data, and that in turn shapes transfer costs. The Digital Personal Data Protection Act, 2023, and its rules, along with RBI directions for payment data and sector guidance for healthcare and insurance, push many businesses to keep primary data in India. That is usually easy with Mumbai or Hyderabad regions. The trouble starts when a compliance-driven design requires an in-country primary and an out-of-country analytics copy, because the transfer between them is billed and the data now crosses a boundary your auditor will ask about.

Map your data classes before you map your architecture. Decide which data must stay in India, which can leave, and which should be aggregated before it leaves. This is also where a sovereign or in-country option can matter. We cover the cost trade-offs in our guide to sovereign cloud costs and choosing the right data region, and what to ask vendors about certification in our piece on sovereign cloud certification.

What should you ask your cloud vendor or partner about egress?

Whether you buy direct from the provider or through a reseller, the questions are the same. Asking them early is cheap; discovering the answers after go-live is not.

• Show me a 90-day forecast of data-transfer spend for our specific architecture, with the assumptions written down.
• Which of our flows cross a region, zone or internet boundary, and which of those are billed?
• Have we placed a CDN in front of every public download path?
• What is our disaster recovery replication frequency, and does it match the recovery target we agreed with the business?
• Are GST and currency conversion included in the forecast I am looking at?
• Which budget alert thresholds are set on transfer spend, and who receives them?
• What is the exit cost if we move this data to another provider later? Egress applies in reverse too.

If you do not have an in-house team to run this review, our IT consulting engagements include a transfer-cost audit as a standard first step, and for migrations we handle the design through cloud migration and managed services. Our team at eDarpan has run these audits for businesses from Pune to Coimbatore, and the pattern is consistent enough that a two-week review usually pays for itself.

Does the cloud still make sense once egress is included?

Often yes, but not automatically. The honest comparison is total cost of ownership, which means hardware depreciation, power, cooling, leased lines, AMC, staff time for patching and backups, against the full cloud bill including transfer, support plan, GST and currency movement. Some workloads, particularly ones that are chatty between systems or that serve large public downloads with little caching, can cost more in the cloud than on a well-run on-premise setup. Others, especially spiky workloads, development environments and anything that needs geographic redundancy, are far cheaper in the cloud than in a server room.

If you are also considering the user-facing side of your stack, transfer cost interacts with the apps you build. A mobile app that pulls large media on every launch can generate egress that no finance model anticipated. Our mobile app development and custom software development teams design payload sizes and caching in from the start for exactly this reason.

Frequently asked questions

What are cloud egress fees in India and why do SMBs get charged for them?

Cloud egress fees are charges for data leaving a provider's network, billed per gigabyte depending on destination. SMBs get charged because providers typically make inbound data free but bill outbound traffic to the internet, between regions, and sometimes between zones. The charge only becomes visible once an application is serving real users and downloads.

How much do data transfer charges add to an AWS or Azure bill for a small business?

In our audits, transfer usually lands between 10 and 25 percent of the total cloud bill for SMB workloads, though it varies widely with architecture. Applications that serve large public downloads without a CDN, or that replicate continuously across regions, sit at the top of that range. Model it from measured traffic rather than assuming a fixed share.

Is it cheaper to host on AWS Mumbai or Google Cloud Delhi for Indian users?

Latency and region pricing are close enough that the choice should rest on your services, your partner support and your data residency needs rather than on a small rate difference. Compare the full bill for your specific architecture, including transfer and GST, on each provider. Check current rates on the pricing pages because they change.

Do I have to pay egress when serving files from S3 or Cloud Storage to customers?

Yes, direct delivery from object storage to internet users is billed as egress, subject to any free allowance. Putting a CDN in front of the bucket usually reduces the cost per gigabyte and cuts repeat requests to origin. Set cache headers correctly so the CDN actually serves the traffic.

Can a CDN reduce cloud egress costs for an Indian e-commerce or logistics business?

Often yes, for any content that is cacheable such as product images, documents, invoices, app bundles and static pages. The savings depend on cache hit rates, so measure them after deployment. Dynamic, per-user responses benefit less from caching and should be designed to minimise payload size instead.

Does data residency rules like DPDP Act 2023 increase egress costs?

They can, indirectly. Keeping primary data in India is usually straightforward with domestic regions, but architectures that copy data out for analytics or to overseas tools create billed transfer and compliance questions at the same time. Map which data classes can leave India before designing the replication and reporting flows, and confirm the approach with your legal or compliance adviser.

What is the first thing to check if my cloud bill suddenly jumped?

Open the billing report, filter to data-transfer SKUs, and sort by amount for the last 30 days. Identify the resource and destination behind the largest line. The usual causes are a new public download path without a CDN, a replication job that was enabled for testing and never turned off, or a log or analytics export that started shipping far more data than planned.

Closing: know your transfer line before it knows you

Cloud egress fees in India are not a hidden trick so much as an ordinary pricing model that catches SMBs because nobody models it. The fix is simple in principle: measure transfer by flow, put public content behind a CDN, keep tightly coupled systems together, match replication to real recovery targets, and watch the transfer line like you watch payroll. Businesses that do this consistently keep their cloud spend predictable enough to plan around, which is the whole point of moving to the cloud in the first place.

If you would like a second pair of eyes on your current bill, eDarpan can run a transfer-cost review and give you a plain-English list of what to change and what it will save. You can contact eDarpan to book one, or learn more about how we work on the about page and across our full services overview. Start with the 90-day billing export this week. The number you find there will tell you more than any pricing page can.

Image credit: Innovate Maryland Emerging Technology Center by MDGovpics via flickr (BY 2.0), sourced through Openverse.