Adrian Viruet

Adrian Viruet works on the global procurement side of Amazon/AWS, in a category-management role tied to the supplier and sourcing environment around hyperscale cloud infrastructure. In industry terms, this places him near the part of the cloud business where vendors, equipment providers, facilities suppliers, network-related partners, and long-cycle infrastructure sourcing all matter to buildout and operations. His profile is best read as a hyperscale procurement and infrastructure-sourcing profile, not as a public-facing sales or cloud product role. AWS’s infrastructure supply-chain materials show how procurement and cost functions sit close to data centre server racks, networking, power, cooling, and related systems, which are the practical parts of the cloud business that telecom and digital infrastructure people recognise immediately. For BTW, Viruet’s relevance comes from the intersection between AWS’s cloud expansion and the supplier ecosystems that support it. At ITW, that means he is more likely relevant to infrastructure vendors, facilities providers, carrier-adjacent partners, and digital infrastructure counterparties than to ordinary enterprise cloud buyers.

Object Position

Adrian Viruet is publicly listed in the ITW attendee metadata as Global Corporate Procurement - Category Manager at Amazon/AWS. The same attendee record classifies his job function as procurement and places his industry category under Cloud & Compute / Hyperscalers.

That combination gives the profile a clear industry position. Viruet sits on the procurement side of the hyperscale cloud market, where supplier relationships and category management support the physical and operational base of cloud infrastructure.

Operating Role / Decision Role

Viruet’s public title points to global corporate procurement and category management. In a hyperscale environment, that role is materially different from generic purchasing. Category managers in this kind of business often work around supplier strategy, sourcing frameworks, vendor performance, risk, cost, and long-term availability of the equipment or services needed to keep infrastructure programmes moving.

AWS’s public infrastructure supply-chain materials describe a team that manages procurement, cost, and automated technology solutions for data centre server racks, frontier outposts, networking, and power and cooling equipment. Viruet’s exact category scope is not public, so the profile should not claim a specific commodity or supplier portfolio. The confirmed point is that his role is attached to AWS procurement and therefore belongs in the supplier-management side of the hyperscale infrastructure ecosystem.

ITW Relevance

Viruet’s ITW relevance is not the usual carrier-sales story. He represents the hyperscaler procurement side of the room.

Potentially relevant conversations at ITW may include:

•infrastructure supplier relationships

•data centre equipment and facilities sourcing

•carrier-adjacent service providers

•cloud infrastructure support ecosystems

•power, cooling, and rack-related vendor environments

•regional supplier and procurement visibility

•connectivity and interconnection partners where relevant to AWS infrastructure planning

Potential counterparties may include:

•data centre operators

•fibre and connectivity providers

•infrastructure vendors

•power and cooling suppliers

•colocation and interconnection ecosystems

•telecom operators with cloud-connectivity relevance

•managed infrastructure and facilities partners

For infrastructure vendors and carrier-adjacent companies, someone in AWS procurement is relevant because hyperscaler demand often shapes supplier roadmaps, capacity planning, and commercial expectations across the wider market.

Control Surface

Viruet’s public control surface is procurement-facing rather than ownership-facing.

The relevant surface includes:

•supplier relationship exposure

•category-management participation

•procurement process visibility

•infrastructure sourcing context

•vendor and supply-chain coordination

•possible exposure to infrastructure cost, risk, and continuity considerations

This should not be overstated as direct control over AWS infrastructure. Procurement roles sit close to the commercial machinery that supports AWS buildout and operations.

Impact Mechanism

Hyperscale procurement affects the infrastructure market through practical supplier decisions. When AWS expands cloud capacity, it needs data centre space, racks, networking gear, power and cooling systems, logistics, and maintenance support across a broad vendor base that can operate at scale.

A person in a category-management role can influence market outcomes because category strategy and supplier engagement influence:

•sourcing resilience

•vendor access

•infrastructure cost structure

•deployment continuity

•supplier qualification

•risk handling

•long-term partner relationships

The impact mechanism is strongest where AWS demand touches constrained markets such as power, cooling, high-density racks, network equipment, data centre components, or regional supplier availability.

Category Boundary

This profile should not be read as a general AWS cloud product, a software procurement, or a public cloud sales role. The more accurate BTW classification is hyperscale procurement and infrastructure sourcing.

Viruet’s relevance is not that he represents AWS as a brand. It is that his function sits in the practical procurement environment behind cloud infrastructure growth, where supplier relationships and infrastructure inputs drive hyperscale market growth.