Help us make these docs great!

All docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Custom URLs for Services

Create a Static Route

  1. On the left navigation bar, click Networking>Static Route.


  3. Enter a name for Static Route URL.

    The name of a static route has lowercase alphanumeric characters, or a hyphen, and must begin and end with an alphanumeric character, and must not be certain keywords, and it must be at least 4 characters and less than 64 characters long.

  4. Click CONTINUE. The static route is created.

    Observe that the name of the static route will be a subdomain belonging to (essentially the provided name will be suffixed with to form the FQDN). For instance, if the name of the static route is my-example-server, the static route URL will be

    Create static route

Once created, you cannot edit the name of a static route. You can however delete and recreate a new static route with a different name easily.

Binding Static Route to Deployment Endpoints

To bind a static route to an externally exposed endpoint, which is defined in a package, during the deployment process:

  1. Click Add Static Route.

Add static route

  1. Select an external network endpoint from the drop-down list.

  2. Select a static route from the drop-down list.

Select endpoint static route pair

This creates a mapping between an external network endpoint and a static route.

You can unbind a static route from a network endpoint by clicking on the delete icon.

In this example, the static route my-example-server is bound to the network endpoint server_endpoint as shown below:

Bind static route

On deploying the package after binding a static route, the network endpoint URL address becomes deterministic and is a constant. It implies that even if the deployment is stopped and provisioned again with the same static route, the network endpoint URL address remains the same.

A package deployment can have multiple static routes. However, a single static route is used for a single deployment.

Refer to billing and usage to understand the limits applied on static routes for different subscription plans.