Elastic IPs#

General information#

In K2 Cloud, instance network interfaces have Private IP in the internal virtual network, which is required for proper operation in the network infrastructure. Private IP is allocated automatically when the interface is created, and cannot be changed.

To ensure access to the instance from the outside, associate an Elastic IP (external address) to its network interface.

K2 Cloud provides public Elastic IP addresses, but you can also register your own provider-independent IPv4 address blocks (and make K2 Cloud responsible for broadcasting BGP routes) and use them in your projects:

  • operating with high reputation IP addresses (for email services);

  • simplifying the migration to the Cloud — when there are a lot of access lists containing specific address block;

  • problem prevention when government agencies block cloud provider subnets;

  • support of devices with certain IPs hardcoded in it;

  • compliance of different regulations;

  • saving the money — you don’t pay for using your own IP addresses.

If an instance does not need external access, then the Elastic IP may be deleted.

Billing#

An hourly fee is charged for each Elastic IP address.

Note

IP addresses from a user pool are free of charge.

Available quotas#

The following default quotas are allocated for an Elastic IP address:

  • 30 Elastic IP addresses per a project in each region.

If necessary, you can increase quotas. To do this, contact the support service via the support portal or by email support@k2.cloud.

Allocating Elastic IP#

When allocating Elastic IP, you will be suggested to choose an IP address pool from which the Elastic IP address will be allocated.

  • By default — the Elastic IP address range provisioned by K2 Cloud.

    Important

    If an allocated Elastic IP has not been used for two months (was not assigned to a network interface), then it will be automatically deleted. After the IP address is deleted, there is no guarantee that the same Elastic IP will be allocated next time.

    Important

    By default, NAT for Elastic IP addresses operates in stateless mode (without connection tracking), which improves traffic routing performance. In rare cases, this may cause end hosts to incorrectly process messages such as ICMP TTL Exceeded or ICMP Fragmentation Needed, as NAT in stateless mode does not translate the packet payload.

    If these mechanisms are critical for your services, submit a request to the support service with a list of Elastic IP addresses to switch them to stateful mode. Once the request is fulfilled, this mode will be supported for the addresses until they are deleted from the project or until stateful mode is disabled by the support service upon a separate request. Additionally, the Elastic IP address will be assigned a tag with the StatefulNat key and True value.

    Neither associating nor disassociating an Elastic IP address affects the support of stateful mode for that address. Traffic passing through this address will be processed in the selected mode, regardless of which instance it is currently assigned to.

  • Owned by user — The pool of IPv4 addresses of your organization in a registered range.

    Note

    This pool is available if you have registered your one or more provider-independent range of addresses (see Provisioning an IP address range). Unlike the K2 Cloud pool, you can specify a specific IP address, otherwise a free random address from your pool will be allocated.

  • DDoS protected — Elastic IP addresses in this pool are protected by Servicepipe provider against DDoS attacks.

    Note

    This pool is available if you previously activated the “DDoS protection service”.

To allocate an Elastic IP:

  1. In the top menu of the web interface, select the project and region where you want to allocate an Elastic IP address.

  2. Expand the side menu by clicking .

  3. Go to Virtual machines Networking Elastic IPs. To quickly find the section, you can use the menu search.

  4. Click Allocate Elastic IP.

  5. In the dialog window:

    • In the Elastic IP pool, select the address pool from which the IP address will be allocated.

    • (For a custom Elastic IP pool only) In the Elastic IP field, specify an IP address that should be allocated from the available range.

  6. If you need to set a tag, click Add tag and specify the tag key and value. To assign more tags, click Add tag again.

  7. Once all parameters are set, click Allocate.

Elastic IP association#

You can associate an unused Elastic IP address with an instance network interface in any VPC to which an internet gateway is attached.

  1. In the top menu of the web interface, select the project and region where you want to associate an Elastic IP address.

  2. Expand the side menu by clicking .

  3. Go to Virtual machines Networking Elastic IPs. To quickly find the section, you can use the menu search.

  4. In the resource table, select IP address and click Associate on the pop-up action bar.

  5. In the window that opens, select whether you want to associate Elastic IP with an instance or network interface.

    • To adjust the list, select a VPC from the drop-down list in the VPC field. In this case, all instances or network interfaces belonging to this VPC will be selected; otherwise, all available instances or network interfaces will be selected.

  6. From the drop-down list, select an instance or network interface with which the Elastic IP address will be associated.

    Note

    When you select an instance, the Elastic IP associated will be associated with its primary network interface.

  7. Click Associate to complete the operation.

Note

Once the Elastic IP is associated, the network interface becomes available at the specified address within a minute.

Elastic IP can also be associated on its page in the Information tab.

Elastic IP disassociation#

Elastic IP can be disassociated only if it is associated with any resource (otherwise the button will be inactive). Once the Elastic IP address has been disassociated, it can be re-associated with an instance network interface or deleted.

  1. In the top menu of the web interface, select the project and region where you want to disassociate an Elastic IP address.

  2. Expand the side menu by clicking .

  3. Go to Virtual machines Networking Elastic IPs. To quickly find the section, you can use the menu search.

  4. In the resource table, select the associated IP address and click Disassociate on the pop-up action bar. Multiple IP addresses can be selected at once.

  5. In the dialog window, confirm the action.

Elastic IP can also be disassociated on its page in the Information tab.

Provisioning an IP address range#

You can send a request to register your own provider-independent block of IPv4 addresses to the K2 Cloud support directly from the web interface. If necessary, our specialist will contact you to get more details. Once IP addresses are registered, you will receive a notification to the specified e-mail address. You can also check the registration status, for example, using the API method DescribeByoipCidrs. The address block status should change from pending-provision to advertised.

  1. In the top menu of the web interface, select the project and region where you want to register an IP address range.

  2. Expand the side menu by clicking .

  3. Go to Virtual machines Networking Elastic IPs. To quickly find the section, you can use the menu search.

  4. Click Provision IP range.

  5. In the new window, enter the IPv4 address range in CIDR notation in the CIDR block field. Provide additional relevant information in the Description field.

  6. Click Submit the request.

Note

To deprovision IP address range, contact support service or use the API method DeprovisionByoipCidr.

Assigning tags#

To add, modify or delete tags for Elastic IP:

  1. In the top menu of the web interface, select the project and region where you want to set tags for an Elastic IP address.

  2. Expand the side menu by clicking .

  3. Go to Virtual machines Networking Elastic IPs. To quickly find the section, you can use the menu search.

  4. In the resource table, find the Elastic IP for which tags should be modified and click on the Elastic IP’s ID to go to its page.

  5. Open the Tags tab and click Edit to set tags.

  6. To add a tag, fill in Key and Value fields. To assign the next tag, click Add tag.

    To modify a tag, edit the required fields (Value and/or Key) of the respective tag.

    To delete a tag, click the icon next to the tag you no longer need.

  7. To complete editing, click Save changes.

Alarm setup#

You can use alarms to configure the execution of a specified action when the traffic through an Elastic IP address goes beyond the specified threshold.

Important

Setup of alarms for Elastic IP addresses is not available in the new web interface yet. Please use the previous version of the web interface.

Deleting an Elastic IP#

Both associated and disassociated Elastic IPs can be deleted.

  1. In the top menu of the web interface, select the project and region where you want to delete an Elastic IP address.

  2. Expand the side menu by clicking .

  3. Go to Virtual machines Networking Elastic IPs. To quickly find the section, you can use the menu search.

  4. In the resource table, select the IP address and click Delete on the pop-up action bar.

  5. In the dialog window, confirm the action.

Elastic IP can also be deleted on its page in the Information tab.

Elastic IP information#

Information about allocated Elastic IPs can be viewed in the resource table in Virtual machines Networking Elastic IP.

To view details of a particular Elastic IP, find the desired address and click its ID. This will open the Elastic IP page.

The Information tab displays the main Elastic IP parameters :

  • Elastic IP address;

  • Elastic IP address pool;

  • instance with which it is associated;

  • network interface with which it is associated;

  • private IP address of a network interface.

Here you can:

The Tags tab displays all tags assigned to the Elastic IP. You can add new, modify existing, and delete no-longer-needed tags.