The CloudBase HTTP Gateway brings two new capabilities: after binding a custom domain, you get global edge acceleration with built-in edge security protection; and Cloud Storage files can now be connected to the gateway and served independently through a custom domain.
Custom domains support global edge acceleration
The HTTP Gateway's custom domains connect to global edge nodes covering 9 major regions — Mainland China, North America, Europe, Asia Pacific, the Middle East, Africa, and South America — and requests are answered by the nearest edge node.
- Global nearest-node access: requests are served by the edge node closest to the user, so overseas traffic no longer detours back to the origin;
- Lower latency: static assets are cached at edge nodes for faster first-screen loading;
- Edge security protection: the acceleration link comes with edge-layer protection built in — no need to integrate a WAF yourself.
Best suited for: developers building mini programs for overseas markets, cross-border H5, and global web services; businesses sensitive to first-screen and access latency; teams that want acceleration and security protection unified on a single link.
Steps:
- Go to "HTTP Gateway → Add Domain" and choose "CloudBase access" as the access method;
- Turn on the "Edge Acceleration" switch, complete domain ownership verification as instructed, and add the corresponding DNS TXT record;
- Once the domain status is normal, configure the CNAME record provided on the page in your DNS console;
- Configuration takes about 10–20 minutes to take effect.
Once enabled, two fees apply — accelerated traffic and accelerated request count — tiered by the region of the access source. See the billing documentation for details.
Cloud Storage connects to the HTTP Gateway
Cloud Storage can bind a custom domain and serve content externally through the HTTP Gateway's edge acceleration link. A single file can be bound to multiple custom domains, each with its own trigger path.
Value for developers:
- Unified domain management: Cloud Storage, HTTP services, and static hosting share one set of domains, configured once in the HTTP Gateway and effective globally;
- Flexible trigger paths: access paths are customizable — for example, after binding
/storage,images/logo.pngis available athttps://your-domain/storage/images/logo.png; - Multi-domain, multi-client reuse: the same file can be bound to multiple domains, so the client app and the admin console each use their own address without interfering with each other.
Best suited for: teams running multiple clients (client app, admin console, and marketing site sharing the same assets); long-term, large-scale projects (wanting tidy domains, routing, and asset structure for easier troubleshooting); individual developers and small teams (no dedicated ops, wanting domain, certificate, acceleration, and protection configured in one go).
Steps: there are two configuration entry points — pick whichever you prefer:
- "Cloud Storage → Domain Management → Add Domain": bind directly and fill in the trigger path — the fewest steps.
- "HTTP Gateway → Route Management → Associate Resources with Domain": click New and choose "Cloud Storage" as the resource type — ideal when managing HTTP services and static hosting together.
Domains for all three resource types are managed in the HTTP Gateway
Domains for HTTP services, static hosting, and Cloud Storage can now all be managed in one place — the HTTP Gateway.
Existing domains can be migrated based on your business needs
The global edge acceleration capability is available to Standard Edition users. Developers who connected domains through the former "CloudBase CDN" can switch the access method to "CloudBase access", enable edge acceleration, and complete the migration by following the on-screen instructions.
Developers still using the default domain can also migrate files to a custom domain with this upgrade. Once connected, feel free to leave a comment on our official account, or reach out to @CloudBase and friends on Xiaohongshu to share your experience.
