From the AWS edition of November 7, 2026
Obedio: Amazon's Wilmington, Ohio data-center site plan heads to Nov 10 planning vote with staff approval recommendation, amid court order and 2027 statewide ban push
Obedio (Global Regulatory Risk Advisors, Inc.) · Municipal records analysis / local government land use · Wilmington, Clinton County, Ohio, United States
- Publisher
- Obedio blog
- Original publication
- 2026-11-06
- Source retrieved
- 2026-11-08
- Event date
- 2026-11-10
What happened
Obedio reports the Wilmington Planning Commission will hold a special meeting at 4:30 p.m. on November 10, 2026 on Amazon Data Services' site plan for a campus at 1488 S US 68, and that city planning staff are recommending approval for the first time. The October 26 staff report describes 12 principal buildings (three server buildings in Phase One, six more in Phase Two), 28 backup generators per large server building and a berm placing the nearest building about 650 feet from homes. The plan was tabled 5-0 in January and March; a July 14 agreed federal court order barred action until council ratified three ordinances and required 14 days' notice. On November 3 voters rejected four adjacent rezonings by about 80-20 (described as unrelated to the AWS project). City officials cited more than $35 million in water, sewer and road improvements and a $28 million Amazon commitment for a municipal safety center for fire, police and dispatch. Approval would still leave building and state permits, and a citizen constitutional amendment banning >25 MW data centers targets the November 2027 ballot.
Why it matters
Direct local-government and public-safety relevance: a city weighing an AWS campus against infrastructure benefits (utilities, a public-safety center) and resident litigation. Signals continued permitting risk for AWS capacity in Ohio after the Nov 3 votes.
Evidence and measured results
Independent analysis compiled from municipal records (agenda, staff report, ordinances, court order) by a business-intelligence firm; agenda details corroborated via the city's meeting list and the Muyni agenda archive.
Limitations and uncertainty
Secondary compilation by a commercial data firm; staff recommendation is not a decision; vote outcome unknown at publication; Amazon commitments are as reported by city officials.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-08; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Local governments must weigh hyperscale AWS campuses against utility, tax and resident impacts under litigation and ballot pressure.
- Stakeholders
- City council and planning commission
- City law and safety directors
- School districts receiving PILOT shares
- Government-affairs teams
- Discovery questions
- What community-benefit commitments are executed versus proposed?
- How do TIF terms allocate payments to schools?
- What permits remain after site-plan approval?
- Value hypothesis
- Clear documentation of host-community terms can reduce disputes and delays; no outcome is guaranteed.
- Potential engagement
- Advisory briefing on data-center host agreements and community-benefit documentation for local governments.
- Unsupported claims
- Vote outcome
- Impact on AWS service availability
- Executed status of the $28M safety-center commitment
Pre-sales engineering
Role takeaway
- Fit
- Fit for capacity-risk and government-affairs planning; no fit for application architecture changes.
- Architecture and integration
- Track campus status separately from Region selection; no workload changes indicated.
- Prerequisites
- Site-approval tracker
- Official agenda and minutes access
- Constraints
- Court-ordered notice and procedures
- Outstanding building and air permits
- Possible 2027 statewide ban
- Security
- Not a cybersecurity item; physical and environmental permitting only.
- Proof of value
- Tracker updated from official minutes after Nov 10
- Commitments linked to council records
Delivery
Role takeaway
- Work
- Maintain an Ohio AWS campus permitting tracker with official-record links.
- Dependencies
- City agendas and minutes
- Local reporting
- Ballot developments
- Ownership
- Infrastructure strategy / government-affairs analyst.
- Skills and adoption
- Reading land-use records and ordinances.
- Governance checkpoints
- Verify vote from minutes
- Separate proposed vs executed commitments
- Acceptance criteria
- Proposed: official decision recorded within one week
- Proposed: 100% of cited commitments sourced to records
- Risks
- Citing unexecuted commitments
- Conflating siting with service availability
- Statewide amendment uncertainty
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
No cloud-architecture change; affects where AWS physical capacity is built, not GovCloud or Bedrock service availability.
Governance
Who approves, reviews and stays accountable for outcomes?
Shows procedural gates (court-ordered notice, ratified ordinances, party-of-record cross-examination) shaping hyperscale approvals.
Security and privacy
What data, permissions and controls need testing?
Not applicable to data security; generator and emissions permits remain open.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed.
Procurement
What should contracts, pricing and exit terms secure?
Tax treatment via a 30-year TIF with payments in lieu of taxes to schools and infrastructure; original tax agreement O-25-73 not shown as passed.
Operating model
Which teams own the service once it runs?
Municipal staff capacity and legal process are binding constraints on campus timing; statewide amendment adds 2027 uncertainty.
Publication history
- 2026-11-07AWS · Issue 107 resources
Stable resource ID: obedio-wilmington-ohio-aws-site-plan-vote-20261106