CDN
Configure CDN to receive renewed certificates automatically.
1. Overview
A Gcore - CDN node deploys certificates to this configured target.
2. Configuration
Select this platform and deployment position, then supply the following parameters.
| Field | Required | Description |
|---|---|---|
| API Token | Yes | |
| CDN Resource ID | Yes |
3. Deployment and renewal
- Use a permanent API key with CDN resource and certificate permissions. New certificates are bound to this resource. Old certificates are retained because they may be shared.
Associate the certificate with the node and enable automatic deployment on renewal. Certificate replacement uses the same configured target on every run.
Old certificate objects are retained to avoid deleting certificates referenced elsewhere. Monitor the platform certificate quota and remove unused objects separately. Repeating a successful deployment of the same PEM certificate reuses its generated certificate name.
Deployment partially updates sslData and enables HTTPS with PATCH, preserving other CDN resource options. A successful API response confirms the binding rather than global edge propagation.
4. Verification
Automated protocol tests cover request construction, failure handling and credential redaction. This integration has not been tested against a live account or device in this change. A successful configuration check verifies connectivity and read access; the first deployment also verifies write permissions.