Discuss with expertTry it for free
© 2026 Direct Cursus Technology L.L.C.

Migrating CDN resources and origin groups to Yandex Cloud CDN

Written by
Updated at July 20, 2026
View in Markdown

Starting January 22, 2026, our Cloud CDN partner, EdgeCenter (EdgeCDN provider), will stop providing CDN on the Yandex Cloud platform.

Yandex Cloud will automatically migrate CDN resources and origin groups from EdgeCDN to Yandex Cloud CDN by January 17, 2026. After the migration, the service will cost the same.

To start using your migrated CDN resources and origin groups:

  1. Enable access to the content.
  2. Verify your TLS certificate.
  3. Edit the CNAME record.
  4. Check origins for protection against information attacks.
  5. Test the resource.

Enable access to the content

  1. In the management console, select the folder housing your CDN resource from the EdgeCDN provider.
  2. Navigate to Cloud CDN.
  3. In the list of resources, find your migrated CDN resource. Make sure its provider is Yandex Cloud CDN and its primary domain name is the same as in EdgeCDN.
  4. If the Status column of the migrated CDN resource says Not active, enable access to the content:
    1. Click next to the resource and select Edit.
    2. Under Content, enable access to the content and click Save.

Note

It may take up to 15 minutes for the new CDN server settings to take effect.

Verify your TLS certificate

If you previously uploaded a TLS certificate for the original CDN resource, select the new CDN resource that has Yandex Cloud CDN as provider in the management console and make sure your certificate name is specified in the Certificate type section.

Warning

Previously, EdgeCDN supported issuing TLS certificates automatically for CDN resources. In CDN resource settings, such certificate type is shown as Let's Encrypt®.

You cannot migrate such certificates from EdgeCDN to Yandex Cloud CDN. Instead, issue a new Let's Encrypt® certificate or upload a custom one through Yandex Certificate Manager and specify it in the settings of the migrated CDN resource.

Editing the CNAME record

  1. Learn the current CNAME record value:

    1. Select the CDN resource with the Yandex Cloud CDN provider you created.
    2. Under DNS settings, copy the CNAME value, i.e., e1b83ae3********.topology.gslb.yccdn.ru.

  2. In your DNS hosting settings, change the CNAME record value from the one pointing to the EdgeCDN domain name to the one pointing to Yandex Cloud CDN.


    Example of the original record for EdgeCDN:

    cdn.example.com. CNAME cl-msa87*****.edgecdn.ru

    Example of the edited record for Yandex Cloud CDN:

    cdn.example.com. CNAME e1b83ae3********.topology.gslb.yccdn.ru

    Tip

    If you use Yandex Cloud DNS for DNS hosting, check out this guide.

    The new resource will start running properly after the CNAME record you edited on your DNS hosting gets propagated across DNS servers. This may take a few hours. For details, see this section on domain names for content distribution.

    Note

    Do not use an ANAME resource record with domain names for content distribution; otherwise, the end user will get a response from a CDN server not linked to the user geolocation. The response will always be the same for all users.

Check origins for protection against information attacks

If the origin you are adding to Yandex Cloud CDN has information security measures in place, e.g., a firewall or DDoS protection, make sure Yandex Cloud CDN addresses are whitelisted.

Test the resource

Once your CNAME record gets propagated across DNS servers, client requests will start arriving to your new CDN resource.

To check whether your resource works properly:

  1. In the management console, select the folder where the CDN resource was created.
  2. Navigate to Cloud CDN.
  3. Select the CDN resource you previously created.
  4. Navigate to the Monitoring tab.

Useful links