For whom: Panel Administrator Required Rights: CDN Account Management.
Supported providers
Each provider declares its capabilities with a level of confirmation (from “stated in documentation” to “verified with real keys”). A capability described only in the provider’s documentation is never considered a production warranty without verification with credentials.
Manual mode is hidden from the list of providers when you connect a new account, but previously created manual accounts continue to work.
Preliminary requirements
- A valid account with the provider and keys with the necessary rights.
- For Yandex Cloud, an authorized service account key (JSON) and directory ID (Folder ID) are required; a service account requires the roles of
cdn.editorandcertificate-manager.editor; and access to Cloud DNS (dns.editor) is also required to automatically manage the DNS zone.
Account connection
The set of fields depends on the provider. The panel shows the desired fields and hints in the account add wizard.1
Open the CDN section and select the provider.
Click on the new account connection and select the provider from the list.
2
Fill in the credentials.
Enter the fields from the provider schema (for Yandex Cloud – JSON authorized key and Folder ID) and the account name.
3
Save it.
For Yandex Cloud, authentication and access to the CDN API, Certificate Manager API and Cloud DNS API are verified; missing rights are listed as
cdn.editor, certificate-manager.editor, dns.editor.Failed verification does not block saving: an account will be created with an error-reflecting status – you can fix the keys and recheck them later.
Secrets: Recorded only
Credentials - write-only:- secrets are encrypted when stored and stored only in encrypted form;
- No API method brings secrets back, either in whole or in part.
Account statuses
Status reflects the result of the last check, along with the time of the check and the human-readable reason.
Key rechecking
The button Check the keys in the account card (or request below) re-starts the check with the provider and updates the status and time of the last check:Archiving and disposal
- Archive is a reversible operation: the account is hidden from the lists, but it can be returned (
PATCHwith"archived": false). The archived accounts are visible in the list with the?include_archived=1parameter. - Deletion is irreversible: the account is deleted along with the stored secret. If the account is linked to CDN resources, deletion is blocked from HTTP 409 - first remove the CDN blocks or use the archive.
Verification
Your account is ready when you click Check the keys. his status became
valid (Ready), and the time of the last check has been updated.- If the
permission_limitedstatus – the panel lists the missing roles; issue them to the service account with the provider and double-check.
Rollback
- Incorrect keys – transfer the correct values through the account editing: the old secret will be replaced, the new check will start automatically.
- The account is no longer needed, but has been used by resources - archive it (reversibly) and can only be deleted after no CDN resource links to it.
- Full rollback: Delete the CDN blocks using the account (see Resources and Operations ), then delete the account - the secret will be deleted along with it.
Typical errors
Deleting your account returns HTTP 409
Deleting your account returns HTTP 409
The account is used by CDN resources. The panel suggests archiving it instead of deleting it. To delete it permanently, first uninstall the associated CDN blocks.
Status of invalid or error
Status of invalid or error
invalid – keys do not pass authentication: check that the full authorized key and the correct Folder ID have been inserted. error – verification has not been performed (for example, the provider API is not available): repeat Check the keys later.