Copying a configuration from one resource to another
You can set CDN resource parameters from a configuration of another CDN resource. To do this, in the Copy a configuration field, select an existing CDN resource. Keep in mind the following:
- You can migrate the Domain name parameter from the CDN resource of one CDN provider to another. The name must be unique across the resources of a single provider.
- Copying parameters between resources of different providers creates a copy of the origin group in the provider of the new resource.
- If the original resource has an uploaded TLS certificate, it will be reused in the new resource. You do not need to upload it again.
-
In the management console
, select the folder where you want to create a resource. -
Go to Cloud CDN.
-
Click Create resource.
-
In the Copy configuration field, select an existing CDN resource whose settings you want to copy to a new one.
-
If required, adjust the settings.
Warning
The Domain name parameter must be unique within the resources of one CDN provider.
-
Click Continue.
-
If required, adjust the settings under Caching, HTTP headers and methods, and Advanced, then click Continue.
Once the CDN resource is created, get the CDN provider's domain name and create a CNAME resource record for the specified name in your DNS hosting settings, e.g., in Yandex Cloud DNS. For more information, see Domain names for content distribution.
Sample resource record:
cdn.example.com. CNAME 328938ed********.a.yccdn.cloud.yandex.net
The new resource will start running properly after the CNAME record that you created on your DNS hosting (see Host names) is propagated across DNS servers. This may take several hours.
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.
For a CDN resource with the EdgeCDN provider, you can configure advanced settings. For a complete description of its features, see the CDN provider's API documentation