Multiple Public IP Addresses for a Single Container
CirrusGrid PaaS supports assigning multiple public IP addresses (of both IPv4 and IPv6 revisions) to a single container. Herewith, the assigned IPs could be either of one of the versions or both of them simultaneously.
For example, if hosting several web-sites on a single node, the multi-IP option allows to handle them as separate production-ready services due to the ability to apply dedicated custom domain name and SSL certificate to each of them. Also, this option can be helpful for operating network appliances (e.g. load balancers) with multiple IP addresses for each network.
Tip: Both Public IPv4 and IPv6 are paid options, charged separately (either for the same or different price) on hourly basis. The exact cost and allowed number of IPs per node/per environment can be seen within the Quotas & Pricing > Account Limits dashboard tab.
You can assign multiple IP addresses through your CirrusGrid dashboard by means of the appropriate spinners at topology wizard when either creating an environment or changing its topology.
Here, you can select or enter the required number of addresses of both types through the appropriate Public IPv4 and Public IPv6 boxes. If meeting the limits, please, contact us to increase the available addresses count.
Managing Multiple Public IP Addresses #
On the main dashboard screen, each node within the environment topology list is supplemented with details on all assigned IP addresses, displayed in the following order:
- Private IP – automatically attached internal IP address; is always displayed first just under the Node ID value
- Public IPv4 – single external IP record or expandable list of all v4 addresses, comes second
- Public IPv6 – single external IP record or expandable list of all v6 addresses, appears last
Also, you can Copy to clipboard and Detach each particular address using the appropriate buttons. And the Attach/Detach IP(s) option next to the addresses list title allows to adjust the total number of assigned IPs of the corresponding type, i.e. for each block separately:
The Node Settings box displays the number of currently attached addresses with the Apply button dimmed until you make some changes.
Note: The very first added Public IP of each type that is added to an instance is considered a primary one (is always displayed first within the IP list). It can be deleted only if no more assigned addresses of a same version have left at a node. This address is used for both incoming and outgoing traffic, whilst the rest of IPs can only receive it.
Also, all IP addresses, assigned to a container, are shown within environment topology details at terminal upon connecting to an environment via SSH Gate.
Here, all container external addresses are displayed within the WAN IP column (in the same order as at the dashboard, i.e. IPv4 > IPv6), whilst the LAN IP one contains its internal address.
Note: In case the required type of the newly attached IP is not indicated explicitly (e.g. within Cloud Scripting solution or application/add-on package settings at CirrusGrid Marketplace), the IPv4 is used by default.
Also, all IP addresses, assigned to a container, are shown within environment topology details at terminal upon connecting to an environment via SSH Gate.
Here, all container external addresses are displayed within the WAN IP column (in the same order as at the dashboard, i.e. IPv4 > IPv6), whilst the LAN IP one contains its internal address.
