For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/it/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/it/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/it/guides/public-cloud/network-services/additional-ip-vs-floating-ip.md.
Vai al contenuto

Concepts - Public Cloud IP types

Vedi come Markdown

Find out how to use public IP addresses in the scope of Public Cloud Networking - Basic IP, Additional IP and Floating IP

Objective

Infrastructure resources can be exposed to the Internet via their own public IP addresses. In the Public Cloud universe, these are Basic IP addresses. For services created on such an infrastructure it is however not recommended to use these IP addresses to expose services themselves.

When a service should be optimised for scalability or agility, its public IP address should not be linked to a particular server or virtual machine. For such cases, separate reserved IP addresses are the best way to make services publicly available.

In the Public Cloud universe you can use Additional IP (previously labelled as Failover IP) or Floating IP to achieve this, or Basic IP to expose an instance directly.

Additional IP and Floating IP provide a flexible way to manage public access to your services. They can stay infrastructure-agnostic and be scaled up or migrated whenever needed.

This guide explains the differences between these three types of public IP addresses.


OVHcloud Console Access

  • Direct link:
  • Navigation path: Public Cloud > Select your project > Network > Public IP

Public Cloud IP concepts

Basic IP

A Basic IP is the public IP address an instance receives when it is attached directly to Ext-Net, the public network managed by OVHcloud in each region. You get a Basic IP by selecting it explicitly when you create an instance.

A Basic IP is delivered as a pair of addresses: one IPv4 and one IPv6. Each address can be deleted separately; deleting one does not delete the other.

Info

In 3-AZ regions, the IPv6 address of a Basic IP cannot be provisioned from the OVHcloud Console yet.

A Basic IP is tied to the instance it was created for. It cannot be moved to another instance or network service, and deletion is the only action available on it. If you delete a Basic IP, or detach the Ext-Net interface from the instance, the address is released for good and cannot be reassigned to you. For an address that must outlive a specific instance, use an Additional IP or a Floating IP instead.

Typical use cases are instances that need direct Internet access without extra configuration: test and development environments, standalone servers, or instances that also use an Additional IP.

A Basic IP is billed per second, separately from the instance it is attached to.

Other network services do not use the Basic IP of an instance:

  • A Load Balancer is exposed to the Internet through a Floating IP only.
  • A Gateway gets its own Basic IP on Ext-Net, which it uses as its external network. Unlike the Basic IP of an instance, it comes with the Gateway: it is not an option you choose, and it cannot be detached or deleted on its own. It is billed separately from the Gateway.

Additional IP (previously labelled as Failover IP)

This type of public IP address is available for services of all relevant OVHcloud universes: Bare Metal Cloud (for bare metal servers), Public Cloud (with OpenStack) or Hosted Private Cloud (with VMware or Nutanix for example).

They are designed to be used in cross-product scenarios, for example in failover operations or hybrid cloud use cases. They are billed on a monthly basis.

Once an Additional IP address is available in your OVHcloud Console, it can be attached/detached or moved between servers and Public Cloud instances. Manual changes may be needed on the backend side to apply new IP configurations.

Please note that in the Public Cloud universe, Additional IP can only be used with instances that have a Basic IP (a public interface on the Ext-Net network).

More information about configuring Additional IP addresses is available in this guide.

Floating IP

This type of public IP address is only available for Public Cloud services, designed for cloud-native use cases and especially automation (e.g. Terraform, Ansible). They serve to expose a private instance or a private network service (Load Balancer for example) to the public network.

The backend (instance/Load Balancer) system configuration when using Floating IP is entirely automatic (via DHCP protocol), no manual setup is needed. However, they require a Gateway in order to map a public IP address to an instance or network service.

Please note that Floating IP can only be associated with a port on a private network (within a specific private network inside a given region).

Floating IP is billed per second on a pay-as-you-go basis.

More information about configuring Floating IP is available on the Public Cloud Networking Concepts page.

How to obtain public IP addresses in the OVHcloud Console

In the Network section of the left-hand menu of your Public Cloud project, click Public IP. The Floating IP and Additional IP tabs let you manage these addresses according to your needs. The Basic IP tab lists the Basic IP addresses of your project, with their region, associated resource and status. From this tab, you can delete a Basic IP.

Basic IP addresses are not ordered from this page: you get one by selecting it when you create an instance.

Depending on your choice, you can select from the different regions and further configuration options are available.

Warning

The pricing methods depend on the use of the IP you choose. Additional IP usage is billed monthly. Basic IP and Floating IP usage are billed per second, separately from the instance.

Go further

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analysed by our experts.

Join our community of users.

Questa pagina ti è stata utile?