Strategic PartnersIssue 107 records
AWS
No new measured AWS AI deployment results appeared overnight. The signals were workforce, siting and operational assurance. CGI Federal and AWS announced an AI workforce coalition with the University of Tennessee, Knoxville as first campus; independent reporting notes it has no timeline, enrollment or placement metrics yet. In Ohio, Amazon's Wilmington site plan goes to a November 10 planning vote with a staff approval recommendation, after a court-ordered pause and with permits and a 2027 statewide-ban push still pending. Fayette County's new-project pause exempts the AWS campus under construction. On the platform side, Security Hub added a no-added-cost SBOM inventory (available wherever Security Hub runs, including GovCloud) that can surface outdated AI SDK packages. A competing vendor's AgentCore review lists controls customers still own, and independent monitoring logged about 2.4 hours of Bedrock degradation tied to a US-West-2 EC2/EBS incident on November 6.
- Evidence records
- 7
- Cross-source patterns
- 2
- Evidence classes
- 4 independent reporting3 vendor claim
- Outcomes
- 3 cautionary2 emerging2 mixed
- Source freshness
- 7 new this fortnight
- Research completed
- 2026-11-08
Choose a role to see its takeaway beside every record in the ledger.
Patterns across the evidence
Synthesis · Lighthouse Advisory interpretation
After the Nov 3 bans, AWS Ohio campuses now hinge on site-by-site municipal and county gates
Two independent local sources show the same mechanism. In Wilmington, Obedio reports staff now recommend approving Amazon's 12-building site plan ahead of a November 10 special vote, but only after a court-ordered pause, two 5-0 tablings and with building and air permits still outstanding, plus a citizen amendment aimed at a November 2027 statewide ban on >25 MW centers. In Fayette County, WLWT reports a county pause on new data-center projects that exempts the AWS facility already under construction. Interpretation: construction status and local procedure, not statewide policy, currently determine whether AWS capacity proceeds; this affects physical campuses, not AWS Region or GovCloud service availability.
Operating questionFor each Ohio AWS campus your stakeholders reference, is it under construction, awaiting a local vote, or exposed to a future statewide ban, and which official record confirms that?
Supporting evidenceObedio (Global Regulatory Risk Advisors, Inc.)WLWT (Cincinnati)
AWS AI assurance work stays on the customer side: package inventory, identity binding and regional resilience
AWS's new Security Hub SBOM inventory (vendor claim, available wherever Security Hub runs, including GovCloud) gives security teams a package-level view of Lambda, ECR and EC2 workloads, which is useful for finding outdated AI SDKs, but it does not patch anything. NeuralTrust's November 6 documentation review (from a competing vendor) lists what AgentCore leaves to customers: session-to-user binding, default execution-role scope, SDK versions and prompt-level threats. ModelBank's monitoring of the November 6 US-West-2 EC2/EBS incident shows Bedrock-dependent services can degrade with regional infrastructure. Interpretation: SLED AI programs need explicit owners for inventory, identity and resilience controls, whatever new managed features AWS ships.
Operating questionWho in the agency owns AI SDK version policy, AgentCore session binding and Bedrock fallback behavior, and how is each tested before production?
Supporting evidenceAmazon Web ServicesNeuralTrustModelBank.ai
Evidence ledger
Full record · every source keeps its link and limitations
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.
Why it matters, evidence and limitations
- Why it matters
- Higher-education workforce signal: a public flagship university is packaging AWS-linked AI workforce credentials with a systems integrator. Relevant to university continuing-education, workforce boards and state agencies seeking AI-ready staff; applicability to other campuses is not shown.
- Evidence and measured results
- Company press release (CGI newsroom; same text distributed via PR Newswire). Vendor and partner claims only; includes quotes from CGI Federal and the UT CECS dean.
- Limitations and uncertainty
- Announcement only; no enrollment, timeline, placement or mission-outcome metrics; AWS role not specified beyond collaboration; 'super intelligence' terminology is marketing/policy framing.
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).
Why it matters, evidence and limitations
- Why it matters
- Provides the independent caveat for SLED higher-education and workforce buyers: treat the coalition as an early-stage offering without evidence of outcomes.
- Evidence and measured results
- Independent local technology reporting summarizing the announcement and ExecutiveBiz coverage; no original interviews or data.
- Limitations and uncertainty
- Secondary reporting; relies partly on ExecutiveBiz; internal date inconsistency on the CGI-AWS agreement (March vs April).
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.
Why it matters, evidence and limitations
- 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.
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.
Why it matters, evidence and limitations
- Why it matters
- County-government relevance: shows the distinction between under-construction AWS campuses and new-project pauses, and resident demands for transparency and community benefits.
- Evidence and measured results
- Local TV investigative report with resident interviews; no official documents linked.
- Limitations and uncertainty
- Community count (10) differs from other reports (at least 14 municipalities with bans or restrictions); resident views are anecdotal; no AWS comment.
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.
Why it matters, evidence and limitations
- Why it matters
- SLED teams running Bedrock AgentCore or other AI agent code in Lambda or ECR containers could use the inventory to find outdated AI SDK packages (for example bedrock-agentcore versions affected by prior AWS bulletins) across accounts, including GovCloud.
- Evidence and measured results
- Primary AWS announcement (vendor claim) plus AWS What's New confirming Security Hub GovCloud availability. No independent validation of coverage or accuracy.
- Limitations and 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.
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.
Why it matters, evidence and limitations
- Why it matters
- Directly relevant to SLED teams building agents on AgentCore (including newly GovCloud-available registry/runtime components): it enumerates controls that remain the agency's responsibility under shared responsibility.
- Evidence and measured results
- Third-party security vendor's documentation review, citing AWS docs and bulletins by title; explicit commercial interest (TrustGate). Not hands-on testing.
- Limitations and 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.
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.
Why it matters, evidence and limitations
- Why it matters
- SLED Bedrock workloads hosted in US-West-2 can be affected by underlying EC2/EBS events; reinforces cross-Region or GovCloud cross-Region inference and resilience planning for constituent-facing AI.
- Evidence and measured results
- Third-party monitoring page combining its probes with quoted AWS status text; not an AWS post-incident report.
- Limitations and 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.
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.
- Independent reporting
- Independent reporting with attributable sources but without a formal evaluation design.
- Vendor claim
- A supplier-provided assertion that has not been upgraded to independent evidence.