How to serve EU viewers from EU infrastructure, even if your encoding runs on AWS
There's a misconception in the streaming industry that if you encode with AWS Elemental MediaLive or go live through Amazon IVS, you're locked into CloudFront for delivery. You're not. And if you're serving EU residents, there are strong reasons (legal, strategic, and financial) to decouple your ingest from your distribution.
The Default Pipeline Problem
Whether you encode with AWS Elemental MediaLive, go live through Amazon IVS (Interactive Video Service), or transcode with AWS Elemental MediaConvert, the path of least resistance looks the same:
Camera → RTMP/SRT → AWS Elemental MediaLive or IVS → MediaPackage → CloudFront → Viewer
It works. AWS has made it frictionless. IVS even abstracts the entire pipeline into a managed service: you push, it delivers. Elemental MediaLive gives you full control over encoding profiles and bitrate ladders. Both are excellent at what they do.
But frictionless doesn't mean risk-free.
When you run this full-stack architecture, every byte of your viewers' data (playback sessions, IP addresses, geolocation, device fingerprints, viewing behavior) flows through infrastructure owned and operated by a company subject to US jurisdiction. Not just the encoding. The delivery, too. Even when IVS or Elemental output lands on a CloudFront PoP physically located in Frankfurt or Paris, it's still Amazon infrastructure, still US jurisdiction.
And that's where the problem starts.
The CLOUD Act vs. GDPR: An Unresolved Conflict
The US CLOUD Act, passed in 2018, allows US law enforcement to compel American companies to hand over data stored abroad, including data belonging to non-US persons sitting on servers physically located in the EU.
GDPR Article 48, on the other hand, explicitly prohibits transferring personal data to non-EU authorities without an international agreement.
These two laws are in direct conflict, and no amount of contractual clauses resolves this. In the summer of 2025, executives from Microsoft, Google, Amazon, and Salesforce testified before the French Senate that they could not guarantee EU citizens' data would be shielded from US government access if compelled by court order.
The providers themselves admit the sovereignty gap is real.
The EU Data Privacy Framework (DPF), the successor to Privacy Shield, is built on foundations that the CJEU has already invalidated twice (Safe Harbour, then Privacy Shield via Schrems II). In early 2025, the Trump administration removed three of five members of the US Privacy and Civil Liberties Oversight Board, leaving the body overseeing DPF commitments without a quorum. The legal ground is shifting again.
"Sovereign Cloud" Marketing vs. Architectural Reality
AWS, Microsoft, and Google have all launched "sovereign cloud" offerings for Europe. AWS announced its European Sovereign Cloud with a first region in Germany. Microsoft followed with sovereign solutions in mid-2025. Google launched its own Data Boundary features.
But here's the critical distinction: sovereignty is not about where the data center sits. It's about who controls the infrastructure and which jurisdiction governs the operator.
If the controlling parent entity is headquartered in the US, the CLOUD Act applies. Period. A data center in Frankfurt operated by an AWS subsidiary is still subject to US legal demands. The EU Data Act (effective September 2025) now requires cloud providers operating in the EU to actively challenge such demands, but challenging is not the same as blocking.
For streaming operators, this means your viewers' session data, analytics, and potentially even content access logs are exposed to a jurisdictional conflict you didn't sign up for.
The Pragmatic Architecture: Decouple Ingest from Delivery
The good news: HLS is an open standard. An HLS manifest is just a URL pointing to segment files. Nothing in the protocol ties your origin to your edge.
You can absolutely:
- Encode with AWS Elemental MediaLive, or go fully managed with Amazon IVS
- Package your HLS/DASH output via MediaPackage (or let IVS handle it)
- Deliver through an EU-based CDN or edge proxy that pulls from your AWS origin
This is not exotic. It's standard multi-CDN architecture, except your delivery layer is operated by a European entity, under EU jurisdiction, with no exposure to the CLOUD Act.
Your encoding pipeline stays where it's best (AWS has excellent media services, no argument there). But the last mile, the part that touches your viewers' devices, collects their IP addresses, and logs their sessions, runs on infrastructure that answers to EU law and EU law alone.
EU-Based CDN Options for Streaming
The European CDN ecosystem has matured significantly. Viable options for HLS/DASH video delivery include:
- Bunny CDN (Slovenia): purpose-built video streaming features, edge storage, competitive pricing
- CDN77 (Czech Republic): strong video streaming track record, transparent pricing, top-tier European performance
- BlazingCDN (Poland): 50+ PoPs, live streaming support, enterprise SLAs
- KeyCDN (Switzerland): lightweight, developer-friendly, Swiss privacy jurisdiction
- Leaseweb CDN (Netherlands): multi-CDN capabilities, Dutch-operated infrastructure
- G-Core (Luxembourg): low-latency edge network with strong media delivery features
None of these are subject to the US CLOUD Act. All are governed by EU or EFTA jurisdiction.
Beyond GDPR: The Broader Regulatory Stack
Data sovereignty in European streaming isn't just about GDPR anymore. The regulatory landscape now includes:
- EU Data Act (effective September 2025): Requires providers to prevent unlawful non-EU government access to data and to challenge conflicting demands
- NIS2 Directive: Cybersecurity requirements for essential and important entities, including digital infrastructure providers
- DORA (applicable from January 2025): Financial sector rules on ICT concentration risk, relevant if your streaming service handles payment or subscription data
- European Health Data Space (EHDS): Strict localization requirements if your content delivery involves health-related data
The direction is clear: Europe is tightening control over data flows, reducing dependency on US tech giants, and building a legal framework where "sovereign" means something concrete, not just a marketing label.
The Cost Argument
Something streaming operators often overlook: EU-based CDNs are frequently cheaper than CloudFront for European delivery.
CloudFront's pricing is region-based, and European egress isn't its cheapest tier. European CDN providers like Bunny CDN and CDN77 often undercut CloudFront significantly on per-GB pricing for EU traffic, while delivering comparable or better performance within Europe (CDN77 consistently ranks in the top 5 for European latency benchmarks).
So the sovereignty move isn't just a compliance exercise. It can be a cost optimization.
The EU Economy Argument: Every Euro Counts
There's a dimension to this conversation that goes beyond compliance and cost: where your streaming budget actually lands.
When you deliver through CloudFront, Akamai, or any US-operated CDN, your egress spend flows to US-headquartered companies, is taxed under US fiscal frameworks, and fuels US shareholder returns. For a European broadcaster or OTT operator spending €50K to €500K/year on CDN delivery, that's a significant capital outflow, multiplied across thousands of streaming operators across the continent.
Routing your EU delivery through European CDN providers means that money stays in the European economy. It funds European jobs: engineers in Prague, network operators in Ljubljana, infrastructure teams in Amsterdam. It strengthens the European tech ecosystem that the EU Commission's Cloud and AI Development Act is explicitly trying to build, with the goal of tripling EU data center capacity by 2030.
This isn't economic nationalism. It's pragmatic industrial policy. The EU is investing heavily in digital sovereignty infrastructure precisely because decades of defaulting to US hyperscalers created a dependency that now poses legal, strategic, and economic risks. As a streaming operator, every delivery contract you sign with a European CDN is a vote for a more resilient European digital infrastructure.
And there's a multiplier effect. European CDN providers buy European bandwidth, lease European rack space, hire European talent, and pay European taxes. The same euro works harder when it circulates locally than when it exits the continent on the next quarterly earnings call.
For publicly funded broadcasters and media organizations receiving EU or national subsidies, this argument carries even more weight. There's a growing expectation, sometimes explicit in procurement rules, that public money should support European digital infrastructure where viable alternatives exist. And in CDN delivery for HLS streaming, they very much exist.
How iReplay's Streaming Cost Optimizer Fits In
This is exactly the architecture our Streaming Cost Optimizer is built for.
It takes any HLS stream as input, whether your origin is AWS Elemental MediaLive, Amazon IVS, MediaPackage, Wowza, Nimble Streamer, or any other HLS-compatible source, and re-delivers it from EU-hosted infrastructure.
Your ingest stays wherever it works best. AWS has earned its place in encoding and packaging, we're not arguing against that. But your EU viewers get served from EU edge nodes, under EU jurisdiction, with your egress spend going to European infrastructure.
And the pricing is simple: per minute of stream delivered. Not per GB. Not per request. Not per edge location tier.
Traditional CDN pricing forces you to estimate bandwidth consumption before you even know your audience. How many concurrent viewers? What bitrate ladder? What's the average session duration? You end up building spreadsheets with worst-case scenarios just to forecast your monthly bill. And when a live event spikes beyond your estimates, you get a surprise invoice.
With minute-based pricing, there's a direct, predictable correlation between watch time and cost. One minute watched = one unit billed. No guesswork on data transfer volumes, no regional surcharges, no hidden egress fees. You know exactly what you'll pay based on a metric you already track: how long people watch your content.
For budgeting, this changes everything. Your finance team doesn't need a networking degree to understand the CDN line item. And for live events with unpredictable audiences, you stop worrying about bandwidth overages because the cost model scales linearly with actual viewership, not with data volume that varies depending on bitrate, device type, and ABR ladder behavior.
No migration of your encoding pipeline. No vendor lock-in. No CLOUD Act exposure on the delivery path. No surprise invoices. Just a smarter delivery layer that respects your budget, your viewers' data rights, and the European digital economy.
Your encoding can be GAFA. Your delivery should be sovereign.