First, you'll need to create a rule mapping the Public IP you want to use for your VM in your iland Secure Cloud environment to the internal IP of that machine. If you have multiple environments, be sure that you first navigate to the correct Edge Gateway in the Console under the vDC level Networking tab.
Go to the networking page in the Console from the Secure Cloud Org level dashboard. Once it loads, select the location of the Edge Gateway you want to modify in the navigation tree below. For each location, you should see the following list of edges displayed in the main window.
Select the gateway you want to work with from the list, and you will be brought to the configuration page for that gateway.
Scroll down the page to the very end until you see the Panel labeled "NAT". It should look something like this:
By default, all iland Secure Cloud environments should have a Source NAT (SNAT) rule similar to the one above that allows for outbound traffic through the public IP of the Edge Gateway. You'll need to add a Destination NAT (DNAT) rule to map the public IP to your VM. To do this, click the "Manage NAT" option. This will open a modal that will allow you to add or edit all of the NAT rules for your environment, all in one place. Click the "Add NEW DNAT Rule" button in the top right corner of this window, and another window will open allowing you to configure the rule.
In this window, you will see the following fields and options:
Once you have created your own rule, click the "Submit" button. If you need to create multiple rules, you can do this here.
Note: It is possible with DNAT rules to map several services across machines to a single public IP using port-based NAT rules. However, in most cases, customers prefer a one to one scenario when it comes to mapping public IPs to machines, and iland recommends this for simplicity if it fits your needs.