[Yandex Cloud documentation](../../index.md) > [Yandex Cloud CDN](../index.md) > [Tutorials](index.md) > Migrating to Yandex Cloud CDN from a third-party CDN provider # Migrating to Yandex Cloud CDN from a third-party CDN provider If your dynamic website uses a third-party CDN to deliver static content to users, you can seamlessly migrate to Yandex Cloud CDN. This tutorial explains how to migrate while keeping your content accessible at all times. ## Solution architecture {#solution-overview} ![cdn-migration-tutorial](../../_assets/cdn/cdn-migration-tutorial.svg) To migrate smoothly, create a new [CDN resource](../concepts/resource.md) in Yandex Cloud CDN that uses the same [origin](../concepts/origins.md) as the third-party CDN. Register a new subdomain for the new CDN resource and create a new [TLS certificate](../../certificate-manager/concepts/managed-certificate.md) for the second-level domain and all its third-level subdomains in Yandex Certificate Manager. Once you have made sure the new CDN resource is working properly, update the static content links on your dynamic website accordingly. Then, remove the third-party CDN and add its domain name as an additional one to your Yandex Cloud CDN resource. Your dynamic website’s static content will stay continuously accessible as you migrate from a third-party CDN to Cloud CDN. To migrate a CDN resource to Yandex Cloud CDN: 1. [Get your cloud ready](#before-you-begin). 1. [Add a TLS certificate to Yandex Certificate Manager](#issue-certificate). 1. [Create a CDN resource in Cloud CDN](#setup-resource). 1. [Create a CNAME record for your new CDN resource's subdomain](#setup-subdomain). 1. [Update your website to use the new CDN resource](#update-website). 1. [Add an additional domain to the CDN resource in Cloud CDN](#add-secondary-domain). ## Getting started {#before-you-begin} Sign up for Yandex Cloud and create a [billing account](../../billing/concepts/billing-account.md): 1. Navigate to the [management console](https://console.yandex.cloud) and log in to Yandex Cloud or create a new account. 1. On the **[Yandex Cloud Billing](https://center.yandex.cloud/billing/accounts)** page, make sure you have a billing account linked and it has the `ACTIVE` or `TRIAL_ACTIVE` [status](../../billing/concepts/billing-account-statuses.md). If you do not have a billing account, [create one](../../billing/quickstart/index.md) and [link](../../billing/operations/pin-cloud.md) a cloud to it. If you have an active billing account, you can create or select a [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) for your infrastructure on the [cloud page](https://console.yandex.cloud/cloud). [Learn more about clouds and folders here](../../resource-manager/concepts/resources-hierarchy.md). ### Access to DNS settings {#dns-access} Make sure you can access the DNS settings on your DNS hosting provider’s website. This is usually the company that registered your domain. Your DNS provider's dashboard should already include a public domain zone matching your domain name, e.g., `example.com.`. This zone should contain a [CNAME record](../../dns/concepts/resource-record.md#cname) for your current CDN subdomain, e.g., `cdn.example.com`, pointing to the third-party CDN provider. ### Required paid resources {#paid-resources} The cost of the CDN infrastructure support includes fees for outbound traffic from CDN servers (see [Cloud CDN pricing](../pricing.md)). ## Add a TLS certificate to Yandex Certificate Manager {#issue-certificate} To ensure data encryption when accessing the new CDN resource, add a new [TLS certificate](../../certificate-manager/concepts/managed-certificate.md) issued by Let's Encrypt® for your website's domain and all its subdomains (wildcard certificate) to Yandex Certificate Manager: 1. Create a new TLS certificate: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) to add your certificate to. 1. Navigate to **Certificate Manager**. 1. Click **Add certificate** and select **Let's Encrypt certificate**. 1. In the window that opens, enter a name for your certificate in the **Name** field, e.g., `my-cdn-certificate`. 1. In the **Domains** field, specify the wildcard for your domain and its subdomains, e.g., `*.example.com`, where `example.com` is your website’s domain name. 1. In the **Check type** field, select `DNS`. 1. Click **Create**. - CLI {#cli} 1. Request a new wildcard certificate. Do it by running this command: ```bash yc certificate-manager certificate request \ --name my-cdn-certificate \ --domains "*." ``` Where: * `--name`: Certificate name, e.g., `my-cdn-certificate`. * `--domains`: Wildcard for your domain and its subdomains, e.g., `*.example.com`, where `example.com` is your website’s domain name. Result: ```text id: fpqba7lpgmp7******** folder_id: b1gt6g8ht345******** created_at: "2025-02-09T20:41:05.916923798Z" name: my-cdn-certificate type: MANAGED domains: - '*.example.com' status: VALIDATING updated_at: "2025-02-09T20:41:05.916923798Z" ``` Save the certificate ID (from the `id` field), as you will need it in the next steps. For more information about the `yc certificate-manager certificate request` command, see the [CLI reference](../../cli/cli-ref/certificate-manager/cli-ref/certificate/request.md). {% endlist %} 1. Follow these steps to verify ownership of your domain: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) you added the [certificate](../../certificate-manager/concepts/managed-certificate.md) to. 1. Navigate to **Certificate Manager**. 1. From the list of certificates, select the one you need verified. 1. In the window that opens, under **Check rights for domains**, you will see the details required to pass the domain rights check. In the **CNAME record** tab, copy and save the values of the **Name** and **Value** fields. You will need these to create a CNAME record. - CLI {#cli} 1. Retrieve the CNAME record values required for the domain rights check. To do this, run the following command while specifying the certificate ID you saved earlier. ```bash yc certificate-manager certificate get \ --full \ --format=json | \ jq -r ".challenges[].dns_challenge" ``` Result: ```json { "name": "_acme-challenge.example.com.", "type": "CNAME", "value": "fpqba7lpgmp7********.cm.yandexcloud.net." } { "name": "_acme-challenge.example.com.", "type": "TXT", "value": "oRnpmIJau5SWFDYqKwwUJMn-61HHdulvqk7********" } ``` Save the values of the `name` and `value` fields for the `CNAME` record. You will need these to create a CNAME record. For more information about the `yc certificate-manager certificate get` command, see the [CLI reference](../../cli/cli-ref/certificate-manager/cli-ref/certificate/get.md). {% endlist %} 1. Using the values from the previous step, create a CNAME record in your website's public DNS zone to verify your domain ownership: If you delegated your website domain to Yandex Cloud DNS, follow [this tutorial](../../dns/operations/resource-record-create.md) to create a CNAME record. Otherwise, use your DNS provider's guides or contact their support. {% note info %} For a successful DNS domain rights check based on a `CNAME` record, make sure the `_acme-challenge` subdomain of the domain name you are checking has no other [resource records](../../dns/concepts/resource-record.md) except `CNAME`. For example, for the `_acme-challenge.example.com.` domain name, there should only be a CNAME record and no TXT record. {% endnote %} Wait for the domain rights check to complete successfully. The wildcard certificate will then be issued and get the `Issued` status. You can check the certificate status on the certificate page in the [management console](https://console.yandex.cloud) or by running the `yc certificate-manager certificate get ` CLI command. ## Create a CDN resource in Cloud CDN {#setup-resource} This section explains how to create a CDN resource with the `Server` origin type. If your origin is a Yandex Object Storage [bucket](../../storage/concepts/bucket.md) or a [Yandex Application Load Balancer](../../application-load-balancer/concepts/application-load-balancer.md), use [this guide](../operations/resources/create-resource.md) to create a CDN resource. Create a CDN resource in Yandex Cloud CDN: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder you are going to create your CDN resource in. 1. Navigate to **Cloud CDN**. 1. Click **Create resource**. 1. Configure the basic CDN resource settings: * Under **Content**: * Enable **Enable access to content**. * In the **Content query** field, select `From one origin`. * In the **Origin type** field, select `Server`. * In the **Origin domain name** field, specify the domain name or public IP address of your static content origin. * In the **Origin request protocol** field, select the protocol the CDN resource will use to communicate with the origin. If you select `HTTPS` or `Match client`, make sure your origin supports HTTPS. * In the **Domain name** field, specify the new domain name you assigned to your new CDN resource, e.g., `cdn-new.example.com`. * Under **Additional settings**: * In the **Redirect clients** field, select `Don't use`. * In the **Certificate type** field, select `Use from Certificate Manager` and then, from the list that opens, select the certificate you created earlier, such as `my-cdn-certificate`. * In the **Host header** field, select `Primary domain name`. 1. Click **Continue**. 1. Under **Caching**, **HTTP headers and methods**, and **Advanced**, leave the default settings, then click **Continue**. - Yandex Cloud CLI {#cli} 1. Run this command: ```bash yc cdn resource create \ --origin-custom-source '' \ --origin-protocol '' \ --cert-manager-ssl-cert-id ``` Where: * ``: Domain name for which you created a CNAME record earlier and that the new CDN resource will use, e.g., `cdn-new.example.com`. * `--origin-custom-source`: Domain name or public IP address of your static content origin. * `--origin-protocol`: Protocol the CDN resource will use to communicate with the origin. The possible values are: * `http`: Use HTTP. * `https`: Use HTTPS. * `match`: Use the same value as that of the `Host` header in the client request to the CDN. If you select `https` or `match`, make sure your origin supports HTTPS. * `--cert-manager-ssl-cert-id`: TLS certificate ID saved earlier when creating the certificate. {% cut "Result" %} ```text id: bc8cfqtx2mkx******** folder_id: b1gt6g8ht345******** cname: cdn-new.example.com created_at: "2025-02-10T07:42:24.920162Z" updated_at: "2025-02-10T07:42:24.920187Z" active: true options: edge_cache_settings: enabled: true default_value: "345600" query_params_options: ignore_query_string: enabled: true value: true stale: enabled: true value: - error - updating origin_group_id: "352269" origin_group_name: Origins for cdn-new.example.com (302798) origin_protocol: HTTP ssl_certificate: type: CM status: READY data: cm: id: fpqnetjumkhn******** ``` {% endcut %} Save the new CDN resource’s ID (the `id` field value), as you will need it later. For more information about the `yc cdn resource create` command, see the [CLI reference](../../cli/cli-ref/cdn/cli-ref/resource/create.md). {% endlist %} {% note warning %} After the CDN resource is set up, it may take up to 15 minutes for it to go live. Make sure the new CDN resource is working properly before proceeding with the next steps. {% endnote %} ## Create a CNAME record for your new CDN resource's subdomain {#setup-subdomain} To seamlessly switch your website to the new CDN resource, you will need a new CDN subdomain. In your website's public DNS zone, create a CNAME record for the new CDN subdomain that the new CDN resource will use: * Record name: New CDN subdomain name, e.g., `cdn-new.example.com.`. * Record type: `CNAME`. * Record value: `cname` value for the new CDN resource, available in the [management console](https://console.yandex.cloud) on the CDN resource page (e.g., `e1b83ae3********.topology.gslb.yccdn.ru`). If you [delegated your website domain to Yandex Cloud DNS](../../dns/concepts/dns-zone.md#public-zones), follow [this guide](../../dns/operations/resource-record-create.md) to create a CNAME record. Otherwise, use your DNS provider's guides or contact their support. ## Update your website to use the new CDN resource {#update-website} Once you have created a new CDN resource in Cloud CDN and tested it, you can start updating your website configuration and removing the old CDN resource. ### Redirect links from the dynamic website {#redirect-links} Redirect the static content links your dynamic website generates to the new CDN subdomain, e.g., by replacing `cdn.example.com` with `cdn-new.example.com`. It is your dynamic website's admin who must do this. Once you have made all required changes, make sure the static content links your website generates are valid and the content is accessible. Also, make sure outbound traffic has stopped on the old CDN resource by using the statistics and monitoring tools from your third-party CDN provider. Your dynamic website has now fully switched to Yandex Cloud CDN. ### Update the CNAME record for the original CDN subdomain {#update-cname} To keep your website's original CDN subdomain working with the new Cloud CDN resource, replace the value of the resource CNAME record for the original subdomain with the one you got earlier: * Record name: Original CDN subdomain name, e.g., `cdn.example.com.`. * Record type: `CNAME`. * Record value: `cname` value for the new CDN resource, available in the [management console](https://console.yandex.cloud) on the CDN resource page (e.g., `e1b83ae3********.topology.gslb.yccdn.ru`). If you delegated your website’s domain to Yandex Cloud DNS, follow [this tutorial](../../dns/operations/resource-record-update.md) to update the CNAME record. Otherwise, use your DNS provider's guides or contact their support. ### Delete the third-party CDN {#delete-resource} Once you have confirmed the original CDN resource from your third-party CDN provider is no longer sending outbound traffic, delete it. To do this, use the third-party DNS provider's guides or contact their support. ## Add an additional domain to the CDN resource in Cloud CDN {#add-secondary-domain} Once you have deleted the third-party CDN resource that was using the original CDN subdomain, you can add that subdomain as an additional domain to your new Cloud CDN resource. Proceed as follows: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder with your CDN resource. 1. Navigate to **Cloud CDN**. 1. In the line with the CDN resource you created earlier, click ![ellipsis](../../_assets/console-icons/ellipsis.svg) and select ![pencil](../../_assets/console-icons/pencil.svg) **Edit**. 1. Under **Domain names for content distribution**, click ![plus](../../_assets/console-icons/plus.svg) **Add domain name** and then, in the field that appears, enter the domain name the old CDN resource used, e.g., `cdn.example.com`. 1. Click **Save**. - Yandex Cloud CLI {#cli} 1. Run this command: ```bash yc cdn resource update \ --secondary-hostnames '' ``` Where: * ``: Cloud CDN resource ID you saved [earlier](#setup-resource). * `--secondary-hostnames`: Domain name that became available after deleting the third-party CDN resource, e.g., `cdn.example.com`. {% note warning %} This command will delete all additional domains previously linked to the CDN resource. To link an additional domain to a CDN resource that already has additional domains linked, list the domains in the `--secondary-hostnames` parameter while separating them with commas. {% endnote %} {% cut "Result" %} ```text id: bc845trezddi******** folder_id: b1gt6g8ht345******** cname: cdn-new.example.com created_at: "2025-01-25T21:47:21.181871Z" updated_at: "2025-02-10T17:10:37.511453Z" active: true options: edge_cache_settings: enabled: true default_value: "345600" query_params_options: ignore_query_string: enabled: true value: true stale: enabled: true value: - error - updating ignore_cookie: enabled: true secondary_hostnames: - cdn.example.com origin_group_id: "350569" origin_group_name: Origins for cdn-new.example.com (301532) origin_protocol: HTTP ssl_certificate: type: CM status: READY ``` {% endcut %} For more information about the `yc cdn resource update` command, see the [CLI reference](../../cli/cli-ref/cdn/cli-ref/resource/update.md). {% endlist %} Updating the CDN resource settings may take up to 15 minutes. After that, your new CDN resource will be accessible via both domain names, i.e., `cdn-new.example.com` and `cdn.example.com`. #### See also {#see-also} * [Creating a CDN resource](../operations/resources/create-resource.md) * [Adding a Let's Encrypt® certificate](../../certificate-manager/operations/managed/cert-create.md) * [Getting started with Cloud DNS](../../dns/quickstart.md)