Common use cases
Cloud CDN and load balancing
Using Cloud CDN with HTTP(S) load balancing
Cloud CDN works with HTTP(S) load balancing to deliver content to your users. The HTTP(S) load balancer provides the frontend IP addresses and ports that receive requests and the back ends that respond to the requests. You can also configure Cloud CDN for use with load balancing and GKE.
|Anycast IP||Serve content globally from a single IP address.|
|SSL/TLS||SSL/TLS support included at no additional cost.|
|Large objects||Upload large objects (up to 5 TB) for media use cases.|
|Signed URLs||Serve responses from our globally distributed caches, even when you need requests to be authorized.|
|Invalidation||Take down cached content in minutes.|
|HTTPS||Provide your own SSL/TLS certificate to secure your content using a domain name of your choice.|
|Monitoring and logging||Use seamlessly with Monitoring and Logging; additional monitoring also available via Network Intelligence Center.|
|Origins||Serve content originating from Compute Engine VMs, Google Kubernetes Engine, and Cloud Storage buckets (or mix-and-match).|
|Modern protocols||Support for HTTP/2 and QUIC.|
When Cloud CDN serves your content, you’re charged for bandwidth and HTTP/HTTP(S) requests. On cache hits, you pay for cache egress bandwidth. On cache misses, you additionally pay for cache fill bandwidth.
You’re also charged for any cache invalidations you initiate. Each invalidation can specify either a single path or a path prefix.View pricing details