Planned Renewable

Amazon Web Services — India Expansion (Rajasthan AI Campus)

Jaipur, Rajasthan, India

Capacity
150MW
Operator
Amazon Web Services
AI Focus
Training, Inference (AI India initiative, AWS Bedrock India)
Year
2026

Amazon Web Services has announced major expansion of its India cloud footprint as part of the company’s commitment to invest over $12.7 billion in India by 2030. This includes expansion beyond the existing Mumbai (ap-south-1) and Hyderabad (ap-south-2) regions, with additional Indian capacity being explored in partnership with state governments.

The Rajasthan government has actively courted hyperscale data center investment, offering land, power infrastructure development, and favorable data center policy. AWS’s India expansion aligns with the Indian government’s Semicon India program and the broader push to make India a global AI infrastructure hub.

India’s data center demand is driven by the rapid growth of UPI-based digital payments, expanding internet penetration (700+ million users), government digital services (DigiYatra, Aadhaar-based authentication), and a large AI startup ecosystem in Bangalore, Hyderabad, and Pune. AWS AI services including Bedrock (with Indian language model support) and SageMaker are experiencing strong growth in India’s enterprise segment. The expansion supports India’s ambitions under the AI Mission to deploy large-scale AI infrastructure for strategic national applications.

Reference Metadata

Country
India
Region
Rajasthan
City
Jaipur
Status
Planned
Timeline Year
2026
Location Precision
City
Machine-readable record
JSON GeoJSON

Browse This Facility Through The Index

Entry pages are the atomic records in the index. Use the JSON endpoint for programmatic access, then move through the taxonomy links to the broader operator, country, energy, and timeline views that contextualize this facility.

Related Facilities

Nearby slices in the index that share the same operator, geography, build phase, or AI profile. Use these to move laterally through the buildout instead of jumping back to the full directory.

Follow the buildout feed