AWS puts a delivery date on the Saudi AI Zone: first 50MW by 2028
The first 50MW gets a 2028 date and the cloud region a December 2026 launch; the power plan behind both is still missing.
As Data Center Dynamics reported from LEAP in Riyadh in late August, AWS and its local partner Humain finally attached a delivery date to the Saudi AI Zone: the first 50MW of capacity will come online by 2028. For procurement teams and construction lenders, the date finally turns the zone from a pledged envelope into a schedule they can plan around, and it lands nearly a year after the pair said around 150,000 AI chips would be deployed at the site — a mix of Nvidia GB300s and AWS's own Trainium processors — and a year and a half after the zone was announced with roughly $5bn of pledged investment, none of it accompanied by a construction schedule.
Fifty megawatts is a meaningful block of AI capacity, but it sits at the front end of a much larger vision, and the qualifier 'first' implies another tranche without saying when that tranche arrives. The restraint looks deliberate: sovereign AI projects tend to promise everything at once, whereas AWS has sequenced the zone into phases, the right way to build when grid access, local supply chains and regulatory sign-off are the binding constraints. That first 50MW is effectively a proof load, demonstrating the connections, approvals and construction chain before the full $5bn envelope is committed to the ground.
Pledges in the Gulf have a way of floating free of schedules, but an in-service date converts part of that pledge into a gate against which spending can be measured. The money still has to be spent, and the zone still has to prove it can attract enough demand to justify later phases; the dated tranche gives the project a concrete deliverable, and concrete deliverables are how infrastructure gets underwritten.
Region in 2026, zone in 2028
Sequencing extends to AWS's other Saudi promise: the $5.3bn cloud region first announced in March 2024 remains on track to go live by December 2026, which means a live region will precede the zone's first tranche by more than a year. A region can open with less power online; the chip-heavy AI Zone is waiting on something slower than construction. None of this diminishes the cloud region milestone, since the region is the revenue-producing asset, while the zone's 50MW is anchor load and demonstration.
Matt Garman, AWS's chief executive, tied the effort to Saudi Arabia's Vision 2030, saying the full-stack cloud and AI infrastructure would help 'power new industries, create jobs.' That language is familiar in sovereign infrastructure deals; the deadlines are the unfamiliar part. AWS is on record with two schedules — a regional launch in December 2026 and an AI Zone tranche by 2028 — and both can be tracked and both can slip.
The missing power plan
The missing piece is power. Data centers are moving from grid tenants to power owners, and the AI buildout now runs on state power politics: front-end costs and approval queues, not capital, decide where hyperscale capacity gets built. The disclosure does not say whether the AI Zone draws from the Saudi grid, builds dedicated generation, or pairs with renewable projects behind the meter. For 50MW, several paths are plausible, but every later phase compounds that decision, and the public absence of a power plan leaves the project's largest risk unspoken.
The Gulf backdrop makes every scheduled date worth extra scrutiny: Data Center Dynamics reported that AWS's Bahrain data centers have been repeatedly damaged during the Iran War, and the company still lists its UAE cloud region as disrupted and severely impacted since early March 2026. The same report lists no Saudi disruption, and conflict risk in Bahrain or the UAE should not be assumed to transfer automatically to Riyadh; still, the track record changes the underwriting frame, and a 2028 target in a region where AWS has already taken hardware losses is not the same as one in Ohio.
For investors, the LEAP announcement is progress because it shrinks the AI Zone to a manageable first commitment. AWS could have repeated the 150,000-chip statistic and announced nothing; instead it named a first tranche it appears prepared to deliver. The next disclosure that matters is not another chip count but the energy procurement behind that first tranche; that contract, more than the delivery date, will tell the market whether the zone is infrastructure or aspiration.