A Floating IP is a public, static IP address that can be assigned to Virtual Machines (VMs), Bare Metal servers, and Load Balancers, allowing them to receive external connections without having a public network interface. This means that these products don't have a public network interface, but they can still receive incoming connections from the Internet.
A floating IP allows you to quickly provide access from an external network to a Virtual Machine that doesn't have a public network interface. By assigning an address to the VM you will be able to connect to it.
Another method for providing access is by creating a public interface for the device. However, this can cause conflicts with the private routed interface as both are used for accessing the internet. You would have to configure the routing manually. A Floating IP is a convenient solution if you only need temporary access to an external network or prefer not to deal with routing configuration.
## How does it work?When you reserve a floating IP and assign it to your Virtual Machine, the router directs incoming traffic to your device by forwarding packets intended for that IP. Outgoing traffic from your instance will still use its private IP, while incoming traffic will be forwarded through the Floating IP.
If your instance has multiple private IPv4 addresses within a routable private subnet, you can assign a unique floating IP to each of these private addresses. Multiple private subnets from one network can be grouped to a single port, allowing the client to attach a Floating IP to any of the routable addresses.
## Check if your subnet is routable
2. Click the three-dot menu, then select **Edit**.
3. Ensure the **Enable router gateway** slider is enabled, making the subnet routable, and allowing servers within the subnet to access the Internet and receive incoming connections.
## Reserve a floating IP from the menu
A floating IP is assigned by a specific data center, and its address is linked to that location. It can only be transferred to a Virtual Machine within the exact location.
1. Select the Region where your machine is located to assign a floating IP and navigate to the **Networking** section.
2. Open the Floating IPs section. You can create a floating IP without assigning it to a machine by clicking **Create a new floating IP.**
3. Additionally, you can create a floating IP and immediately assign it to a specific Virtual Machine. To do this, enable the "Assign to existing instance" slider, select the machine and interface, and click **Create a new floating IP.**
## Reserve a floating IP when creating a Virtual Machine
When creating a VM, in the "Network settings" section, select the "**Private** " network type. Specify the network and subnet of the interface you want to assign the floating IP. Enable the "**Use floating IP** " slider, click "**Create a new floating IP** ", and save the settings using the "**Add Interface** " button.
The Virtual Machine will be created with a private interface and a new floating IP assigned to it.
Next to the free IP, click "Assign to instance" or select this option from the selector on the right.
Select the Virtual Machine in the pop-up window, and the floating IP's network interface will be assigned. Click **Assign floating IP**.
## Detach a floating IP from a Virtual Machine
You can detach a floating IP address in the "Floating IPs" section or in the Virtual Machine menu. In the "Floating IP" section, click the selector next to the address and select **Detach from Instance**, and the IP will no longer be assigned to the machine.
In the Virtual Machine menu, open the "Networking" tab and select the private interface. Open the selector and click "**Detach Floating IP** ". The IP will no longer be assigned to this machine.
Floating IPs are freely available for Virtual Machines, Bare Metal servers, and Load Balancers. Once detached, they remain ready for reassignment. You can transfer it to another Virtual Machine within the same data center by selecting the target instance and linking the IP. This helps maintain a stable external address even as your infrastructure evolves.
## Delete a floating IP
In the "Floating IPs" section, click the selector next to the desired address and select **Delete**. The IP will be removed, and you will no longer be charged.
Keep services reachable even when infrastructure changes by assigning and reassigning a floating IP address to a Virtual Machine. A floating IP is a static public address — it stays the same when moved between instances, so DNS records and client configurations remain valid.
Open a terminal and set these variables before running the examples:
```bash theme={null} export GCORE_API_KEY="{YOUR_API_KEY}" export GCORE_CLOUD_PROJECT_ID="{YOUR_PROJECT_ID}" export GCORE_CLOUD_REGION_ID="{YOUR_REGION_ID}" ``` ## QuickstartThe scripts below reserve a floating IP and assign it to an existing Virtual Machine's private interface, then unassign and delete it. The VM's subnet must be [routable](/cloud/networking/create-and-manage-a-subnetwork#network-routing) for assignment to work.
Each step below explains what the call does, which parameters matter, and what the response looks like.
Deleting a floating IP releases the address and stops billing for it.
Reserve a public IP from the region pool and bind it to a VM's private interface. The [`gcore_cloud_floating_ip`](https://registry.terraform.io/providers/G-Core/gcore/latest/docs/resources/cloud_floating_ip) resource manages both reservation and assignment in a single configuration.
Creating the resource reserves a public IP from the region pool. Without `port_id`, the address is held unassigned with `status: DOWN`.
```hcl theme={null} resource "gcore_cloud_floating_ip" "example" { project_id = var.project_id region_id = var.region_id } output "floating_ip_address" { value = gcore_cloud_floating_ip.example.floating_ip_address } ```After `terraform apply`:
```bash theme={null} floating_ip_address = "109.61.46.198" ``` ## Assign to a Virtual MachineSetting `port_id` to a VM's private interface UUID binds the floating IP to that instance. Incoming packets are forwarded to the VM; outbound traffic continues to use the private IP.
```hcl theme={null} resource "gcore_cloud_floating_ip" "example" { project_id = var.project_id region_id = var.region_id port_id = "{PORT_ID}" } ```To find the `port_id`, retrieve the instance details and extract the port ID from each interface entry under `addresses`:
```bash theme={null} curl "https://api.gcore.com/cloud/v1/instances/{PROJECT_ID}/{REGION_ID}/{INSTANCE_ID}" \ -H "Authorization: APIKey $GCORE_API_KEY" \ | jq '.addresses | to_entries[].value[].port_id' ```After applying, `status` changes from `DOWN` to `ACTIVE`.
## Unassign from a Virtual MachineRemove `port_id` from the resource block and run `terraform apply`. The address returns to `DOWN` and remains reserved for reassignment.
```hcl theme={null} resource "gcore_cloud_floating_ip" "example" { project_id = var.project_id region_id = var.region_id # port_id removed — Terraform detaches the floating IP on next apply } ``` ```bash theme={null} terraform apply ``` ## Delete a floating IPRemove the resource block — Terraform detects the missing declaration and releases the address on the next `terraform apply`.
```hcl theme={null} # Remove or comment out this block: # resource "gcore_cloud_floating_ip" "example" { # project_id = var.project_id # region_id = var.region_id # } ``` ```bash theme={null} terraform apply ``` ## Import an existing floating IPUse when a floating IP was reserved outside Terraform and needs to be brought under configuration management.
```bash theme={null} terraform import gcore_cloud_floating_ip.example '{PROJECT_ID}/{REGION_ID}/{FLOATING_IP_ID}' ```