David Ricardo, Senior Software Engineer
Anand Vijayan, Senior Product Manager
European broadcasters, streaming platforms, and public sector organizations have strict data protection regulations, including GDPR and national standards. While traditional content delivery networks (CDNs) use global Anycast routing meshes that dynamically shift traffic across borders during congestion or maintenance, regulated European workloads need explicit guarantees that media delivery, caching, origin fills, and log processing stay within the European Union.
To meet these requirements without sacrificing edge scale or cache offload, Google Cloud is introducing EU Data Residency (Private GA) for Media CDN, alongside the general availability of Europe Flexible Origin Shielding in Frankfurt (europe-west3). This new Flexible Origin Shielding offering is a component of the EU Data Residency product, and will even be useful to customers without data residency requirements.
Sovereign Delivery Architecture
Media CDN enforces an explicit European delivery boundary across four layers of the infrastructure stack so that customer content and end-user data remain localized within the EU:
EU-Restricted Anycast & Edge Serving: Enrolled projects receive a dedicated Anycast IP range announced exclusively in Europe and routed via EU-only network paths to physical Media CDN Edge Caches within EU member states. As a defense-in-depth safeguard, non-EU edge proxies enforce Layer 4 connection rejection if a request targeting an EU data residency IP reaches a non-EU node.
- In-Region Cache Fill &
europe-west3Flexible Origin Shielding: Cache misses from EU Edge Caches are consolidated through our new Flexible Origin Shielding offering in Frankfurt (europe-west3), with automated in-region failover. Global fallback outside the EU is disabled and peer-to-peer cache fills are constrained so that traffic stays within the EU boundary. - EU-Resident Customer Logs & Internal Telemetry Redaction: Customers can route and retain all customer-facing access and audit logs (Cloud Logging and Cloud Audit Logs) within EU regional storage buckets. For Google-internal operational telemetry, no sensitive data leaves the EU.
- Continuous route & compliance auditing: Production Anycast probers continuously verify in-region serving and out-of-region connection rejection.
Standard Global vs. EU Data Residency comparison
| Architectural Layer | Standard Global Media CDN | Media CDN EU Data Residency |
|---|---|---|
| Edge IP Announcement | Global Anycast across all global PoPs | Dedicated Anycast advertised exclusively in the EU |
| Edge Cache Footprint | Global Edge Cache cluster deployment | Physical Edge Caches within EU member states |
| Out-of-Region Ingress | Connect to nearest global edge | Layer 4 connection rejection on non-EU nodes |
| Origin Shielding | Global metro hubs, configurable with Flexible Origin Shielding | Configured to use Flexible Origin Shielding in europe-west3 only |
| Cache Miss Routing | Dynamic multi-region fallback | Strictly localized in-region; global fallback disabled |
| Customer Access Logs | Regional or multi-regional Cloud Logging | Stored in customer-designated EU Cloud Logging buckets |
| Operational Telemetry | Standard system diagnostic logs | Sensitive data is localized to the EU |
Europe Flexible Origin Shielding for all workloads
Beyond strict Data Residency projects, Europe Flexible Origin Shielding (europe-west3) is generally available for all Media CDN customers operating origins in Europe. Enabling europe-west3 on an EdgeCacheOrigin provides three primary operational benefits:
- Increased origin offload: Consolidates cache misses across European Edge Caches into a single regional shield tier, protecting live encoders, video packagers, and Cloud Storage buckets from request spikes during peak live events.
- Lower egress & transit costs: Improves mid-tier cache hit ratios while keeping shield-to-origin fetches localized within the European network backbone.
- Built-In Regional Resilience: Automatically fails over between Frankfurt (
europe-west3) and a backup city without manual routing changes.
Quickstart configuration
Note: To set up data residency for your EU workload, please contact Google Cloud Sales.
To set up the new Flexible Shielding region, follow the steps below.
Configure EdgeCacheOrigin with Europe Flexible Shielding
Define your European origin and set flexShielding.region to europe-west3:
name: projects/my-media-project/locations/global/edgeCacheOrigins/europe-live-origin
originAddress: "origin.media.example.eu"
protocol: HTTPS
port: 443
retryConditions:
- CONNECT_FAILURE
- HTTP_5XX
- GATEWAY_ERROR
timeout:
connectTimeout: 5s
maxAttemptsTimeout: 15s
responseTimeout: 10s
flexShielding:
region: europe-west3
Import the origin configuration:
gcloud edge-cache origins import europe-live-origin \
--source=europe-origin.yaml \
--location=global
Attach Origin to EdgeCacheService
Bind the shielded origin to your EdgeCacheService route rules:
name: projects/my-media-project/locations/global/edgeCacheServices/streaming-eu-service
routing:
hostRules:
- hosts:
- "stream.example.eu"
pathMatcher: media-matcher
pathMatchers:
- name: media-matcher
routeRules:
- priority: 1
description: "Live HLS and DASH media segments"
matchRules:
- pathTemplateMatch: "/**.ts"
- pathTemplateMatch: "/**.m4s"
origin: europe-live-origin
routeAction:
cdnPolicy:
cacheMode: FORCE_CACHE_ALL
defaultTtl: 300s
maxTtl: 3600s
clientTtl: 60s
Import the service configuration:
gcloud edge-cache services import streaming-eu-service \
--source=eu-service.yaml \
--location=global
Availability and next steps
- Europe Flexible Origin Shielding (
europe-west3): Generally available for all Media CDN customers via all our API surfaces: the Google Cloud Console,gcloudCLI, Terraform, and language bindings. - EU Data Residency (Private GA): Available via customized configuration. Contact sales to learn more!
To get started, review the Flexible Origin Shielding Documentation and Media CDN Release Notes, or contact your Google Cloud account team to request project enrollment for EU Data Residency.
