Reserved ip-addresses are a useful building block when running multiple workspaces that share information or when exposing a service to the internet. You can create and attach a reserved ip the same way you would create a storage volume.
The reserved ip feature provides you with a public, static network address. You assign the reserved ip to a new workspace. Subsequently this workspace will be accessible through this address.
This address being static means that it will not be changed or withdrawn - unless you choose to release it by deleting it in the dashboard. This is particularly useful when you want to expose a web server or build a network of workspaces. Other instances can rely on this address being present.
A reserved ip that you create is accessible from anywhere on the internet.
However, by default Research Cloud applications only open the ports that are required for SSH and RDP access to the workspaces. Also port 80 and 443 for a http and https, respectively, are opened.
In order to open other ports, please contact us through .
To create a new reserved ip, go to the "IP addresses" tab on the Research Cloud portal's dashboard.
Click on the green "+" on the top right of the (potentially empty) ip list.
The portal will guide you through the steps to create a new reserved ip:
Choose "SURF IP", "Azure IP" or "AWS IP". Depending on the cloud provider your workspaces will run on (and click continue).
Choose the CO you want to create the reserved ip for.
Choose the wallet that will fund the reserved ip, choose the cloud and the flavour.
In this last step give a unique name for the new reserved IP and a description.
Click on "SUBMIT" to have your new reserved ip created.
The user who creates the reserved ip remains its owner.
Only the owner can attach it to workspaces and delete it.
Once the reserved ip's state changes from "creating" to "available", you can attach the ip to a workspace you are creating. The status of the ip will change to "in use", then.
When creating the workspace, use the corresponding creation step to attach the reserved ip.
The reserved ip will become available again after the workspace it has been attached to is deleted.