Share an HTTP application over HTTPS

Choose exactly what becomes public

For a virtual machine, start an HTTP server and select the guest port it listens on. For a K3s cluster, identify the Kubernetes namespace, Service and Service port. The console tracks setup until the public route is active.

The public HTTPS endpoint routes to the selected HTTP application. It does not expose the whole private network or make the Kubernetes API public. Publishing is a separate operation from creating a VM or cluster.

Public means reachable by other people

Anyone who has the generated address can reach your published application. DCS console sign-in does not authenticate visitors to your application. Add authentication in the application itself when you need to restrict its contents.

Review what the application reveals before publishing: development dashboards, debug pages, tokens and internal data should not be available to anonymous visitors. HTTPS protects the connection to the public endpoint; it does not decide who may use your application.

Publish, check and withdraw

1. Make sure the application responds to HTTP on the private side first.
2. Open Public HTTPS for the resource and enter the application name and target details.
3. Wait for the route to become active, then test the generated address from outside the private network.
4. Use Unpublish to withdraw access. Wait for removal to complete and check the old address before treating the route as closed.

What this beta covers

The publishing scope is HTTP applications behind a generated HTTPS address. General TCP, public SSH and WebSocket publishing are outside this beta scope. Do not assume support for custom domains or an uptime guarantee.

Beta launch checks are still in progress and new customer deployments are paused. The guide describes the workflow for an enabled environment; it is not an announcement that public customer provisioning has opened.