Google Cloud Media CDN
CDN & Delivery

Google Cloud Media CDN

Streamcake registers Media CDN edge origins and host routing so live streams use your CDN domain on a shared Google edge cache service.
Streamcake's Google Cloud Media CDN service integrates with the Network Services APIs to manage stream delivery through Google edge infrastructure. For each stream path the workflow registers edge cache origins idempotently, resolves origin addresses from contribution URLs and optional default object-storage host mapping, and updates host rules and path matchers on your pre-provisioned edge cache service. Preview and active URL types receive routing at the right lifecycle moments, profile identifiers select hostname and origin settings, and playback helpers substitute the CDN domain while preserving paths. Workflow event logs record provisioning steps; cloud-side metrics complement operational visibility. Removal paths in the current implementation do not delete routes automatically, so operators should monitor routing growth alongside cache and origin health.

Not sure where to start?

Tell us your use case and we'll recommend the right MediaLive configuration for your workflow.


Features

Register stream contribution paths as edge origins safely — existing entries are detected so repeat workflow steps do not create duplicates.
Attach new route rules to your pre-provisioned edge cache using hostname matching and path matchers so traffic maps cleanly to each distribution.
Route preview-style contribution addresses during setup, then align active viewer paths when the stream is promoted to live delivery.
Several CDN profiles per integration let each stream pick the right hostname and origin mapping through the profile identifier carried on the stream record.
Map contribution hosts to the correct upstream source when using default object-storage hosts versus custom origin domains in your configuration.
Machine identity authenticates programmatic calls to Google Cloud networking APIs used for origin and routing updates in each workflow step.
Build viewer-ready playback addresses by replacing the contribution hostname with your configured CDN domain while keeping paths intact.
Workflow event logs capture start and completion for provisioning actions; cloud-side metrics complement checks on cache behaviour and origin health.

Ready to go live with broadcast-grade reliability?

Provision a Google Cloud Media CDN in minutes. No infrastructure to manage — Streamcake handles everything end-to-end.

Use Cases

Pair workflow event history with periodic review of edge cache routing tables because automated teardown of routes is not performed in the current service behaviour.

Target Audience
  • Platform operations
  • SRE teams
Key Features Used
  • Operations Visibility
  • Host-Based Edge Routing
  • Secure API Identity
  • Idempotent Edge Origins
Run Google Cloud Media CDN alongside other Streamcake delivery integrations so encoders and packagers stay independent of which edge network serves viewers.

Target Audience
  • Multi-cloud architects
  • large broadcasters
Key Features Used
  • Playback Domain Swap
  • Multi-Profile Delivery
  • Secure API Identity
  • Operations Visibility
Deliver high-profile live programmes through Google edge infrastructure with orchestrated origin registration and routing updates tied to each workflow phase.

Target Audience
  • Sports leagues
  • concert streamers
  • global broadcasters
Key Features Used
  • Idempotent Edge Origins
  • Host-Based Edge Routing
  • Playback Domain Swap
  • Operations Visibility
Operate several Media CDN profiles with separate hostnames and origin mappings so each brand or tenant keeps its own edge configuration inside one integration.

Target Audience
  • Multi-brand operators
  • enterprise media
Key Features Used
  • Multi-Profile Delivery
  • Flexible Origin Mapping
  • Host-Based Edge Routing
  • Secure API Identity
When operators change the CDN profile on a stream that has not begun finalising, routing updates apply the new profile while preserving orderly workflow guards.

Target Audience
  • Broadcast operations
  • managed service providers
Key Features Used
  • Multi-Profile Delivery
  • Preview and Active Phases
  • Flexible Origin Mapping
  • Host-Based Edge Routing
Serve packaged live output that originates from cloud object endpoints by mapping default storage hosts to the correct upstream source in service settings.

Target Audience
  • OTT platforms
  • archive-first workflows
Key Features Used
  • Flexible Origin Mapping
  • Idempotent Edge Origins
  • Playback Domain Swap
  • Preview and Active Phases

Ready to go live with broadcast-grade reliability?

Provision a MediaLive channel in minutes. No infrastructure to manage — Streamcake handles everything end-to-end.