The bug here is really no different than if you have a "real" server, and need to change the network card. You'd stop the server, replace the card, start the server and no longer have eth0.
There are a number of things that really *should* be done when "cleaning" an image, this is just one of them. Other things might be removing /root/.bash_history (its an example, possibly not a good one).
I think at the moment this is best left as a "cleaning" step that must occur. Things like this are why I recommend using the pristine tarball rather than a live image when rebundling an ec2 image.
The bug here is really no different than if you have a "real" server, and need to change the network card. You'd stop the server, replace the card, start the server and no longer have eth0.
There are a number of things that really *should* be done when "cleaning" an image, this is just one of them. Other things might be removing /root/.bash_history (its an example, possibly not a good one).
I think at the moment this is best left as a "cleaning" step that must occur. Things like this are why I recommend using the pristine tarball rather than a live image when rebundling an ec2 image.