Strategic PartnersIssue 055 records
AWS
A quiet Monday edition of product notices and local siting fights. AWS added Claude Haiku 5.5 to Kiro in GovCloud, giving developer teams there a cheaper model tier for bulk and review tasks; let Amazon Connect flows call MCP tools through AgentCore Gateway, but only in commercial Regions; and simplified Amazon Quick desktop sign-in. None reports a SLED customer or measured result. On the constraint side, the Tri-City Herald reports AWS confirmed it is behind a $264 million West Richland, Wash., land deal for up to 21 data center buildings as the council weighs a moratorium, and Sunbury, Ohio votes Nov 3 on a charter ban that could stop a proposed $2 billion Amazon campus. Company water and power claims in both remain unverified.
- Evidence records
- 5
- Cross-source patterns
- 1
- Evidence classes
- 3 vendor claim2 independent reporting
- Outcomes
- 3 emerging2 cautionary
- Source freshness
- 4 new this fortnight1 recent
- Research completed
- 2026-11-03
Choose a role to see its takeaway beside every record in the ledger.
Patterns across the evidence
Synthesis · Lighthouse Advisory interpretation
AWS data center expansion is meeting local moratoriums and ballot bans, with company utility claims left for councils to verify
Two independent local reports show the same constraint. In West Richland, Wash., AWS confirmed only on Nov 2 that it is the buyer behind a $264 million land deal for up to 21 buildings, while the council considers an interim moratorium and SEPA review is pending. In Sunbury, Ohio, voters decide Nov 3 on a charter ban on data centers over 25 MW that would likely stop a proposed $2 billion Amazon campus already under moratorium. In both, water, power and tax figures come from the company or advocates and are not independently verified. This is context for municipal and utility clients, not evidence about AWS AI services.
Operating questionWhat independent review, disclosure and enforceable commitments does the local government require before approving a hyperscale campus?
Supporting evidenceTri-City Herald; Amazon Web Services; City of West RichlandDelaware Gazette; City of Sunbury; Amazon Data Services
Evidence ledger
Full record · every source keeps its link and limitations
Kiro adds Claude Haiku 5.5 in AWS GovCloud (US), completing the Claude 5.5 family for the agentic IDE and CLI there
AWS announced on Nov 2 that Claude Haiku 5.5 is available in the Kiro IDE and CLI in the AWS GovCloud (US) Regions, so all three Claude 5.5 models are now in Kiro there. AWS positions Haiku 5.5 for high-volume, low-latency work such as summarising long context, classifying and routing requests, bulk text processing, small multi-file edits and parallel review subagents, with Opus 5.5 and Sonnet 5.5 doing harder planning. It has a 1M context window, a 0.06x credit multiplier and a 0.3x multiplier for requests over 100K tokens. The archive already holds Haiku 5.5 on Bedrock in GovCloud; this item is the Kiro developer-tool availability.
Why it matters, evidence and limitations
- Why it matters
- State and university development teams working inside GovCloud can now pick a cheaper, faster model tier for routine agentic coding tasks without leaving the boundary. Relevance is limited to organisations already using Kiro in GovCloud; no SLED customer or measured result is given.
- Evidence and measured results
- One-page vendor availability notice. No benchmark, accuracy, cost-per-task or customer data.
- Limitations and uncertainty
- Vendor notice only. Authorization of Kiro in GovCloud for a given workload remains the agency's responsibility. Relevance limited to existing Kiro GovCloud users.
Amazon Connect flows can now call MCP tools through Bedrock AgentCore Gateway via a new External Tool block, but not yet in GovCloud
AWS announced (feed date Nov 2) that Amazon Connect Customer flows can invoke Model Context Protocol tools through a new External Tool block, connecting to third-party applications via Amazon Bedrock AgentCore Gateway and reusing the same tools used by agentic experiences, without custom Lambda functions. AWS's example is retrieving CRM case history or transaction details during a contact. The feature is listed in nine commercial Regions; GovCloud is not listed.
Why it matters, evidence and limitations
- Why it matters
- 311 centres, benefits call lines and nonemergency lines built on Amazon Connect (the archive includes Richmond's nonemergency deployment) could pull case or account data into flows with less custom code. The absence of GovCloud limits use where CJIS or similar data must stay there.
- Evidence and measured results
- Vendor feature notice; no customer, reliability or security evaluation.
- Limitations and uncertainty
- Commercial Regions only per the notice. No reliability, latency or failure-handling detail. Vendor claim.
Amazon Quick desktop app now reuses an organisation's existing Quick sign-in, removing a separate identity-provider setup
AWS announced on Nov 2 that the Amazon Quick desktop application now signs users in with the same method the organisation uses for Quick on the web, so administrators no longer need to register a separate OIDC application. An admin adds a desktop connector once in the Quick console; it works with IAM Identity Center, IAM federation or native Quick users, and a dedicated configuration with Entra ID, Google Workspace, Okta or Ping remains optional.
Why it matters, evidence and limitations
- Why it matters
- Agencies and universities piloting Amazon Quick as an AI assistant for staff face one less identity integration to approve. Relevance is modest: it is an administrative change, and the notice gives no Region list beyond full-feature Quick Regions.
- Evidence and measured results
- Vendor feature notice; no adoption or security evaluation.
- Limitations and uncertainty
- Vendor notice; Region support stated only as full-feature Quick Regions; GovCloud availability not stated.
Tri-City Herald: AWS confirms it is behind a $264M West Richland, Wash., land deal for up to 21 data center buildings as the council weighs a moratorium
The Tri-City Herald reports (Nov 2) that AWS confirmed it is the buyer behind Trammell Crow's $264 million July purchase of nearly 1,000 acres at Lewis & Clark Ranch in West Richland, planning three buildings first and up to 21. AWS has not submitted a site plan; the project is subject to Washington SEPA review. Residents, including about 200 homes across Ruppert Road, have pushed back, and the council was to consider an interim moratorium on Nov 3. AWS's FAQ claims outside-air cooling 93% of the time, 10 million gallons of water a year for three buildings rising to 70 million at 21, and that its power needs won't affect local utility customers; those are AWS statements reported by the paper. The paper notes AWS previously used an alias for the Wallula Gap site.
Why it matters, evidence and limitations
- Why it matters
- Local governments, ports and utilities negotiating AI data center capacity face disclosure, land-use and utility questions; the alias purchase and moratorium push show how trust issues shape approvals. For SLED AI buyers it is context on regional capacity and community constraints, not a deployment.
- Evidence and measured results
- Independent local reporting with AWS's confirmation by phone and its FAQ figures; no independent verification of water or power claims.
- Limitations and uncertainty
- Water, power, emissions and jobs figures are AWS claims. Moratorium outcome on Nov 3 unknown at submission. Not an AI deployment.
Delaware Gazette: Sunbury, Ohio votes Nov 3 on a charter ban on data centers over 25 MW that targets a proposed $2 billion Amazon Data Services campus
The Delaware Gazette reports that Sunbury voters decide on Nov 3 a self-executing charter amendment prohibiting data centers with aggregate monthly demand or peak load above 25 MW. The backing group, Big Walnut for Responsible Growth, notes the city's November 2024 incentive for a proposed $2 billion Amazon Data Services campus and the council's unanimous April 2026 moratorium through Jan 31, 2027. Why now: the vote is Nov 3, the day after this edition, and it follows the Trenton, Ohio Issue 17 vote on an AWS project already in the archive; national coverage on Nov 2 counted it among 41 data center ballot measures.
Why it matters, evidence and limitations
- Why it matters
- A second Ohio city could constrain an AWS/Amazon campus by charter, showing that local ballot measures are becoming a routine constraint on AI infrastructure siting. Relevant to municipal and utility clients, not to AI service buyers directly.
- Evidence and measured results
- Independent local reporting quoting ballot language and the advocacy group's summary; no company statement in the article.
- Limitations and uncertainty
- Published Oct 6; the vote outcome is unknown at submission. The project history is quoted from an advocacy group's website. Independent WCMH coverage could not be opened (HTTP 403).
How to read this edition
Source findings, measured results and limitations come from the cited publications. Patterns, operating questions, role takeaways and implementation considerations are Lighthouse Advisory interpretation, stated as questions to validate locally rather than guaranteed outcomes. Vendor and operator claims are labeled as claims. Full research method.
- Vendor claim
- A supplier-provided assertion that has not been upgraded to independent evidence.
- Independent reporting
- Independent reporting with attributable sources but without a formal evaluation design.