Table of Contents
Note: This feature is only supported by the Dashboard and not the API.
The Index page displays the current port forwarding rules in effect. Port forwarding is used to enable communications between external hosts and services offered within a VLAN (virtual local area network) in a private cloud. As a common use case, you could use port forwarding rules to enable external hosts to access SSH or HTTP services on a specific instance and port in your VLAN. Port forwarding is often known as port mapping, because a request on a public port gets _mapped_ to a private port number. The port can be the same on both sides, or mapped from any open external port to any open internal port. Unlike port forwarding in traditional computing, in virtual environments (such as cloud infrastructures that support port forwarding capabilities) you can have multi-tenant IP addressing. That is, a virtual instance in the cloud could support more than one IP address. This offers a lot of flexibility on how to forward network traffic for a given IP:Port combination, and is also why both an IP address _and_ Instance name are required when configuring port forwarding rules.
Note: Think of port forwarding as another networking "mode". Instead of the standard Security Group model, port forwarding is how some cloud infrastructures implement a virtual networking mode. Depending on the cloud's implementation, both modes may co-exist. That is, the cloud may support one mode or the other, both modes, or some hybrid of both. (For example, the cloud supports both networking modes as a whole, but within a given Datacenter / Zone only one mode can be configured.) A summary view of port forwarding looks like this:
public_IP:public_port -> instance:private_port.
Clouds > Private Cloud
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.