With multiple NICs, Public IP address is not displayed

With multiple NICs, Public IP address is not displayed in the AWS Instance or Azure VM.

When configuring a Virtual Machine with multiple nics the external nic must be configured first to enable the Public IP address

Overview

When creating a blueprint containing a VM with public and private network interfaces the public interface must be defined first. If the internal network is defined in the blueprint first then this issue can occur.

This example shows the external network with a public IP defined first.

nics:
  external-network:
    ips:
      - private:
          type: dynamic
        public:
          type: static
    firewall: demo-external-firewall
    subnet: demo-external-subnet
  internal-network: 
    ips:
      - private:
          type: dynamic
    firewall: demo-internal-firewall
    subnet: demo-internal-subnet

AWS has the following warning when using Multiple IP addresses.

When you add a second network interface, the system can no longer auto-assign a public IPv4 address. You will not be able to connect to the instance over IPv4 unless you assign an Elastic IP address to the primary network interface (eth0). You can assign the Elastic IP address after you complete the Launch wizard. For more information, see Working with Elastic IP addresses.

When defining the external network first AWS and Azure will display the external Public IPv4 address in the console.

AWS

Azure

If the internal network is defined first in a Tuono blueprint both AWS and Azure may not configure the Public IPs for the NIC.

AWS

Azure