Cloud CDN works with external HTTP(S) Load Balancing to deliver content to your users. The external HTTP(S) load balancer provides the frontend IP addresses and ports that receive requests and the backends (or origins) that respond to the requests.
Cloud CDN content can be sourced from various types of backends:
- Instance groups
- Zonal network endpoint groups (NEGs)
- Serverless NEGs: One or more App Engine, Cloud Run, or Cloud Functions services
- Internet NEGs for external backends
- Buckets in Cloud Storage
Use the following guides to set up Cloud CDN:
- With a managed instance group backend
- With a Cloud Storage backend bucket
- With Cloud Run, Cloud Functions, or App Engine
- With third-party object storage
- With an external backend by using an internet NEG
- With Google Kubernetes Engine by configuring Ingress features
To learn how Cloud CDN works, see the Cloud CDN overview.