> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gcore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Gcore CDN delivers websites, files, and video from an origin through edge servers, configured per CDN resource.

[Gcore CDN](https://gcore.com/cdn) delivers websites, files, and video to end users from servers close to them. This helps content load faster and reduces requests to the servers that hold the original files. The CDN also lets you control who can access the content, block malicious requests, and reduce file size.

> [card] Connect a domain
>
> Start by creating a [CDN resource](https://docs.gcore.com/cdn/getting-started/create-a-cdn-resource/overview.md): add the origin that holds the files and the domain to serve them from, then point the domain to the CDN.

You can also use a CDN resource to deliver video with [Video CDN](https://docs.gcore.com/cdn/video-cdn/video-cdn-overview.md), as long as the content is already prepared for playback.

## Delivery settings

These areas shape the [delivery path](https://docs.gcore.com/cdn/how-cdn-works.md): where content comes from, how it is cached and delivered, and who can access it.

> [card] Origins
>
> An [origin group](https://docs.gcore.com/cdn/add-an-origin-group.md) points the CDN at the server, bucket, or FastEdge HTTP application that holds the files, and can combine several origins. To reduce the load on that origin, [Origin Shielding](https://docs.gcore.com/cdn/cdn-resource-options/general/enable-and-configure-origin-shielding.md) adds a cache layer in front of it.

> [card] Cache
>
> Cached files stay on the CDN for the [cache lifetime](https://docs.gcore.com/cdn/cdn-resource-options/cache/specify-cache-lifetime-on-a-cdn-resource-or-origin.md). A file can enter the cache earlier with [Prefetch](https://docs.gcore.com/cdn/load-the-content-to-cdn-before-users-request-it.md), which loads it before the first request, and leave earlier with [Purge](https://docs.gcore.com/cdn/clear-cdn-resource-cache-by-url-pattern-or-all.md), which removes it before that lifetime ends.

> [card] Secure connections
>
> Enable HTTPS for end users by adding an [SSL certificate](https://docs.gcore.com/cdn/ssl-certificates/add-an-ssl-certificate-to-deliver-content-over-https.md). You can also select the [origin pull protocol](https://docs.gcore.com/cdn/cdn-resource-options/general/specify-an-origin-and-the-origin-pull-protocol.md) the CDN uses to connect to your server over HTTP or HTTPS.

> [card] Access and security
>
> [Access policies](https://docs.gcore.com/cdn/cdn-resource-options/security/control-access-to-the-content-with-country-referrer-ip-and-user-agents-policies.md) and [secure token](https://docs.gcore.com/cdn/cdn-resource-options/security/use-a-secure-token/about-secure-token.md) decide who can request files, and [WAAP](https://docs.gcore.com/cdn/cdn-resource-options/cdn-security/protect-cdn-resources-with-waap.md) can block malicious HTTP requests before they reach the origin.

> [card] Per-file settings
>
> Use [Rules](https://docs.gcore.com/cdn/cdn-resource-options/rules-for-particular-files/create-a-rule-manually-or-from-a-template-to-configure-settings-for-particular-files.md) to control how specific files are delivered. For example, images can be cached longer than HTML pages.

> [card] Image optimization
>
> Make images load faster with [Image Stack](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/about-image-stack.md), which automatically resizes and converts them while the originals stay unchanged.

## Monitoring and logs

Monitor CDN performance, analyze traffic, and investigate individual requests using reports and logs.

* [Reports](https://docs.gcore.com/cdn/view-statistics-of-a-cdn-resource.md): traffic, response codes, and cache performance in the Customer Portal.
* [Grafana](https://docs.gcore.com/cdn/grafana/view-cdn-statistics-in-grafana.md): the same kind of metrics in Grafana, outside the Customer Portal.
* [Log viewer](https://docs.gcore.com/cdn/logs/log-viewer-view-and-download-cdn-resource-logs.md): requests from the last three days.
* [Logs Uploader](https://docs.gcore.com/cdn/logs/logs-uploader.md): export of request logs to external storage.

## Billing and troubleshooting

Find out how CDN usage is billed and what to do when content isn't delivered.

* [Billing](https://docs.gcore.com/cdn/how-the-cdn-service-and-its-additional-options-are-billed.md): plans, usage limits, and charges above them.
* [Troubleshooting](https://docs.gcore.com/cdn/troubleshooting/common-setup-issues.md): fixes for content that isn't delivered after setup.

## Integrations and advanced options

* [FastEdge](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-fastedge.md): custom code that runs on requests and responses inside the CDN.
* [Terraform](https://docs.gcore.com/developer-tools/terraform/overview.md): CDN resources, origin groups, and settings managed as code.
* [CMS integration guides](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms.md): connecting common CMS, ecommerce, and storage systems to a resource.
* [Dedicated IP](https://docs.gcore.com/cdn/ip-configuration-options/dedicated-ip.md) and [BYOIP](https://docs.gcore.com/cdn/ip-configuration-options/byoip.md): exclusive addresses instead of shared ones, either reserved by Gcore or the customer's own prefix.
