{"resourceId":"fortune-ohio-data-center-ballot-bans-20261104","versions":[{"version":"external-5f43e0e8b744da4f930c92e3ec25c1db2cf49ae7ed5484d9582d795154046aed","resource":{"id":"fortune-ohio-data-center-ballot-bans-20261104","title":"Fortune: At least 14 Ohio municipalities pass data-center bans or restrictions after Nov 3; Sunbury and Trenton measures cite Amazon/AWS projects","organization":"Fortune","sector":"National business journalism","geography":"United States (Ohio municipalities; national context)","publishedAt":"2026-11-04","publicationDate":"2026-11-04","eventDate":"2026-11-03","sourceName":"Fortune","sourceLabel":"Ohioans overwhelmingly oppose data centers. 21 ballot measures just put their ire to the test","sourceUrl":"https://fortune.com/2026/11/04/ohio-data-center-ballot-measures-midterm-elections/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["infrastructure","governance-procurement","operating-model"],"finding":"Fortune reports that Ohio voters rejected the AI buildout almost everywhere it was on the ballot November 3, with at least 14 municipalities passing bans or other restrictions on data centers, after 21 ballot measures across 18 municipalities—more than half of 41 data-center-related measures nationwide. In Sunbury, a charter amendment banning data centers using 25 megawatts or more appears to have passed with 100% of the unofficial vote counted, aimed at a possible hyperscale Amazon project whose fate remains unclear per NBC4. In Trenton, a ban passed 80% to 20%; organizers hope it keeps an 18-building Amazon Web Services data center out of the city, though it likely will not affect a four-building AWS campus already under construction nearby, citing Journal-News. Fortune also notes Ohio ranks fifth among U.S. states in operational data centers and cites state data that companies plan to invest up to $40 billion in AI infrastructure in the state by 2030.","sledRelevance":"Statewide pattern of local AWS/Amazon-relevant siting constraints in Ohio after the midterms; complements single-city Trenton detail and prior KUOW/Dealroom coverage with a Fortune statewide roll-up.","evidence":"National business press synthesizing local results; some figures attributed to Ballotpedia, NBC4 and Journal-News.","architectureImplications":"No cloud architecture change; physical infrastructure and power thresholds (>25 MW / >20 MW in some measures) dominate.","governanceImplications":"Local charter amendments and referendums create patchwork constraints; no statewide Ohio ban stated.","securityPrivacyImplications":"None reported for cyber.","caveats":"Some results described as unofficial; Amazon project fate in Sunbury unclear; poll numbers are separate from ballot outcomes.","streamIds":["aws"],"roles":{"sales":"Use Fortune's Ohio roll-up to show siting risk is multi-municipality, not a single Trenton story. Name Amazon and AWS examples only as Fortune reports them: a possible hyperscale Amazon project in Sunbury and Trenton AWS campuses. Do not invent statewide capacity-loss percentages from this article alone. Separate cloud-service availability from local permitting. A bounded engagement is an Ohio municipal-risk map for public-sector cloud stakeholders, with unofficial-result caveats where Fortune uses them and a refresh plan for contested sites.","engineering":"Fit for capacity planning and government-affairs inputs to AWS public-sector programs, not for Bedrock code changes. Keep application architectures on AWS Regions and treat local campus projects as separate dependencies. Prerequisites include an inventory of Ohio campus dependencies and a rule distinguishing Region from campus. Constraints are a patchwork of greater-than-25 MW bans and related voter gates. This is political and land-use risk, not a CVE finding. Proof of value is a dated risk map covering Fortune's municipality claim with AWS/Amazon mentions flagged and Sunbury fate marked unclear.","delivery":"Build an Ohio municipal outcomes table from Fortune plus local primary refresh for AWS-linked sites. Dependencies include government affairs and local reporting updates. Ownership sits with infrastructure strategy; sellers use approved wording only. Skills needed are ballot-measure literacy and attribution discipline. Governance checkpoints: no overstated capacity-at-risk metrics without cited analysts, and no mixing of poll numbers with election results. Acceptance proposals: table includes Sunbury and Trenton Amazon/AWS notes; unofficial-result caveat present; publication date cited. Risks include overgeneralizing Ohio to all states and stale municipal status."},"roleDetails":{"sales":{"customerProblem":"Ohio's midterm produced a cluster of local data-center bans that Fortune ties in part to Amazon/AWS projects in Sunbury and Trenton.","stakeholders":["Government affairs","Infrastructure planner","State/local public-sector account team"],"discoveryQuestions":["Which Ohio municipalities in our pipeline now have bans or voter gates?","Do any customer commitments assume Amazon/AWS campus build timelines there?","How do we refresh unofficial results?"],"valueHypothesis":"A multi-city risk map may prevent single-story bias and overconfident Ohio campus timelines.","potentialEngagement":"Ohio municipal outcomes briefing with Amazon/AWS-linked examples as Fortune states them.","unsupportedClaims":["Guaranteed statewide moratorium","Quantified AWS capacity loss from Fortune alone","Cybersecurity implications"]},"engineering":{"fit":"Fit for Ohio siting and capacity conversations supporting AWS public-sector work.","architectureIntegration":"Keep application architectures on AWS Regions; treat local campus projects as separate dependencies.","prerequisites":["Municipal outcomes inventory","Primary local sources for contested sites","Region vs campus design rule"],"constraints":["Unofficial counts in places","Patchwork local law","Amazon Sunbury fate unclear"],"security":"Not a cyber finding; land-use and political risk as reported.","proofOfValue":["Map lists Fortune's 14+ municipality claim with date","Sunbury and Trenton Amazon/AWS notes attributed","Unofficial caveat where Fortune uses it"]},"delivery":{"work":"Produce Ohio outcomes table and socialize with account teams.","dependencies":["Fortune article","Local primary refresh","Government affairs"],"ownership":"Infrastructure strategy owns the map; sellers use approved wording.","skillsAdoption":"Ballot-measure literacy and attribution discipline.","governanceCheckpoints":["Attribution review","Leadership acknowledgment of patchwork risk"],"acceptanceCriteria":["Proposed: table cites Fortune publication date","Proposed: no unsourced capacity-loss %","Proposed: Sunbury fate marked unclear"],"risks":["Overgeneralizing Ohio to all states","Mixing polls with results","Stale municipal status"]}},"retrievedAt":"2026-11-07T04:10:20Z","enrichedAt":"2026-11-07T04:14:49Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"None reported.","procurementImplications":"Tax breaks and rezoning fights appear in related municipal measures; Gallup/ICAPP poll figures are opinion context, not election results.","operatingModelImplications":"Hyperscale campus planning in Ohio faces denser local veto points; cloud service roadmaps should not assume smooth local buildout.","sourceVerification":{"openedUrl":"https://fortune.com/2026/11/04/ohio-data-center-ballot-measures-midterm-elections/","referenceExcerpt":"at least 14 municipalities passing bans or other restrictions on data centers.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}