yahoo-eng-team team mailing list archive

[James Falcon <1867197@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3622

** Bug watch added: github.com/canonical/cloud-init/issues #3622
   https://github.com/canonical/cloud-init/issues/3622

** Changed in: cloud-init
       Status: Triaged => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1867197

Title:
  ec2: add support for rendering public IP addresses in network config

Status in cloud-init:
  Expired

Bug description:
  cloud-init 20.1 currently renders only local ip address information in
  the network configuration emitted for attached NICs.

  Ec2 instances can be launched and configured with multiple public IP
  addresses

  https://aws.amazon.com/blogs/aws/multiple-ip-addresses-for-
  ec2-instances-in-a-virtual-private-cloud/

  
  Ec2 IMDS network data exposes public IPv4 addresses in the following metadata keys:
  *  network.interfaces.macs.<MAC_ADDR>.public-ipv4s =  "18.218.219.181"
  * and an association of public ip to the private IPs allocated via the key
       "ipv4-associations": {
          "18.218.219.181": "172.31.44.13"
        },

  
  Cloud-init should render known public ipv4 address configuration on the node to avoid network round trips for local services that may connect with the VMs known public IP

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1867197/+subscriptions