Help us make these docs great!

All rapyuta.io 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. In the rapyuta.io console, on the left navigation bar, click Networking > Static Routes.

  2. Click Add New Static Route.

  3. Enter the 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 .ep-r.io (essentially the provided name will be suffixed with .ep-r.io to form the FQDN). For instance, if the name of the static route is my-example-server, the static route URL will be my-example-server.ep-r.io.
    • You cannot edit the name of a static route. However, you can delete and recreate a new static route with a different name.

Binding Static Route to Deployment Endpoints

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

  1. Click Add Static Route.

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

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

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.

Below is an example of the static route my-example-server which is bound to the network endpoint server_endpoint.

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.