Strategic PartnersLatest editionIssue 12
AWS
November 10 AWS news centered on what SLED buyers must decide for themselves. AWS promoted Moonshot AI's Kimi K3.1 Pro on Bedrock, saying data stays within AWS and is not shared with Moonshot, while Texas has listed Moonshot AI as a…
Full research summary
November 10 AWS news centered on what SLED buyers must decide for themselves. AWS promoted Moonshot AI's Kimi K3.1 Pro on Bedrock, saying data stays within AWS and is not shared with Moonshot, while Texas has listed Moonshot AI as a prohibited technology for state employees and devices since January, without saying how that applies to cloud-hosted models. OpenAI's Daybreak cyber models reached Bedrock's runtime endpoint for enrolled customers; an independent Irregular evaluation of the model behind Daybreak Blue found real zero-day discovery but low end-to-end reliability. AWS also released an AgentCore Web Search API (commercial Regions only, not GovCloud), an agent evaluation playbook, and a token-cost data lake that centralizes full prompts that may contain PII. In Ohio, Butler County planners backed a township ban that could block a proposed $5 billion AWS campus.
Read the edition Previous: Issue 11, November 9All AWS editions
What this stream covers
AWS AI and ML services, Bedrock, SageMaker, infrastructure and government cloud. Separate vendor claims from independent deployments, benchmarks and limitations. Explain Government/Education applicability where supported, without forcing irrelevant news into a SLED use case. Azure/Microsoft belong in Microsoft stream; Google Cloud belongs in Google stream.
- Evidence records
- 8
- Cross-source patterns
- 2
- Also published November 10
- AnthropicCampus OperationsCiscoCitizen Engagement & ServicesCrowdStrikeDellEmergency ServicesEverpureGoogleHealth & Human ServicesK–12Local GovernmentMicrosoftNetAppNVIDIAOpenAIPalo Alto NetworksPublic SafetyRed HatResearch UniversitiesServiceNowState GovernmentStudent SuccessTransportationUtility ManagementVAST Data
- Subscribe
- Atom feed for AWS
What the evidence supports, and what it leaves open
2 patterns this edition will stand behind, each carried by at least two independent sources. Every one arrives with the question it has not answered.
- Bedrock's expanding model catalog moves vendor-eligibility and cyber-access decisions onto SLED buyers
Operating questionWho reviews each new Bedrock model against state vendor restrictions, third-party access programs and independent evidence before it is allowed in agency accounts?
- New AgentCore and Bedrock operations tooling arrives commercial-first, and evaluation thresholds, prompt archives and query budgets stay with the customer
Operating questionFor each production agent, who sets evaluation thresholds, approves grounding domains and query budgets, and decides how long prompt logs are kept, and is the tooling available in the partition the agent runs in?
Research through your lens
Every resource includes source evidence and takeaways for all three roles.
Evidence in this micro-vertical
73 resources
Follow the outcomes
73 resources across outcomes in your selection. Counts include all outcomes.
Refine by evidence type and topic
AWS publishes an agent evaluation playbook for AgentCore, adding managed DeepEval and AutoEval evaluators alongside built-in ones
AWS's November 10, 2026 post describes AgentCore Evaluations with three tiers: AWS-authored built-in evaluators (GoalSuccessRate, Helpfulness and 13 more), managed third-party evaluators from the open-source DeepEval and AutoEval libraries, and custom LLM-as-a-judge evaluators including multi-dimension scoring. It recommends defining success in business terms, mapping behaviors to trace- or session-level evaluators, and running on-demand, online (sampled live traffic) and batch (golden dataset) modes. It warns that a high completion rate can hide failures such as PII leakage, and that ground-truth evaluators run only in batch.
Limitations & uncertainty
Vendor guidance; evaluator reliability is asserted ('benchmarked for reliability') without published data. GovCloud availability not stated.
AWS makes AgentCore Web Search available as a direct API at $7 per 1,000 queries, in six commercial Regions
On November 10, 2026 AWS announced general availability of the InvokeWebSearch API on Bedrock AgentCore, returning ranked results from an Amazon-operated web index with text extracts, titles, URLs and publication times, filterable by domain and date. Calls are IAM-authorized, can run over PrivateLink and can be logged as CloudTrail data events, billed at $7 per 1,000 queries. The API is available in six commercial Regions; AWS's developer guide states it is not available in GovCloud (US-West), where the earlier Gateway connector must be used.
Limitations & uncertainty
Vendor claim; no index quality or freshness data. GovCloud limitation is from the AWS developer guide opened alongside.
AWS details Moonshot AI's Kimi K3.1 Pro Highspeed on Amazon Bedrock, with data-boundary claims and US-only routing option
AWS's November 10, 2026 launch post says Kimi K3.1 Pro Highspeed, an open-weight model from China-based Moonshot AI with a 1-million-token context window, is on Amazon Bedrock (AWS's What's New entry is dated November 6). AWS states customer data is processed within the AWS data boundary, is not shared with Moonshot AI, is not used for training, and that zero data retention is always on. Access is through cross-Region inference: a global profile (cheapest, any commercial Region), a US profile and an India profile. A Flex tier is offered at half the Standard price. Performance claims are attributed to Moonshot AI; no benchmarks or GovCloud availability are given.
Limitations & uncertainty
Vendor claim; no benchmarks. Interpretation of state vendor bans as applied to hosted models is ours, not the source's. GovCloud availability is not stated in the source.
OpenAI's Daybreak Red and Daybreak Blue cyber models reach the Bedrock runtime endpoint for enrolled customers via US and Global routing
AWS announced on November 10, 2026 that eligible customers can call OpenAI's Daybreak Red (GPT-5.6 Cyber) and Daybreak Blue (GPT-5.6 Sol) through the bedrock-runtime endpoint, using US and Global cross-Region inference profiles. AWS describes Blue as the starting point for defensive work and Red for authorized vulnerability research and exploit reproduction, with a lower refusal threshold matched by stronger identity verification, monitoring and access controls. Access requires enrollment in OpenAI's Daybreak program, then an access request through the AWS account team. AWS states inference data is not used for training.
Limitations & uncertainty
Vendor claim. Global routing is commercial-only; GovCloud availability for Red was a separate October announcement already archived.
AWS publishes a Bedrock invocation data lake for org-wide token and cost visibility that centralizes full prompts and responses
AWS's November 10, 2026 post provides CloudFormation templates that forward Bedrock invocation logs from linked accounts to a central account, flatten them with Lambda, store Parquet in S3 via Firehose, and query them in Athena, with optional joins to the Cost and Usage Report by IAM ARN and a Quick Sight dashboard. Each record includes model, account, IAM identity, token counts, stop reason and prompt/response text. AWS notes the bucket is KMS-encrypted and that prompts might contain PII, recommending IAM and bucket policy review. It frames this as a tokenomics (AI FinOps) practice.
Limitations & uncertainty
Vendor sample; not a managed service. Prompt-retention implications for public records are our interpretation. GovCloud deployment not discussed.
Butler County planners back St. Clair Township's data center ban that could stop a proposed $5 billion AWS campus; Trenton residents threaten suit
On November 10, 2026 the Butler County Planning Commission unanimously recommended approval of a St. Clair Township zoning change banning data centers, where an 18-building, $5 billion AWS campus is proposed on 600 acres across Madison and St. Clair townships. The change returns to the township zoning commission and then trustees. Separately, lawyers for Trenton residents asked the city to revoke the zoning certificate for a Prologis-built AWS data center, citing the new 25 MW ban, and said taxpayers intend to sue. Prologis says the ban does not affect its project; AWS gave a general statement.
Limitations & uncertainty
Recommendation, not final adoption. AWS's response was a general statement. Trenton vote was archived earlier; this item reports new county action and a legal demand.
AWS publishes a write-time memory-poisoning defense for Bedrock AgentCore, tested on 11 demo scenarios and leaving composition to customers
An AWS ProServe post (November 9, 2026) describes memory poisoning as persistent indirect prompt injection and offers a sample Lambda interceptor on AgentCore Gateway that scores memory writes on semantic drift (40%), instruction patterns (25%), namespace boundary (25%) and write rate (10%), returning ALLOW, QUARANTINE or DENY. In a demo of 11 scenarios (3 benign, 8 attacks) using a keyword-overlap stand-in for Titan embeddings, all decisions matched expectations; added latency was about 26 ms warm and cost about $2.50 per day for 10,000 writes. Writes made directly through the SDK bypass the Gateway check.
Limitations & uncertainty
Eleven-case demo with a substitute similarity method; scores may change with real embeddings. Not a managed AWS feature.
AWS offers Anthropic's Claude Mythos 5.2 cybersecurity model on Bedrock in AWS GovCloud (US), limited to allow-listed organizations
AWS announced on November 9, 2026 that Claude Mythos 5.2 is offered through Amazon Bedrock in the AWS GovCloud (US) Regions to eligible customers only. AWS describes it as Anthropic's most advanced model for cybersecurity, coding and complex reasoning, able to find software vulnerabilities and demonstrate exploitability, and the first Anthropic model with these cybersecurity capabilities in GovCloud. Access is limited to allow-listed organizations through Anthropic's Cyber Verification Program. The post gives no benchmarks, pricing or eligibility criteria.
Limitations & uncertainty
Vendor claim. No benchmarks, no eligibility criteria, no approval timeline. See the related CVP, FedRAMP-status and Oossa items in this edition for access and authorization constraints.
AWS's Bedrock FedRAMP and DoD IL4/IL5 model status page, updated November 9, lists Anthropic models through Fable 5.1 but not Fable 5.2 or Mythos 5.2
AWS's model-level authorization page for Bedrock shows 'Last updated: November 9, 2026' and a table of model families against U.S. East/West (FedRAMP Class C), GovCloud (FedRAMP Class D) and DoD IL4/IL5 columns. At retrieval, the Anthropic rows ran from Claude 3 Haiku through 'Fable 5.1'; neither Fable 5.2 nor Mythos 5.2 appeared on the page, even though both were announced for GovCloud the same day. The AWS GovCloud Bedrock user guide (also opened) points customers to this page for FedRAMP Class D and IL approvals.
Limitations & uncertainty
Point-in-time observation of a page that may be updated soon; the text extraction did not let us map each 'X' to a specific column, so no claim is made about Fable 5.1's exact authorization levels.
Claude Fable 5.2 reaches AWS GovCloud (US) as a 'covered model' that requires data retention for safety monitoring
AWS announced on November 9, 2026 that Claude Fable 5.2, described as Anthropic's most capable generally available model for technical work, is available in AWS GovCloud (US). AWS says it can work for hours to days unattended and coordinate subagents. The post states Anthropic designated Fable 5.2 and Mythos 5.2 as covered models that require data retention for safety monitoring; until Enterprise Frontier Safeguards is available, eligible customers can use Fable 5.2 with zero data retention. AWS's companion ML blog post (also opened) says default use requires retention for up to 30 days with human safety review performed by Amazon personnel within the AWS boundary.
Limitations & uncertainty
Vendor claim. Capability statements are Anthropic's testing, not independent results. Model was not listed on the FedRAMP/IL status page at retrieval (separate item).
AWS enables short-lived cross-partition credentials between GovCloud (US) and commercial Regions, while telling customers to treat cross-partition access as an exception
AWS announced on November 9, 2026 that IAM outbound identity federation now works across partitions: a workload in GovCloud (US) can obtain a short-lived signed JWT with sts:GetWebIdentityToken and exchange it for temporary credentials in a commercial-partition role via sts:AssumeRoleWithWebIdentity, replacing long-term access keys. It is off by default, enabled per account, free of charge, and auditable in CloudTrail in both partitions. AWS advises consulting compliance teams (citing FedRAMP, ITAR and DoD CC SRG), initiating access from the more restrictive partition, and treating cross-partition access as an exception.
Limitations & uncertainty
Vendor documentation. Applicability to AI workloads (e.g., calling commercial-only Bedrock models from GovCloud) is our interpretation and may be prohibited by an agency's data rules.
AWS profiles Xtasis, a Northwestern researcher's company, whose de-identification and citation tools run on AWS, with claimed 60-75% literature-time savings
AWS's November 9 Public Sector Blog post profiles three tools built by Xtasis, the company of Northwestern research assistant professor Adrienne Kline. PixelGuard de-identifies medical images, with a crosswalk log and low-confidence changes flagged for human review, and deploys inside the customer's own environment; NoteGuard redacts all 18 HIPAA identifiers from clinical notes. Both are sold through AWS Marketplace. CiteGeist manages literature, verifies that references exist and uses NVIDIA Nemotron via Bedrock and SageMaker AI for summaries. Claims include 'hundreds of hours' of redaction saved and a roughly 60-75% cut in literature-management time; no method or sample is given.
Limitations & uncertainty
Vendor marketing with unverified metrics; private-university origin; no de-identification accuracy figures.
Oossa: AWS's GovCloud Mythos 5.2 announcement gives no benchmarks, pricing, eligibility criteria or approval timeline
Oossa's November 9 article separates AWS's descriptions from evidence: the announcement includes no test results, examples, benchmark scores or pricing; does not say which software has been tested or whether findings were independently checked; and does not list eligibility criteria or how long approval takes. It concludes approved teams must assess the model's findings rather than treat them as confirmed vulnerabilities.
Limitations & uncertainty
Single-source article; adds analysis, not new facts. Publisher (OLY Europe LTD) is not a specialist government outlet.
AWS Agent Registry generally available in AWS GovCloud (US-West) via Bedrock AgentCore for governed MCP, tool and agent catalogs
AWS says AWS Agent Registry, available through Amazon Bedrock AgentCore, is now generally available in the AWS GovCloud (US-West) Region. It is described as a fully managed discovery service and central catalog for organizing, curating and discovering MCP servers, tools, agents, agent skills and custom resources, with an approval workflow controlling what becomes discoverable. People and AI agents can find resources through hybrid search, catalog browsing and a native MCP endpoint. AWS pitches public sector organizations and partners for a single governed inventory, citing approval workflows and CloudTrail audit logs for compliance and oversight. The announcement does not state GovCloud (US-East) availability, pricing, measured adoption or independent compliance outcomes.
Limitations & uncertainty
GovCloud (US-West) only in this post; no US-East claim; no pricing; no SLED customer case; catalog does not equal runtime permission.
AWS Security Hub adds organization-wide SBOM inventory from Amazon Inspector for EC2, ECR and Lambda, available wherever Security Hub runs (including GovCloud)
AWS says Security Hub now provides a Software Bill of Materials inventory giving central security teams an organization-wide view of software packages installed on compute resources. It is built from SBOMs that Amazon Inspector generates for EC2 instances, ECR container images and Lambda functions, lists each package with version, type and number of resources, supports filtering by account and Region, shows installed software per resource during triage, and is queryable by API. It is included with Security Hub Essentials at no additional cost, needs no new enablement, populates where Inspector is enabled, and is available in all Regions where Security Hub is available. A separate March 30, 2026 What's New confirms Security Hub availability in GovCloud (US-East and US-West). The announcement does not mention AI workloads; the AI link here is interpretation.
Limitations & uncertainty
Vendor claim; AI relevance is interpretation; coverage of AgentCore-managed runtimes not stated; Inspector must be enabled; GovCloud availability inferred from Security Hub's GovCloud availability plus 'all Regions' statement.
Briefpixel: Agent Registry in GovCloud US-West is a discovery catalog with approval and audit logging, not automatic compliance or US-East coverage
Briefpixel reports AWS announced general availability of Agent Registry in AWS GovCloud (US-West) on November 6 through Bedrock AgentCore as a searchable catalog of agents, MCP servers, tools, skills and custom resources. The piece stresses the announcement is regional availability in US-West, not confirmation of GovCloud (US-East), and that AWS identifies public-sector organizations and partners as the audience. It separates catalog discovery from AgentCore Runtime hosting: cataloguing a tool does not mean its code is deployed or that every user may run it. Briefpixel also notes GovCloud eligibility checks, no new price in the release, and that using a registry does not make an organisation automatically compliant.
Limitations & uncertainty
Secondary commentary; no independent lab test; relies on AWS primary materials.
We are the Frontier: CGI Federal–AWS–UT Knoxville AI workforce coalition is announced rather than shipped, with no timeline or placement metrics
The outlet reports the CGI Federal, AWS and University of Tennessee, Knoxville coalition and characterizes it as 'announced rather than shipped': an initial program is named but no enrollment or delivery timeline was given. It notes the offerings are micro-credentials, micro-certificates and executive certificates with no performance or placement metrics published, and that enrollment details, pricing and start dates were not announced. It frames the coalition as extending a CGI-AWS strategic collaboration into workforce training, and suggests watching for additional university partners or an expansion timeline. The article draws on ExecutiveBiz reporting and dates the CGI-AWS collaboration inconsistently (March in one passage, April in another).
Limitations & uncertainty
Secondary reporting; relies partly on ExecutiveBiz; internal date inconsistency on the CGI-AWS agreement (March vs April).
Journal-News: Trenton, Ohio voters pass ~80% ban on >25 MW data centers; organizers target proposed 18-building AWS campus while four-building AWS site continues
Journal-News reports that with 100% of precincts reporting, Trenton's data-center ban measure passed about 80% to 20% on November 3, 2026 (article dated/updated November 6). The measure bans data centers requiring more than 25 megawatts within city limits. A citizen organizer hopes it will keep an 18-building Amazon Web Services data center from developing within the city and could rein in electric use of a four-building AWS data center already under construction. The paper states the measure would likely not affect the four-building AWS campus under construction on 141 acres in Trenton, but could impact a proposed 18-building AWS project tied to 600 acres in Madison and St. Clair townships if annexation into Trenton succeeds. St. Clair Township introduced a zoning amendment to prohibit data centers with a Butler County hearing set for November 10; Butler County's six-month moratorium affecting Madison Township expires in December.
Limitations & uncertainty
Unofficial results framing in places; AWS corporate response not quoted; township bans not yet final; WVXU separately attributes industrial-park construction differently—this item follows Journal-News AWS attribution.
ModelBank: Amazon Bedrock degraded about 2.4 hours on Nov 6 as US-WEST-2 EC2/EBS launch failures hit dependent services
ModelBank reports Amazon Bedrock had degraded performance on November 6, 2026 between 22:51 and 01:12 UTC (about 2.4 hours; 4:51–7:12 PM CT), mapped to one official AWS incident, 'Elevated Launch Failures' in US-WEST-2. Quoted AWS updates attribute the issue to a subsystem supporting EBS volumes needed during EC2 instance launch, affecting all four Oregon AZs and services that instantiate new instances (for example DataSync and AWS Backup); AWS advised customers not to mutate running instances. The resolved notice gives 2:35–4:21 PM PST. ModelBank's own probes detected degradation for about one hour. It reports 100.00% measured availability over 30 days and seven days with an outage or degradation in the last 90 days.
Limitations & uncertainty
Which Bedrock functions degraded is not specified; probe methodology not detailed; times differ between official window (2:35–4:21 PM PST) and ModelBank window; no AWS root-cause report.
NeuralTrust: Amazon Bedrock AgentCore security gaps customers still own—session mapping, default execution roles, SDK versions and prompt-level threats
NeuralTrust, which sells a competing agent gateway, re-read AgentCore Developer Guide pages, two AWS security bulletins and two BeyondTrust write-ups on November 6, 2026 without deploying AgentCore. It credits AgentCore with per-session microVM isolation, managed credentials and deterministic Gateway policy, but lists customer-owned gaps: AWS states AgentCore does not enforce session-to-user mappings; sessions run up to 8 hours on microVMs; code in the microVM can read execution-role credentials via the metadata service (MMDSv2 required from June 30, 2026); the CLI's default execution role permits invoking all foundation models in the account; InvokeAgentRuntimeForUser's user-id header is not verified against an IdP; policy only covers Gateway-routed traffic; guardrail scores are non-deterministic. It recaps the Code Interpreter Sandbox DNS issue (remediated April 15 per BeyondTrust) and SDK CVEs fixed in 1.6.1 and 1.18.1, and notes CloudTrail InvokeCodeInterpreter records carry no request parameters.
Limitations & uncertainty
Commercial conflict of interest; did not deploy AgentCore; GovCloud specifics not addressed; AWS docs cited without links so claims should be checked against current AWS documentation.
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 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.
Limitations & 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.
AWS announces general availability of Web Answer on Amazon Bedrock AgentCore for synthesized, cited web answers in one tool call
AWS says Web Answer on Amazon Bedrock AgentCore is generally available as a managed tool that returns a synthesized, grounded, cited answer to a natural-language question in a single call, so builders need not maintain their own search, retrieve, synthesis and citation pipeline. It extends June's Web Search on AgentCore, plans parallel searches, and supports domain include/deny lists and publish-date filters. It attaches as a Gateway target over MCP with IAM authentication and claims zero data egress. Availability is stated only for US East (N. Virginia), with per-tool-call pricing. No GovCloud availability, customer deployments or measured quality results are given.
Limitations & uncertainty
US East (N. Virginia) only; no GovCloud; no accuracy, hallucination or latency metrics; no SLED customer evidence.
AWS Security Hub Network Scanning now available in AWS GovCloud (US) to probe actual internet reachability of resources
AWS says Security Hub Network Scanning is now supported in AWS GovCloud (US). The feature probes resources from the internet to detect actual reachability, not only what security groups and route tables suggest could be reachable. It discovers public IPs, VMs and load balancers, identifies reachable ports and services, and emits findings that Security Hub Exposures can correlate. Existing customers enable it per account/Region or via organization configuration policy; it is on by default for new Security Hub customers. AWS says it is included with Security Hub Essentials at no additional cost in commercial and GovCloud Regions that support Security Hub. No independent evaluation or SLED case study is provided.
Limitations & uncertainty
Vendor announcement only; no measured false-positive rates, scan frequency details in this page, or customer outcomes.
CGI Federal launches AI ('SI') Workforce Development Coalition with AWS; University of Tennessee, Knoxville is first university partner
CGI Federal announced on November 5, 2026 a Super Intelligence (SI) Workforce Development Coalition, led by CGI Federal in collaboration with AWS, to co-develop curricula preparing college graduates and mid- and late-career professionals to work alongside AI ('digital labor'). Topics named include integrating digital labor, redesigning workflows for hybrid human-AI teams and managing AI-augmented operations. Learners can pursue micro-credentials, micro-certificates and executive certificates ending in a capstone that delivers a live or shadow-mode digital labor deployment. The University of Tennessee, Knoxville is the first participating university, through its College of Emerging and Collaborative Studies. CGI says it is working with universities across the U.S. The release names no AWS services, enrollment numbers, pricing, start dates or outcome metrics.
Limitations & uncertainty
Announcement only; no enrollment, timeline, placement or mission-outcome metrics; AWS role not specified beyond collaboration; 'super intelligence' terminology is marketing/policy framing.
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
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.
Limitations & 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.
KUOW: Post-midterm 'blue wave' threatens Amazon and Microsoft data-center expansion as Ohio bans and Texas/Georgia/Ohio governors campaigned on curbs
KUOW reports that midterm voters and candidates favoring slower AI infrastructure buildout prevailed, creating new political risk for Amazon and Microsoft data-center expansion beyond the Pacific Northwest into Ohio, Georgia and Texas. Local Ohio jurisdictions passed moratoria or restrictions that could affect Amazon plans; nearly 80% of Trenton voters passed a ban on data centers requiring more than 25 MW aimed at Amazon's planned 18-building campus. Texas Gov. Greg Abbott had temporarily blocked state permits; governor-elect Gina Hinojosa has called for a broader moratorium until the Legislature regulates the industry. Researcher Miquel Vila of 10a Labs expects a surge of regulations in key markets, with uncertain effects on whether projects still make financial sense in those states or the US.
Limitations & uncertainty
Single regional outlet; Texas/Georgia outcomes described as campaign pledges whose legal force depends on state law; Trenton figure rounded as 'nearly 80%'.
WLWT: As ten Ohio communities pass data-center bans, AWS construction in Fayette County continues; county pause on new projects excludes it
WLWT reports that voters in 10 Ohio communities, including Trenton, approved bans on large data centers on November 3, while work continues on Amazon Web Services' multibillion-dollar data center in Fayette County beside Interstate 71. Fayette County commissioners recently paused new data center projects in several townships, but the pause does not affect the AWS facility under construction. Residents of nearby Jeffersonville (about 1,250 people) raised concerns about lost farmland, property values and tax consequences, and night lighting, though they declined to appear on camera. One resident supported the project if AWS covers utility costs and called for more transparency and community benefits, while worrying Ohio could lose AI investment.
Limitations & uncertainty
Community count (10) differs from other reports (at least 14 municipalities with bans or restrictions); resident views are anecdotal; no AWS comment.
Fortune: At least 14 Ohio municipalities pass data-center bans or restrictions after Nov 3; Sunbury and Trenton measures cite Amazon/AWS projects
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.
Limitations & uncertainty
Some results described as unofficial; Amazon project fate in Sunbury unclear; poll numbers are separate from ballot outcomes.
GeekWire: Amazon's first Washington data centers face scrutiny; only 23 of 706 Wallula Gap comments supported the project as AWS CEO warns moratoriums could cost the US the AI race
Amazon is pursuing its first Washington data centers: a 134-acre Wallula Gap site in Walla Walla County and the 1,000-acre West Richland campus. Of 706 submissions in a 30-day comment period closing Oct 12 on Wallula Gap, only 23 (about 3%) supported it, per a Walla Walla Union-Bulletin analysis, and many asked for a full Environmental Impact Statement. Amazon says it will pay 100% of property taxes and work with utilities so bills do not rise; GeekWire notes its renewable matching is annual accounting and its water figures exclude power-generation water. AWS CEO Matt Garman warned local and state moratoriums could harm the economy and national security.
Limitations & uncertainty
Comment analysis is from another outlet; Amazon claims on bills, water and taxes are company statements.
Sunbury, Ohio voters pass 25 MW data center ban aimed at a proposed Amazon campus 2,809-763 as at least 14 Ohio towns approve limits; Trenton ban passes about 80-20
Sunbury voters approved a charter amendment banning data centers of 25 MW or more by 2,809 to 763 (78.64%), all six precincts reporting, in unofficial Delaware County Board of Elections results reported by Delaware Source. The measure targeted a possible hyperscale Amazon project. At least 14 Ohio municipalities passed bans or restrictions on Nov 3, citing Fortune. In Trenton a ban passed 80% to 20%; organizers hope it keeps out an 18-building AWS campus, though it likely will not affect a four-building AWS campus already under construction nearby. The report notes neither cited outlet says Amazon has changed plans, and figures are unofficial until certified.
Limitations & uncertainty
Voltgrid labels the story AI-assisted and relies on other outlets; 10TV's original report was not retrievable (HTTP 403) and DigiTimes was paywalled. Unofficial results. Trenton figure rounded.
Stream editions
Each edition carries its own synthesis and evidence ledger.
November 10, 20261 edition
November 9, 20261 edition
November 7, 20261 edition
November 6, 20261 edition
November 5, 20261 edition
November 4, 20261 edition
November 3, 20261 edition
November 2, 20261 edition