node.example.com node, the panel will create a cdn.node.example.com.
For whom: panel administrator. Required rights: full access to the panel (management of integrations and Flow).
How it works.
1
Connect to a CDN provider account
In the CDN panel, select the provider and fill in the credentials fields. The panel will check the keys immediately when you save. For more information, see Providers and accounts .
2
Add a CDN block to Flow
In the constructor, connect the gateway → CDN block → input node. the CDN block should lead exactly to one input node with the configured domain; in one Flow, only one CDN block is supported.
3
Apply the configuration
When you use Flow, the dashboard starts the provisioning operation: the delivery domain, TLS, CDN resource, DNS recording and end-to-end verification. There is no separate button to create a CDN, everything happens inside the Flow application.
Idempotence and state journal
Each provisioning is a operation with a state log: it goes through clear steps (validation, resource creation, waiting for DNS and certificate, verification) to the final status ofREADY. Operations are deterministic and idempotent:
- Reuse of the same Flow reuses an existing binding rather than creating duplicates.
- If the CDN is already ready, re-use is completed immediately.
- If the checks have not passed, re-use re-checks the resource and can transfer it to the finished state when the problem is eliminated.
The principle of fail-closed
The panel deliberately distrusts the status of “ready” on the provider side. The resource is considered ready only after a full set of empirical checks: DNS recording is visible on both authoritative servers and public solvers; TLS is valid on both the delivery domain and the origin node; functional tests (HTTP methods, no caching, transport) have been passed. If the CDN isn’t ready, the Flow application ends up with a mistake — the configuration won’t “go halfway” — which protects you from a situation where traffic is directed to a CDN that doesn’t actually work.Section map
Providers and accounts
What providers are supported, how to connect and verify an account.
Resources and operations
Operation life cycle, READY conditions, rollback.
DNS and Cloudflare AutoDNS
Automatic DNS node records and domain pools.
Observability
Statuses, error codes and transaction logs.
Troubleshooting
Typical scenarios and diagnostic procedure.
Flow
Input point constructor in which the CDN block lives.
Restrictions
- One CDN block on Flow.
- The CDN block should be allowed in exactly one physical input node with the domain.
- Full automation is now only available for Yandex Cloud; other providers – see Providers and accounts.
- Origin-node must respond to HTTPS with a valid certificate before the start of providing.
