Reduce Supplier Exposure in On‑Prem Device and Cloud Data Infrastructure

What happened

An AWS engineering description explains how a flat, near-random single-tier network design improves resilience and can be materially more energy- and cost-efficient than traditional datacenter network topologies. The piece highlights provider-side savings and notes those efficiencies are becoming default in new builds, which raises the question of where provider gains are allocated. Watch whether cloud vendors document how these infrastructure efficiencies are shared with customers or used to change service mixes

Why the category manager should care

Ask providers to demonstrate how datacenter-level network efficiencies affect customer pricing, capacity, or SLA guarantees rather than assuming automatic pass-through

Key facts

• Near-random, single-tier network design is presented as default in new datacenter builds
• Author claims up to a large percentage improvement in energy efficiency versus traditional de
• Claims that AWS has held many customer SKU prices steady despite component cost pressures

What happened

Boston Scientific and McKesson disclosed separate cyber incidents: Boston Scientific’s on-premise breach disrupted remote monitoring and prevented activation of new cardiac-device communicators, while McKesson reported a large data-exfiltration claim. Boston Scientific said cloud-based systems were not affected but on-prem systems were, and it engaged an external IR firm for restoration. Watch restoration timelines, supplier coordination, and whether contracts require vendor-assisted activation or restore evidence

Why the category manager should care

Treat device telemetry systems and pairing/activation workflows as contractually critical services with defined restore and verification requirements

Key facts

• New remote monitoring communicators cannot be activated while affected on-prem systems are of
• Boston Scientific identified affected on-premise systems while noting cloud systems were not
• Boston Scientific hired an external IR provider to assist with investigation and restoration

What happened

AWS acquired DuckLabs, the team behind DuckDB, positioning the embedded analytical engine as connective tissue across application and data stacks. AWS argues native-embedded analytics lets developers run OLAP queries inside host processes without separate DBMS servers, changing integration and operational models. Procurement should track how this affects vendor support, portability, and developer costs for analytics inside application runtimes

Why the category manager should care

Require explicit acceptance and portability testing for embedded DB features and clarify who supports in-process analytics after vendor acquisitions

Key facts

• DuckDB runs embedded in host processes and removes the need for a separate DBMS server
• AWS frames DuckDB as 'connective tissue' for application-level analytics and data engineering
• DuckDB Foundation remains independent but AWS ownership of DuckLabs signals tighter integrati