Ohio already has 125 local data center moratoriums. Early results from its 21 ballot measures on AI infrastructure have determined there will be more

Ohio voters rejected or restricted data-center projects in at least 14 municipalities, with residents across 18 municipalities voting on 21 measures; results in Oregon were not yet available. The state has more than 200 operational data centers, and companies plan to invest up to $40 billion in AI infrastructure there by 2030, but polling found 55% of Ohio adults opposed data-center construction and 65% opposed tax breaks for it. The results highlight local permitting, tax-break and power-supply risks for planned projects, without establishing the fate of every development.

Analysis

The investable risk is not an immediate hit to Amazon’s consolidated earnings; it is a higher and less predictable cost of securing incremental power and sites. Local restrictions can turn tax incentives into enforceable community benefits, financial guarantees, noise limits, or developer-funded utility upgrades—each reducing project returns and lengthening permitting. The burden is asymmetric for hyperscalers: they can redirect some future capacity, but relocation may add time and grid-connection costs while competing for a narrower set of permissive sites. Local vetoes therefore look more like a cap on the pace and economics of marginal capacity than evidence that AI demand disappears.

For AMZN, the cited project outcomes do not establish a material change to AWS’s committed spending or existing construction; do not extrapolate them to the company’s full buildout. The near-term market risk is sentiment and a higher policy-risk discount on AI capex, while the 1–3 month catalyst is whether other states adopt comparable restrictions or require developers to bear more grid costs. Over 6–18 months, the key question is whether capacity shifts to alternative jurisdictions or is actually delayed. Power and cooling-equipment suppliers could benefit from relocation and grid-upgrade spending, but that is conditional and may be offset by project deferrals.

Contrarian point: visible local opposition may improve project terms rather than stop investment. If developers secure predictable approvals by paying for infrastructure and limiting local impacts, the result could be modestly higher costs but lower execution uncertainty. No evidence here establishes a material AMZN earnings revision.

Key Decisions for Investors

• No immediate AMZN short on this signal alone. Treat it as a policy-risk watch item; the local measures cited do not establish the scale of any change to AWS’s committed or consolidated capex.
• Track AMZN disclosures and state/local permitting for evidence of delayed AWS capacity, higher project costs, or reduced tax incentives. Reassess only if restrictions spread across major buildout markets or management changes capex or capacity guidance.
• Watch for upside exposure in grid and data-center infrastructure suppliers if projects relocate or developers fund more grid upgrades; require evidence of orders and backlog conversion before expressing the theme as a trade.
• Falsification: the risk thesis weakens if affected projects obtain approvals on schedule, replacement sites absorb planned capacity without meaningful delay, and AMZN’s AWS capacity or capex guidance remains intact.