> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Providers and accounts

> Supported CDN providers, account connection, key verification, statuses and archiving.

A CDN provider account is a reusable credentials profile: you connect it once and then use it for any number of CDN blocks. The panel checks the keys when you create and when you update them, stores the secrets in encrypted form, and never gives them back.

> [!NOTE]
>
> For whom: Panel Administrator Required Rights: CDN Account Management.

## Supported providers

| Provider | Mode | What does it mean |
| - | - | - |
| Yandex Cloud CDN | Full automation | The only provider with working automatic provisioning: domain, TLS, CDN resource and DNS are created by the panel. |
| VK Cloud CDN | Candidate | Keys can be saved, but the account receives the status of `permission_limited`: the provider is not qualified for production until the checks of the contract, TLS, cache and transport with real credentials. |
| Selectel CDN | Candidate | Similar to VK Cloud: Key Storage - Yes, Automatic Provisioning - Not Yet. |
| Beget CDN | Candidate | Similar to VK Cloud and Selectel. |
| Timeweb CDN | Instruction Mode | Timeweb does not have a public CDN management API; only the Instruction/Import mode and DNS verification are available. |
| Manual Mode (Manual) | Manual setting | You configure the CDN in the provider console yourself; the panel only stores notes in free form and does not check any keys. When applying the configuration, the panel does not call the provider's API, but generates instructions for manual configuration. |

> [!NOTE]
>
> 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.

> [!NOTE]
>
> Manual mode is hidden from the list of providers when you connect a new account, but previously created manual accounts continue to work.

Cloudflare is not intentionally on this list: it is not a CDN provider, but a separate integration of AutoDNS for node records – see [DNS and Cloudflare AutoDNS](https://docs.axottle.com/en/cdn/dns.md).

## 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.editor` and `certificate-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`.

> [!NOTE]
>
> 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 | Value |
| - | - |
| `draft` | Account saved but not yet verified with the provider. |
| `valid` | Check passed - account ready to use. |
| `permission_limited` | Keys are authenticated, but there are not enough rights; the list of missing roles is shown in the dashboard, and this status is obtained by candidate providers before qualifying. |
| `invalid` | Keys are not authenticated from the provider. |
| `expired` | Credentials expired. |
| `error` | Check ended in error (e.g. provider unavailable). |
| `archived` | Archive Account: hidden from lists and not used for new blocks. |

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 (`PATCH` with `"archived": false`). The archived accounts are visible in the list with the `?include_archived=1` parameter.
* **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

> [!TIP]
>
> 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_limited` status – 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 ](https://docs.axottle.com/en/cdn/resources-and-operations.md)), then delete the account - the secret will be deleted along with it.

## Typical errors

> [accordion] Authorization\_limited status immediately after connection
>
> For Yandex Cloud, the service account lacks roles – the panel will list the missing ones (`cdn.editor`, `certificate-manager.editor`, `dns.editor`). For VK Cloud, Selectel and Beget, this is the expected behavior: the provider is not yet qualified for automatic provisioning.

> [accordion] 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.

> [accordion] 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.

Related pages: [ Resources and operations ](https://docs.axottle.com/en/cdn/resources-and-operations.md), [ Observation ](https://docs.axottle.com/en/cdn/observability.md), [Flow](https://docs.axottle.com/en/connection-units/overview.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.