AWS says access to struck data centers cannot be restored — siting risk now tests capex assumptions
AWS plans 36-building data center campus in Indiana County, Pennsylvania
AWS plans 36-building data center campus in Pennsylvania
Shut up and take our money: Amazon plows $1B+ into quashing datacenter dissent
Amazon pours $1B+ into quashing datacenter opposition
AWS drops non-disclosure agreements for data center projects
AWS drops non-disclosure agreements for data center projects
Amazon secures Uzbekistan’s Uztelecom as partner for Amazon Leo satellite service
Amazon signs Uzbekistan's Uztelecom as Amazon Leo partner
Amazon signs PPA with Constellation for Maryland nuclear plant
Amazon signs PPA with Constellation for Maryland nuclear plant
Synopsys and Amazon sign $1bn multi-year IP agreement for custom chip development
Synopsys and Amazon sign $1bn multi-year custom chip IP deal
Prysmian, Rio Tinto to supply Amazon data center in Ohio with low-carbon aluminum
Prysmian and Rio Tinto to supply an Amazon Ohio DC with low-carbon aluminum
AWS says wartime damage means some Middle East cloud resources are gone for good
AWS: some Middle East cloud resources are gone for good
AWS “unable to restore access” to data centers hit by Iran strikes
AWS says it cannot restore access to data centers hit by strikes
The leading-indicator reading here is that data center siting risk has surfaced, for the first time, in the form of "cannot be restored." Signals on the capex_dc axis have so far tracked supply-side constraints — power, land, GPU availability. This one is different in kind: it is downside risk to assets already built. Hyperscaler capex has accelerated on the assumption that capacity, once built, fills up; geopolitics now sits on top of that assumption as a new variable.
The reading splits two ways: (a) this is treated as a localized exception and buildout plans are left unchanged, or (b) region design and redundancy requirements are raised, structurally lifting the investment cost per region. Under (a), the trajectory of total capex is unchanged and the impact stays within insurance and provisioning. Under (b), securing the same capacity costs more, and published capex guidance gets consumed by redundancy rather than by capacity.
Three things to watch next: (1) whether AWS records an impairment or special charge at its next quarterly disclosure; (2) whether other hyperscalers begin addressing siting and redundancy policy; and (3) whether customers' multi-cloud and multi-region requirements start showing up in procurement terms. Point (2) in particular is the dividing line between a one-off event and a rewriting of industry-wide assumptions.