AWS India Cloud Infrastructure ProgrammeMumbai and Hyderabad regions · national investment programme
Record PRJ-018National — two live regionsTier A — procurement-relevant15 public sources cross-checked
Two live regionsNo MW publishedCarries no capacityNon-additive
21bn
Cloud/AI, 2026–30
48bn
Amazon India plan
3.7bn
Actually spent to 2022
2
Live regions
2–3GW
Reported ambition
6–8
Colocation LOIs reported
AWS runs two cloud regions in India — Mumbai since June 2016 and Hyderabad since November 2022 — and has committed US$21 billion to Indian cloud and AI infrastructure for 2026–2030, inside Amazon's broader US$48 billion India plan. The number that matters more than any of those: AWS had actually spent US$3.7 billion in India between 2016 and 2022. Every larger figure is a promise, and each one has been replaced by a bigger promise.
1At a glance
Record ID
PRJ-018 — Gridvik India Data Centre Registry
Record
AWS India cloud infrastructure programme — investment programme, not a facility
Operator
Amazon Web Services, a business of Amazon
Regions
Asia Pacific (Mumbai), launched June 2016, API name ap-south-1 — and Asia Pacific (Hyderabad), launched November 2022, ap-south-2, AWS's 30th region worldwide
Current commitment
US$21 billion for cloud and AI infrastructure in India, 2026–2030 — part of Amazon's US$48 billion India plan
Actual spend
About US$3.7 billion in the Mumbai region between 2016 and 2022. Over US$1.3 billion in the Hyderabad region by end-2025
Stated ambition
A reported long-term target of 2–3 GW of Indian data-centre capacity, per industry reporting in March 2026 — not confirmed by AWS
Route to capacity
Reported letters of intent with six to eight colocation providers — Sify, Yotta, NTT Data, CtrlS and CapitaLand among them
Record type
investment_programme — carries no MW and is never summed with facility records
Gridvik tier
A — procurement-relevant, and unusual. AWS is buying Indian capacity through partners as well as building it, which means the buying decisions may not sit in Seattle
2The number ladder — five figures, one actual spend
No company in Indian data centres has had its investment commitment revised upward more often than AWS. Each new figure replaced the previous one; none of them was added to it.
Figure 1AWS and Amazon India investment figures as announced, newest first. The $48 bn and $21 bn announcements are from 2026; $12.7 bn dates from May 2023; $8.3 bn from January 2025; and $3.7 bn is the only figure that represents money actually spent.
What each figure is, and what it is not
Figure
Announced
Covers
Status
US$48 bn
2026
All Amazon businesses in India, 2026–2030
Not DC
US$21 bn
2026
AWS cloud and AI infrastructure in India, 2026–2030
Current
US$12.7 bn
May 2023
AWS cloud infrastructure in India through 2030
Superseded
US$8.3 bn
Jan 2025
Mumbai cloud region build-out
Subsumed
US$3.7 bn
Reported 2023
Actual Mumbai region spend, capex and opex, 2016–2022
Sunk
Gridvik read — the commitment is not a budget line
The US$12.7 billion of May 2023 has not been added to the US$21 billion of 2026. It was replaced. The US$8.3 billion for Mumbai in January 2025 is a regional component of the same envelope, not an extra layer.
This matters because Indian data-centre capacity is routinely projected by summing announcements. Do it here and AWS alone contributes about US$90 billion of 'investment' that describes roughly US$5 billion of actual spend.
The only defensible statement: AWS has spent about US$3.7 bn in Mumbai and over US$1.3 bn in Hyderabad, and has now committed US$21 bn for the years 2026 to 2030. Everything else is a headline.
3Two regions, ten years
Mumbai — ap-south-1
Launched June 2016, AWS's first Indian region. A third availability zone was added in 2019. More than US$3.7 billion invested between 2016 and 2022, covering both capital and operating expenditure on constructing, maintaining and operating the data centres
Hyderabad — ap-south-2
Launched November 2022 as AWS's 30th region globally, with three availability zones from day one. AWS estimated about US$4.4 billion of investment in India by 2030 through this region. More than US$1.3 billion had been invested by end-2025
What two regions buy a customer
For the first time, Indian customers could build genuine multi-region architecture — disaster recovery and data residency without leaving the country. This is the competitive logic against Microsoft's four regions and Google's two
Availability zones
Three per region. Each zone has independent power, cooling and networking, which means the physical build is replicated infrastructure, not additive capacity
Local Zones
AWS has been adding Local Zones in India for low-latency workloads — small footprints, not material to capacity totals but relevant to edge equipment demand
What is not published
Capacity in MW for either region, building counts, square footage, substation ratings and tenancy. AWS has published none of it in ten years of Indian operation
4The 2–3 GW ambition and the colocation route
The most commercially important unreported fact in Indian data centres
In March 2026, industry reporting stated that AWS is targeting a long-term scale-up to 2–3 GW of capacity in India after the government declared a 20-year tax holiday for cloud companies — and that AWS had signed letters of intent with six to eight Indian colocation providers, including Sify Technologies, Yotta Data Services, NTT Data, CtrlS and CapitaLand.
This is not confirmed by AWS and Gridvik does not carry the 2–3 GW as a fact. But if the reporting is even directionally right, it changes the entire competitive map for vendors in this market.
What the reported model implies
AWS taking large blocks of Indian operators' capacity rather than building every megawatt itself. Evidence for this already exists: AWS leased land in Navi Mumbai in 2023 on a 180-month term with an expansion option, and reports circulate of colocation letters of intent across multiple providers
Why it matters to a vendor
The buyer changes. In a self-build, the specification authority and purchase order are both AWS. In a colocation deal, the Indian operator buys the equipment to AWS's design. For most Indian suppliers the colocation route is far more accessible — Sify, NTT, CtrlS and Yotta are procureable accounts in a way that AWS Seattle is not
What it means for capacity accounting
Capacity that AWS leases from an Indian operator may be counted twice in market reports — once as the operator's capacity and once as AWS's regional footprint. This is the single largest source of double counting in Indian data-centre statistics
The tax trigger
The 20-year tax holiday for cloud companies is the stated policy trigger. It is a demand-side incentive that favours exactly this build-vs-lease decision
Gridvik's handling
The 2–3 GW figure is recorded as a reported ambition, unconfirmed. The letters of intent are recorded as reported. Neither is entered as capacity in this registry
5Timeline
AWS launches its Asia Pacific (Mumbai) region — its first infrastructure region in India.
A third availability zone is added to the Mumbai region.
The Asia Pacific (Hyderabad) region launches with three availability zones as AWS's 30th region worldwide. Estimated investment of about US$4.4 bn in India by 2030 through that region.
AWS announces US$12.7 bn of planned Indian cloud infrastructure investment by 2030, on top of US$3.7 bn already spent in Mumbai since 2016.
AWS signs a land lease in Navi Mumbai for a data centre — 180 months from August 2023, with an expansion option.
AWS announces US$8.3 bn to build out its Mumbai cloud region.
Industry reporting states AWS is targeting 2–3 GW of Indian capacity and has signed letters of intent with six to eight colocation providers, after a 20-year tax holiday was declared for cloud companies. Not confirmed by AWS.
Groundbreaking at Bharat Future City, Hyderabad, inside a ₹60,000 crore Telangana commitment — recorded separately as PRJ-017.
AWS commits over US$21 bn to Indian cloud and AI infrastructure for 2026–2030, within Amazon's US$48 bn India plan.
6Procurement
Read this before the table
This record has no facility. It sets the funding and the structure for AWS's Indian buying, and the structure is the interesting part: some is self-build, some is leased from Indian operators. Everything below is a Gridvik estimate.
Procurement window and scope
Gridvik assessment · 22 Oct 2026
Order window
2026 to 2030. The US$21 bn commitment covers exactly these five years, and the reported 2–3 GW ambition runs over a similar horizon. Phase one of the Bharat Future City campus (PRJ-017) lands around mid-2028, and colocation blocks with Indian operators could move faster than that.
Procurement heat
Very high — but split across two very different buying models. Self-build capacity is procured by AWS through global frameworks. Leased capacity is procured by the Indian operator.
Who buys
Two sets of buyers. AWS for the self-build. For the reported colocation blocks: Sify, Yotta, NTT Data, CtrlS and CapitaLand — and those five names are far more actionable for an Indian vendor than AWS is, because they place equipment orders in India through Indian procurement teams
DG / gensets (indicative)
Not estimable. AWS publishes no capacity, and the 2–3 GW figure is unconfirmed. If it is even approximately right, the implied genset requirement across ten years would run into the thousands of units — but Gridvik will not put a number on an unconfirmed capacity ambition
UPS (indicative)
AWS has moved toward distributed/rack-level power with battery at the rack in its newer designs, reducing centralised UPS content per MW. Relevant for any vendor whose India pitch is built on large centralised UPS
Cooling (indicative)
Not published for India. AWS has deployed direct-to-chip liquid cooling for its own AI training fleet globally. Indian capacity, whether self-built or leased, is increasingly specified for high-density AI rather than enterprise colocation — which shifts the requirement toward liquid cooling, CDUs and non-evaporative heat rejection
Categories in scope
HV substations and switchgear · DG and gensets · distributed power and rack battery · CDUs and liquid cooling · high-density racks · CRAH and fan walls · dry coolers · busway · structured cabling and optics · fire and suppression · leak detection · BMS/DCIM · water treatment and reuse · renewables and storage
Decision role
Public decision roles — in GridFeed
Stage-change history
Dated change log — in GridFeed
All estimates are labelled as estimates. No tender dates claimed, no private contact data published.
Region launches and API names, availability-zone counts, the $3.7 bn, $1.3 bn, $12.7 bn, $8.3 bn, $21 bn and $48 bn figures with their announcement dates and perimeters, the Navi Mumbai lease term, and the reported 2–3 GW ambition and colocation letters of intent
What is derived
Only the procurement section and the observation about double counting
Capacity
None recorded. AWS has published no MW in ten years of Indian operations. The 2–3 GW figure is recorded as a reported ambition with its source type stated, not as a capacity entry
Additivity rule
Non-additive. Carries no MW. This programme funds the Bharat Future City campus (PRJ-017) and any leased colocation capacity. It is never summed with either
Investment handling
The figures form a series of superseding commitments, not a stack. Gridvik presents them as a ladder in time and states explicitly that they are not additive
Currency
Reported in both INR and USD by AWS. Gridvik uses the fixed quarterly reference rate of ₹88.40 per USD
8Limits and open questions
Capacity
No MW published for either region, at any point in ten years. The only regional capacity statements are third-party estimates
The 2–3 GW ambition
Reported by one outlet from unnamed sources. Not confirmed by AWS. Not carried as a registry figure
Colocation letters of intent
Reported as letters of intent with six to eight providers. An LOI is not a contract, and none of the parties named has confirmed an agreed capacity block
Double counting risk
Leased capacity may appear both in an Indian operator's total and in AWS's regional footprint. No public source reconciles this
Mumbai region capacity
Unknown, despite ten years of operation and US$3.7 bn of spend
Hyderabad region capacity
Unknown. More than US$1.3 bn invested by end-2025 against an estimated US$4.4 bn programme
Bharat Future City capacity
Not confirmed by AWS — see PRJ-017 for the rejected 1,200 MW claim
What we will not claim
No capacity, no per-region allocation, no confirmation of the 2–3 GW target, and no equipment budget
9Sources
This record was compiled entirely from publicly available sources, cross-checked against one another.
AWS press releases (2016, 2022, 2023)·AWS Builder Center, India background·About Amazon India·Economic Times Datacenters·ET Energyworld·ET Brand Equity·Reuters·Times of India·Livemint·Deccan Herald·Outlook Business·CNBC TV18·Indian Express·DatacenterDynamics·MLQ.ai
Gridvik does not publish source URLs on record pages; citations are retained in the internal source register and are available on request.
What this page is, and what it is not
This is a public-source record of an investment programme and a cloud footprint. Announcement dates and perimeters are attributed to AWS; the capacity ambition is attributed to the reporting that disclosed it.
The procurement section is labelled as estimation. No tender insider information, no private contact data, no operator-paid placement. Corrections are free and published with a date.
