An External IP (EIP) is a public IPv4 address that you can allocate to your account and then associate with one of your resources.
You can disassociate an EIP from its resource at any time, and then reassociate it with another one. You can also fix an EIP to the instance it is associated with through the stop and start process using an OUTSCALE tag. For more information, see Configuring an Instance with User Data and OUTSCALE Tags.
EIPs are public IPv4 addresses that you can allocate to your account. You can then associate them with with the following resources:
Internet-facing load balancers
EIPs enable communication with the Internet. For more information, see About VPCs > IP Addressing and Access to the Internet.
To associate an EIP in a VPC, the VPC must have an Internet gateway attached. For more information, see Connecting Instances in a VPC to the Internet.
You can disassociate and reassociate an EIP at any time. For example, this enables you, in case of instance failure, to transfer the EIP to another instance. Therefore, the new instance has the same public IP, which means that scripts or applications using this EIP do not encounter any issue. For more information, see the EIP Association section below.
In the public Cloud, the EIP replaces the public IP of the instance. In a VPC, the EIP attaches a public IP to the instance or to the primary network interface. If you are working with several network interfaces, you can choose to associate the EIP with the primary network interface or with a flexible network interface (FNI). In that case, you can also choose to associate the EIP with either the primary private IP of the network interface or one of its secondary private IPs. For more information, see About FNIs.
You can associate an EIP with only one resource at a time.
If you associate an EIP with an instance or a network interface, using Cockpit you always need to disassociate the EIP before you can reassociate it with another resource. Using the APIs, you can configure a reassociation behavior: either prevent it, or automatically disassociate the EIP and reassociate it with the new instance or network interface you specify. For more information, see Associating an EIP with an Instance or a Network Interface.
If you create a NAT gateway, you need to specify an EIP. To modify the EIP associated with a NAT gateway, you need to delete the NAT gateway and re-create it with the new EIP. For more information, see Creating a NAT Gateway.
You can also associate an EIP with an internet-facing load balancer when managing the load balancer. For more information on the association behavior, see About Load Balancers > External IP. For more information on managing the load balancer, see Creating an Internet-facing Load Balancer in the Public Cloud or Creating an Internet-facing Load Balancer in a VPC.
You can associate an EIP to an instance using one of the following solutions:
This solution instantly associates the EIP with a running instance. However, the EIP is disassociated from the instance every time you stop and start the instance. For more information, see Associating an EIP with an Instance or a Network Interface.
This solution involves using a tag,
osc.fcu.eip.auto-attach. This tag enables you to associate an EIP with an instance and fix this EIP to the instance through the stop and start process. The tag is taken into account only at boot, that is, after launch and after a stop start. You can add this tag using regular tags or in the user data of the instance, with
osc.fcu.eip.auto-attachas Key and the EIP as Value. For more information, see Tagging Your Resources or Configuring an Instance with User Data and OUTSCALE Tags.
If you do not have time to stop and start your instance to associate the EIP with the instance using the
osc.fcu.eip.auto-attachtag, you can associate the EIP using the non-persistent solution, and then add this tag to the instance using the same EIP as value. Therefore, the EIP will be fixed to the instance the next time you stop and start the instance.
If you add the
osc.fcu.eip.auto-attachtag to an instance that already has an EIP associated or replace its value with another EIP, the current EIP will be removed and replaced with the new EIP you specify as value the next time you stop and start the instance.
As network interfaces do not follow a stop and start lifecycle, the association between an EIP and a network interface is always persistent.
After you disassociate an EIP, it is still allocated to your account. If you do not use an allocated EIP anymore, you can release it to make it available for other users. For more information, see Disassociating an EIP from an Instance or a Network Interface and Releasing an EIP from Your Account.
Ensure that none of your applications or scripts use the EIP you release.