Timeweb Cloud connects S3 static sites to a CDN and custom domains

Timeweb Cloud has added one-click CDN connectivity for static websites hosted in its S3 object storage. A site can now use a custom third-level domain instead of exposing the storage service’s technical address.

A simpler static-delivery architecture

A static site is a collection of HTML, CSS, JavaScript, and media that does not require server-side rendering for every request. Object storage can hold those artefacts, while a CDN caches copies closer to visitors and reduces repeated reads from the origin bucket.

A custom domain gives users and search engines a stable address. The underlying storage arrangement can change later without replacing public links or exposing an infrastructure-specific hostname.

Checks before moving traffic

• review the DNS record and lower its TTL before migration;
• issue and validate a TLS certificate for the hostname;
• set accurate Content-Type values for every asset class;
• use separate cache policies for HTML and versioned static files;
• configure 404 responses and directory-index behaviour;
• keep source maps, build inputs, and operational files out of the public bucket;
• test invalidation or adopt content hashes in asset names.

HTML usually needs a short lifetime or revalidation, while fingerprinted assets can remain at the edge much longer. Mixing those policies can leave a new page pointing to an asset that no longer exists or keep an old document visible after deployment.

What the announcement does not specify

The changelog confirms CDN and custom-domain support but does not provide pricing, edge geography, SLA terms, invalidation limits, or all supported response-header controls in this entry. Those points should be checked in the service documentation and validated on a non-production hostname.

Source: the official Timeweb Cloud changelog dated 9 September 2026.