Hi Forest, looking at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using- eni.html#ec2-net-utils
"DHCP script Whenever the network interface receives a new DHCP lease, this script queries the instance metadata for Elastic IP addresses. For each Elastic IP address, it adds a rule to the routing policy database to ensure that outbound traffic from that address uses the correct network interface. It also adds each private IP address to the network interface as a secondary address." I think all they do is run a hook script on DHCP lease that configures the interface. And yes they add multiple ip addresses to the same interface. I am looking at some sort of solution because I want to use some instances as LXC hosts and would love to give each container its own ip. So I think I will have to go down the route of using subinterfaces. Will keep tracking this bug Thank you Alessandro -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1153626 Title: Multiple Interfaces and IPs not detected in AWS VPC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1153626/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
