Need for a fixed public IP address #
In certain contexts, there is a need for one (or more) public IP addresses that remain fixed for the duration of the DRP, such as:
- For an IPsec tunnel with a third party
- For an SFTP server address
- For an EDI flow
- …
Unfortunately, it is not possible to keep the same public IP address in nominal (in the customer’s data center) and the OTC Cloud: they are not part of the same ASN.
Solution implemented #
During the project onboarding phase:
- We work with the customer to determine the number of fixed public IP addresses to be created (called EIPs: Elastic IPs).
- Which servers (ECS) should host these EIPs?
- Then Nuabee’s tools deploy these EIPs (through several steps)
The EIP addresses are communicated to the customer (available in our monitoring console (Atlas) in the details of a machine) in order to update their configurations (or notify their partners).
Of course, Nuabee’s internal tools were designed not to destroy these EIPs during maintenance operations on these servers.
Fixed public IP constraints #
Implementing this solution means that for the server supporting this fixed IP address:
- Can no longer change its backup public IP address (it must be deleted and another one created)
- Can no longer change the IP address of the subnet gateway
- Can no longer change the VPC of the subnet
- Can no longer change the subnet mask