From the AWS edition of November 5, 2026
Dealroom: Midterm wins in Texas, Georgia and Ohio advance data-center moratorium politics affecting Amazon campuses; analysts flag ~45% of planned US capacity at risk
Amazon Web Services; States of Texas, Georgia and Ohio; City of Trenton, Ohio · State government; AI infrastructure investment · United States (Texas, Georgia, Ohio; national capacity context)
- Publisher
- Dealroom News
- Original publication
- 2026-11-05
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-03
What happened
Dealroom's Nov 5 scorecard, citing the Financial Times and other outlets, reports Democratic gubernatorial winners in Texas, Georgia and Ohio campaigned on curbing data-center development: Texas's Gina Hinojosa pledged an immediate moratorium pending safeguards; Georgia's Keisha Lance Bottoms a temporary statewide pause; Ohio's Amy Acton a conditional freeze unless strict energy and water criteria are met. Locally, Trenton, Ohio passed a measure that would stymie an Amazon campus, and Edgewater, Florida approved a charter ban 77% to 23%. Analysts quoted say Texas is roughly 25-30% of planned US data-center capacity and that Democratic state/local wins may bring short-term moratoria affecting about 45% of planned US capacity expansion (Goldman Sachs' Jan Hatzius). Bank of America notes AWS revenue growth of 39% in the periods cited as context for a possible utilization/pricing trade-off. Caveats: governors' powers depend on legislatures; pledges differ in strength.
Why it matters
Gives state and local officials a national scorecard of how Nov 3 politics may slow hyperscale AWS-related capacity, with explicit Amazon campus examples and quantified analyst capacity-at-risk estimates that agencies should treat as market opinion, not settled law.
Evidence and measured results
Secondary industry scorecard synthesizing FT, Ballotpedia/CNBC, AdImpact/Axios, Fortune/RFI and sell-side analyst comments; useful as a map of claims, not primary election returns.
Limitations and uncertainty
Secondary synthesis; some tallies were 'on track' at press time; Amazon share price reaction is market noise; Azure/Google figures mentioned are out of AWS-stream scope for claims.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Election outcomes in major AI build-out states raise the odds of statewide pauses that could delay new Amazon and peer campuses.
- Stakeholders
- State CIO / energy advisor
- Legislative staff
- Utility regulators
- Economic development
- Discovery questions
- Which pledges require legislation versus executive action?
- How is 'planned capacity' defined in the 45% estimate?
- Which Amazon projects in-state are permitted versus proposed?
- Value hypothesis
- A living pledge-versus-law tracker helps agencies avoid over-reacting to headlines; value unproven.
- Potential engagement
- Jurisdiction tracker distinguishing campaign pledge, introduced bill and enacted rule.
- Unsupported claims
- That 45% of capacity is already illegal
- AWS Region outages
- Final certified multi-state tallies
Pre-sales engineering
Role takeaway
- Fit
- Fit for policy and infrastructure planning audiences; weak fit for application engineering alone.
- Architecture and integration
- None for app architecture; capacity forecasts may change.
- Prerequisites
- Access to bill trackers
- List of in-state hyperscale proposals
- Constraints
- Secondary sources
- Analyst estimates
- Pledges differ by state
- Security
- Not applicable.
- Proof of value
- Cross-check each pledge against primary reporting
- Confirm Amazon project status with permitting agencies
Delivery
Role takeaway
- Work
- Build and maintain a pledge/bill/enacted tracker for TX/GA/OH and key localities.
- Dependencies
- Legislative calendars
- Local clerk updates
- Ownership
- Public-sector strategy / government affairs with legal review.
- Skills and adoption
- Policy analysis and permitting literacy.
- Governance checkpoints
- Weekly tracker update through session
- Legal review of any enacted text
- Acceptance criteria
- Proposed: every cited jurisdiction labeled pledge/bill/enacted
- Proposed: Amazon projects listed with permit status
- Risks
- Treating estimates as law
- Mixing Microsoft/Google projects into AWS commitments
- Stale 'on track' tallies
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?
None for AWS APIs; multi-year capacity and power planning implications.
Governance
Who approves, reviews and stays accountable for outcomes?
Statewide pauses and conditional freezes would add legislative and criteria gates above local zoning.
Security and privacy
What data, permissions and controls need testing?
None reported.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None reported.
Procurement
What should contracts, pricing and exit terms secure?
Moratorium pledges are not identical to enacted statutes; agencies should track bill text.
Operating model
Which teams own the service once it runs?
Hyperscaler and neocloud timelines may slip; existing AWS Regions continue operating.
Publication history
- 2026-11-05AWS · Issue 084 resources
Stable resource ID: dealroom-midterm-data-center-moratoriums-tx-ga-oh-20261105