ProBackend
ai cloud regulation
2 hours ago6 min read

Brussels Targets AWS and Azure for Stricter Cloud Competition Rules

The European Commission has signaled a preliminary intent to bring AWS and Microsoft Azure under stricter Digital Markets Act oversight, aiming to curb entrenched market power in cloud services.

The Virtual Myth and the Concrete Reality

The cloud is a lie. Not the technology itself, of course, but the metaphor. We talk about cloud computing as if it were a weightless, atmospheric resource—an ethereal mist of processing power floating somewhere above our heads. It isn't. It is concrete, steel, copper wire, and millions of gallons of cooling water pumped through massive data centers. As an environmental scientist, I cannot look at the cloud without seeing the massive physical footprint: the megawatts of electricity, the heat exchangers, the raw mineral extraction required for high-end server racks.

According to reports published by The Register, the European Commission’s preliminary decision to designate Amazon Web Services (AWS) and Microsoft Azure as gatekeepers under the Digital Markets Act (DMA) is a crucial reality check. Brussels is finally addressing the physical and economic reality of cloud infrastructure. These hyperscalers are no longer just service providers; they have become the default infrastructure of modern business, especially across Europe. They control the virtual pipes. They control the concrete storage. When a couple of offshore corporations hold the power to dictate the operational parameters of European digital commerce, they are not merely competitors in a free market. They are utilities. It is about time we regulated them like it.

The Virtual Myth and the Concrete Reality

Why the Quantitative Rules Broke Down

At its inception, the Digital Markets Act was built with a specific set of tools. The drafting focused heavily on consumer-facing platforms: search engines, web browsers, social networks, and app marketplaces. The regulation defined gatekeepers using simple quantitative thresholds—annual revenues, market capitalization, and millions of active monthly users. These metrics translate well to consumer apps. They do not translate well to the hidden plumbing of enterprise infrastructure.

AWS and Azure did not trigger these consumer-oriented numbers directly, yet their systemic grip is undeniable. Under Article 3(8) of the DMA, the Commission can designate gatekeepers qualitatively. If your servers host the applications that half of Europe's businesses run on, you are a gatekeeper, regardless of how many individual consumer logins you count. It is about downstream leverage. The commission's move shows a necessary evolution: evaluating infrastructure by its gravity, not its raw user headcount. By looking past the simple mathematical formulas, Brussels is recognizing that systemic importance is about structural integration, not just consumer clicks. A server rack that handles banking data is infinitely more critical than a social media feed, even if the latter has ten times the active logins.

Why the Quantitative Rules Broke Down

The Frictionless Trap of Hyperscaler Lock-in

Predictably, the hyperscalers argue they operate in a friction-free market. They claim that competition is fierce and that switching is just a couple of mouse clicks away. This is pure public relations. In the real world, the costs of migrating out of AWS or Azure are astronomical. It isn't just about egress fees—though charging a toll to move your own data off their servers is a remarkably lucrative racket. The true trap is architectural.

Modern software isn't built on raw virtual machines anymore. It is built on proprietary platform services, custom vector databases, and highly structured API pipelines. When a company builds its application on these tools, they are welding their code to the provider's proprietary stack. We have seen these infrastructure dynamics before in the startup space. Cloud giants routinely lock in early-stage firms by handing out massive compute subsidies, a practice we analyzed in our breakdown of the capital battles that define cloud credit wars. Moving off these platforms is not a simple migration; it is a complex, high-risk architectural rewrite. It is the enterprise equivalent of changing the engine of an airplane mid-flight. When the switching cost is that high, customer choice is an illusion.

The Lobbying War and the Google Question

The public relations response to the Commission's announcement has been quiet but revealing. Microsoft’s immediate reaction was to point the finger elsewhere. A Microsoft spokesperson expressed concern that the regulator is ignoring the growing power of Google Cloud and Gemini, warning that this exclusion could tilt the market. It is a classic diversion tactic: point at the third-place competitor to make your own duopoly look harmless.

Meanwhile, advocacy groups are celebrating. The Open Cloud Coalition, which Microsoft previously dismissed as a Google-backed lobbying front, welcomed the preliminary findings. The coalition pointed out that the lock-in effects of the Big Two are actively shaping the growth of enterprise AI. It is a high-stakes proxy war. By dominating the physical servers where AI models are trained and run, AWS and Azure are positioning themselves as the sole gatekeepers of the next industrial era. If you control the hardware, you control the algorithms. And if you control the algorithms, you control the economic landscape. The Open Cloud Coalition's support for the designation highlights the growing anxiety among smaller European providers who are being squeezed out of their own regional markets by American hyperscalers.

Bridging the Regulatory Grid

The hyperscalers are also pushing a legal argument: that Europe’s regulatory stack is already too heavy. AWS pointed specifically to the EU Data Act framework, claiming that adding the DMA is a redundant, overlapping burden that will strangle innovation and deter investment. This represents a fundamental misreading of the problem. The Data Act deals with data portability and access rights across the economy. The DMA targets structural power.

It focuses on the gatekeeper status of platforms that can unilaterally dictate market terms. In a market where over half of EU businesses rely on public cloud services, relying on generic portability rules is like trying to regulate a water monopoly with standard residential plumbing codes. You need structural remedies. The DMA provides these remedies: mandatory interoperability, non-discriminatory access, and a prohibition on self-preferencing. If AWS and Azure are forced to make their platform services truly interoperable, it will dismantle the proprietary walls that keep customers trapped. It is a necessary intervention. Without it, the European cloud market will remain a closed ecosystem controlled by two foreign companies. We need rules that target the root of the problem, and referencing the EU Data Act limits highlights the need for a stronger legal framework.

The Transatlantic Compliance Runway

Both Amazon and Microsoft now have a window to respond to the Commission’s preliminary findings. If the designations are finalized, the clock starts ticking: the companies will have exactly six months to align their practices with the DMA. Non-compliance is an expensive proposition, carrying potential fines of up to 10 percent of global annual turnover. For companies with revenues in the hundreds of billions, that is a threat with real teeth.

Contrast this proactive stance in Brussels with the regulatory hesitation across the English Channel. The UK's Competition and Markets Authority (CMA) spent years investigating the cloud market, only to settle for voluntary commitments rather than hard rules. Brussels is showing what regulatory conviction actually looks like. If European tech sovereignty is to mean anything, it must start with the physical servers that power the continent's digital ambitions. We cannot build a sustainable, competitive digital economy on infrastructure we do not control and cannot regulate. The European Commission has taken a stand. Now, we wait to see if the hyperscalers can find a way to escape the gatekeeper tag.

More blogs