It has come to our attention that aws is a bit inconsistent with their images across different sizes. While smaller images tend to have an eth0 interface, larger instances have an ens3 interface. Since the firewalling, loadbalancing, and virtualnetwork depend on a consistent, predictable interface name across all instances from the same provider, we will need to have the bootstrap first run a check to see if the expected interface exists, and if not will need to rollback the interface naming convention and reboot.
Here is a resource on how to rollback the naming convention:
It has come to our attention that aws is a bit inconsistent with their images across different sizes. While smaller images tend to have an
eth0interface, larger instances have anens3interface. Since the firewalling, loadbalancing, and virtualnetwork depend on a consistent, predictable interface name across all instances from the same provider, we will need to have the bootstrap first run a check to see if the expected interface exists, and if not will need to rollback the interface naming convention and reboot.Here is a resource on how to rollback the naming convention:
http://www.itzgeek.com/how-tos/mini-howtos/change-default-network-name-ens33-to-old-eth0-on-ubuntu-16-04.html