Public IP

Public IP

The platform provides a Shared Load Balancer as the default entry point for hosted applications. For production environments, a Public IP is recommended because it creates a direct connection between the Internet and a specific container, supporting more secure and efficient request processing.

In this article

Public IP Overview

A Public IP can be attached to almost any software stack in an environment, except a Memcached node. Compared with access through the Shared Load Balancer, a Public IP provides a more stable connection and reduces the risk of being affected by traffic or processes from other applications.

Attaching a Public IP also enables access to features such as:

  • FTP and FTPS access
  • Custom SSL
  • Remote debugging from an IDE
  • WebSockets
  • Direct external access to a selected container
Public IP compared with Shared Load Balancer
Public IP provides a direct connection to a container, while Shared Load Balancer traffic is routed through the platform entry point.

Supported IP Versions

The platform supports two versions of the Internet Protocol:

IPv4 Internet Protocol version 4 is the fourth revision of the Internet Protocol and the first version to be widely deployed.
IPv6 Internet Protocol version 6 is the latest IP version. It expands the available address space, improves multicast routing, and simplifies processing by routers.

Attach a Public IP

To bind an external IP address to a node, open the environment topology wizard and enable the required number of Public IPv4 or Public IPv6 addresses in the central configuration area.

Add Public IPv4 and Public IPv6 in environment topology wizard
Configure Public IPv4 and Public IPv6 addresses in the topology wizard.
!

Notes

  • Enabling Public IPv4 disables the Access via SLB option by default.
  • This change can cause a temporary interruption in environment access for several minutes while DNS cache information is updated.
  • For horizontally scaled nodes, every container within the layer receives its own set of external IP addresses.

Manage Public IP Addresses

To find and manage allocated IP addresses in an existing environment, expand the required node in the environment topology list.

Manage external IPv4 and IPv6 addresses from dashboard
Expand a node to copy, attach, detach, or remove Public IP addresses.

Hover over an allocated address to access the available management actions:

Copy to Clipboard Copies the selected Public IP address in one click.
Attach/Detach IP(s) Adjusts the total number of Public IPv4 and Public IPv6 addresses assigned to the node.
Detach IP Removes a selected external address from the node.

Important Notes

!
  • A Public IP is a paid option and is charged for every hour of use. The exact cost is defined by the hosting service provider and can be viewed under Quotas & Pricing > Pricing > Options in the dashboard.
  • When a Public IP is enabled for any node in an environment, the standard Swap Domains function cannot be used for that environment. The Swap Public IPs API can be used instead.
  • When multiple Public IPs are attached, the first external address of each type—IPv4 or IPv6—is treated as the primary address and can only be deleted after the remaining addresses are removed.
  • The primary address supports both incoming and outgoing traffic. Additional Public IP addresses are intended for incoming traffic only.