Migrating CDN resources and origin groups to Yandex Cloud CDN
Starting January 22, 2026, our Cloud CDN partner, EdgeCenter, will stop providing CDN on the Yandex Cloud platform.
For this reason, you will need to migrate your CDN resources from EdgeCDN to Yandex Cloud. When switching, the cost of using the service will remain the same. You can either do it on your own or as part of the partial auto-migration process we will complete by January 17, 2026.
To migrate your CDN resources and origin groups from the EdgeCDN provider to Yandex Cloud CDN:
- Migrate the existing resource configuration.
- Edit the CNAME record.
- Check whether your resource works correctly.
Migrating the existing resource configuration
-
In the management console
, select the folder housing your CDN resource managed by the EdgeCDN provider. -
Go to Cloud CDN.
-
Click Create resource.
-
Under Copy a configuration, select your CDN resource managed by the EdgeCDN provider (the one you want to migrate to Yandex Cloud CDN).
Tip
You can find the provider name under the resource domain name.
-
All settings will get populated automatically as per the original CDN resource configuration. You can adjust them, if required.
Note
When migrating from EdgeCDN to Yandex Cloud CDN, you can keep your resource’s Domain name. The name must be unique across the resources of a single CDN provider.
-
Click Continue.
-
If required, adjust the settings under Caching, HTTP headers and methods, and Additional settings, and then click Continue.
Wait until this new CDN resource appears in the list as managed by Yandex Cloud CDN.
Apart from this new CDN resource, the system will also create a copy of your origin group.
-
If you uploaded a TLS certificate for the original CDN resource, select your new CDN resource that has Yandex Cloud CDN as provider and make sure the Certificate type section has your certificate name specified.
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 when migrating your CDN resource.
Editing the CNAME record
-
Learn the current CNAME record value:
Management console- Select the CDN resource with the Yandex Cloud CDN provider you created.
- Under DNS settings, copy the CNAME value, e.g.,
e1b83ae3********.topology.gslb.yccdn.ru.
-
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.ruExample of the edited record for Yandex Cloud CDN:
cdn.example.com. CNAME e1b83ae3********.topology.gslb.yccdn.ruTip
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.
Checking whether your resource works correctly
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:
- In the management console
, select the folder where the CDN resource was created. - Go to Cloud CDN.
- Select the CDN resource you previously created.
- Navigate to Monitoring.
Partial auto-migration
By January 17, 2026, we will automatically migrate your CDN resources by copying them with saved settings and transferring to Yandex Cloud CDN.
All you will need to do is replace the CNAME domain record in your DNS hosting settings.